You are not logged in.
I fixed the problem with kfloppy and telepathy and tried to do -Syu again.
I now get this problem and am unsure how to fix it. I'm a little afraid to just keep at it because I'm sure I'll muck it up beyond repair.
So, here's what's happening:
[bart@ASU-X99 ~]$ sudo pacman -Syyu
:: Synchronizing package databases...
core 132.5 KiB 148 KiB/s 00:01 [--------------------------------------------] 100%
extra 8.2 MiB 5.23 MiB/s 00:02 [--------------------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (244) apache-2.4.58-1 apr-1.7.4-1 archlinux-keyring-20231026-1 attica5-5.111.0-1 avogadrolibs-1.98.0-3
avogadrolibs-qt5-1.98.0-3 baloo5-5.111.0-1 bash-5.2.015-5 bluedevil-1:5.27.9-1 bluez-qt5-5.111.0-1
<SNIP>
syndication5-5.111.0-1 syntax-highlighting5-5.111.0-1 systemsettings-5.27.9-1 texinfo-7.1-1
threadweaver5-5.111.0-1 tracker3-miners-3.6.2-1 vim-9.0.2070-1 vim-runtime-9.0.2070-1 vlc-3.0.20-1
vtk-9.2.6-10 vulkan-icd-loader-1.3.269-1 vulkan-tools-1.3.269-1 xcb-util-cursor-0.1.5-1
xdg-desktop-portal-kde-5.27.9-1 xfsprogs-6.5.0-1 xorg-server-21.1.9-1 xorg-server-common-21.1.9-1
xorg-xwayland-23.2.2-1 xxhash-0.8.2-1 zeromq-4.3.5-2 zlib-1:1.3-2
Total Installed Size: 3205.28 MiB
Net Upgrade Size: 10.67 MiB
:: Proceed with installation? [Y/n]
(244/244) checking keys in keyring [--------------------------------------------] 100%
(244/244) checking package integrity [--------------------------------------------] 100%
error: iana-etc: signature from "Jelle van der Waa <jelle@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/iana-etc-20231018-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] ^C
Interrupt signal received
I interrupted the process here because it seems to go on forever
After poking around on this forum, I tried:
[bart@ASU-X99 ~]$ sudo pacman-key --populate archlinux
==> Appending keys from archlinux.gpg...
gpg: public key of ultimately trusted key 3C5CFD4F2FA83929 not found
==> Locally signing trusted keys in keyring...
==> ERROR: 2AC0A42EFB0B5CBC7A0402ED4DC95B6D7BE9892E could not be locally signed.
==> ERROR: 69E6471E3AE065297529832E6BA0F5A2037F4F41 could not be locally signed.
==> ERROR: D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C could not be locally signed.
==> ERROR: 3572FA2A1B067F22C58AF155F8B821B42A6FDCD7 could not be locally signed.
==> ERROR: 91FFE0700E80619CEB73235CA88E23E377514E00 could not be locally signed.
[bart@ASU-X99 ~]$
I tried:
[bart@ASU-X99 ~]$ sudo pacman -Qn | wc -l
[sudo] password for root:
1489
which seems to indicate there are 1489 keys stored in that file.
Can that file be removed and recreated? There must be a bunch of "junk" in it by now.
Last edited by mt_arch_user (2023-11-02 03:01:16)
Offline
The key database is normally on newer archlinux-keyring versions kept up to date with a systemd timer. Is that broken in your case? In any case the "canonical" fix for this used to be to update archlinux-keyring in isolation, so:
sudo pacman -Sy archlinux-keyring && sudo pacman -Su
Maybe also post
systemctl status archlinux-keyring-wkd-sync.{timer,service}
pacman -Qn lists all packages you've installed that still exist in the sync repositories and have no relation whatsoever to the keyring, not sure where you picked up that inference.
FWIW as far as "going on forever", that was a prompt for your input, you will need to have chosen Y or n
Last edited by V1del (2023-11-02 00:35:33)
Offline
Your keyring is corrupt.
https://wiki.archlinux.org/title/Pacman … l_the_keys
Last edited by Scimmia (2023-11-02 01:56:55)
Offline
FWIW as far as "going on forever", that was a prompt for your input, you will need to have chosen Y or n
:-) No, what I meant is that when I responded to the prompt, it gave me another one for the next key. And the next. And the next. wash, rinse and repeat!
Offline
I won!
Looks like Scimmia was right. I found this link:
https://wiki.artixlinux.org/Main/Troubl … gnature.29
which shows how to remove the key file and rebuild it.
Then, of course, I had to figure out where the file that chose the repository is and remove the entries that had 404 errors. Eventually though it is done!
I even figured out how to update the packages that were installed using AUR!
Thanks for the responses as they pointed me in the right direction. Don't know what I'd do without you people.
Bart
Last edited by mt_arch_user (2023-11-02 03:00:36)
Offline