Hi, have both files in a directory qt4-4.8.7-32-x86_64.pkg.tar.xz qt4-4.8.7-32-x86_64.pkg.tar.xz.sig
/>sudo pacman -U qt4-4.8.7-32-x86_64.pkg.tar.xz error: 'qt4-4.8.7-32-x86_64.pkg.tar.xz': invalid or corrupted package (PGP signature)
pacman-key -v qt4-4.8.7-32-x86_64.pkg.tar.xz.sig ==> Checking qt4-4.8.7-32-x86_64.pkg.tar.xz.sig... (detached) gpg: Signature made Sun 10 May 2020 07:52:41 PM CEST gpg: using RSA key DD3BF75DCD96541AC723B7CD6A4CD3276CA8EBBD gpg: Note: trustdb not writable gpg: Good signature from "Viktor Drobot linux776@gmail.com" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: DD3B F75D CD96 541A C723 B7CD 6A4C D327 6CA8 EBBD ==> ERROR: The signature identified by qt4-4.8.7-32-x86_64.pkg.tar.xz.sig could not be verified.
Fix?
Pinned Comments
eschwartz commented on 2019-05-09 13:24 (UTC)
@semeion,
qt4 was expelled from the official repositories due to https://lists.archlinux.org/pipermail/arch-dev-public/2019-April/029560.html
It will not be restored, because software needs to stop using qt4. It's fine for people to still use it via the AUR if they have old software that is not ported, but the proper solution is to get that software ported to qt5.
"It takes a long time to compile" is not a reason to move it to community.
@xuanruiqi,
Only Developers and Trusted Users have access to pkgbuild.com, and we will not be uploading qt4 there. If we wanted qt4, we would upload it to community, but we don't -- we have managed to move every package still being actively maintained in the official repos, over to qt5, and we want to stay that way.
...
Again, the proper long-term solution is to get software ported over to qt5.
dviktor commented on 2019-05-05 17:49 (UTC) (edited on 2019-05-15 19:02 (UTC) by dviktor)
For those who have problems with
‘std::tr1’ has not been declared
error: build in clean chroot withextra-x86_64-build
script.