Arch Linux

hburd

Member

Registered: 2023-06-30

Posts: 2

[SOLVED] Gpg errors when upgrading archlinux-keyring

I ran pacman -Syu like I normally do, but this time I ran into some strange errors when upgrading the archlinux-keyring package.

:: Processing package changes...
[...]
( 50/347) upgrading archlinux-keyring                                                                            [###################################################################] 100%
==> Appending keys from archlinux.gpg...
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)

This continues for about 30k lines, occasionally interspersed with:

gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: [don't know]: invalid packet (ctb=40)
gpg: /etc/pacman.d/gnupg/pubring.gpg: copy to '/etc/pacman.d/gnupg/pubring.gpg.tmp' failed: Invalid packet
gpg: error writing keyring '/etc/pacman.d/gnupg/pubring.gpg': Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: error reading '/usr/share/pacman/keyrings/archlinux.gpg': Invalid packet
gpg: no valid OpenPGP data found.
gpg: import from '/usr/share/pacman/keyrings/archlinux.gpg' failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet
gpg: mpi larger than indicated length (40 bits)
gpg: keydb_search failed: Invalid packet

After that, the package upgrades continue, the post-transaction hooks seem to run without issue, and at the end of the pacman output is this error:

call to execv failed (No such file or directory)
error: command failed to execute correctly

I wanted to try to reproduce this by running `sudo pacman -Syu archlinux-keyring`, but this gives a different error now:

:: Synchronizing package databases...
 core is up to date
 extra                                                                                 8.3 MiB  6.77 MiB/s 00:01 [###################################################################] 100%
 community is up to date
 multilib is up to date
warning: archlinux-keyring-20230629-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20230629-1

Total Download Size:   1.14 MiB
Total Installed Size:  1.62 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 archlinux-keyring-20230629-1-any                                                   1167.7 KiB  13.7 MiB/s 00:00 [###################################################################] 100%
(1/1) checking keys in keyring                                                                                   [###################################################################] 100%
(1/1) checking package integrity                                                                                 [###################################################################] 100%
error: archlinux-keyring: signature from "Christian Hesse <eworm@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20230629-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

I don't understand what just happened, or even what is broken, which makes it difficult to formulate a constructive question. I'm guessing my keyring is messed up somehow, but I don't know enough about package signing to understand the consequences of that. So I will start with two very vague questions: what just happened, and how can I fix this?

Last edited by hburd (2023-07-04 03:49:20)

hburd

Member

Registered: 2023-06-30

Posts: 2

Re: [SOLVED] Gpg errors when upgrading archlinux-keyring

I don't think I properly communicated the problem in my initial post - I wasn't able to install or update any packages without running into this "invalid or corrupted package (PGP signature)".

I fixed this by following the resetting all keys steps on the wiki, specifically:

# pacman-key --init
# pacman-key --populate

After that I did a pacman -Syu and it finished without problems.