Skip to main content ↑ ↓
Topic: keyring PGP key error on upgrade (Read 3758 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

keyring PGP key error on upgrade

I had some errors that stopped the update relating to a missing key:
PGP key 139B09DA5BF0D338, "David Runge <[email protected]>"
Then I installed most of the packages with -S, but these 3 were related to that key:
Packages (3) libtraceevent-1:1.6.2-1  libtracefs-1.4.2-1  trace-cmd-3.1.2-1
So I manually installed the archlinux-keyring package update with -S too and then I could install the other 3 above, with the new keys and the hooks run.
So running this before -Syu was the solution to my problem:
Code: [Select]
$ pakku -S archlinux-keyring
(Or use pacman, yay, whatever you are usually updating with.)

I also did some other things first but not sure if that's relevant, although I guess the segfault looks sort of interesting wherever that came from, I think possibly inside pacman rather than pakku as the lock file was left in place. Importing the key manually didn't help at all.
Code: [Select]
downloading required keys...
:: Import PGP key 139B09DA5BF0D338, "David Runge <[email protected]>"? [Y/n] y

error: segmentation fault
Please submit a full bug report with --debug if appropriate.
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
Segmentation fault
$ gpg --recv-key 139B09DA5BF0D338
gpg: key 139B09DA5BF0D338: public key "David Runge <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
$ pakku -Syu
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
$ sudo rm /var/lib/pacman/db.lck

Re: keyring PGP key error on upgrade

Reply #1 –
in the past when i had trouble with keyring and had the key ring number i also seemed to have issue with tht gpg command and used pacman-key command instead..
Cat Herders of Linux

Re: keyring PGP key error on upgrade

Reply #2 –
Had the same issue, just with different PGP data appearing in the error message (someone else's email address).
Issue is about having to accept a compulsory receipt of a PGP key to then allow the usual daily upgrade to occur.  Not accepting the request terminates the upgrade, Accepting the request brings an error that states it cannot upgrade the PGP key remotely, which also terminates the upgrade.

So I ran :

 pacman -S archlinux-keyring

as suggested  in the entries above in this forum thread.

While it is installing, It has many warnings about being a Dev version only. It installed ok, so then I retried the daily upgrade which returns to its normal self  :=  brilliant.

Looking for confirmation that this will all turn out O.k. - - - usually this kind of thing gets handled permanently, eventually - go Artix Dev. team !!

Also, anything I else I should do toward this error situation ?

Thanks.

Re: keyring PGP key error on upgrade

Reply #3 –
Quote from: protoshop – on
Had the same issue, just with different PGP data appearing in the error message (someone else's email address).
Issue is about having to accept a compulsory receipt of a PGP key to then allow the usual daily upgrade to occur.  Not accepting the request terminates the upgrade, Accepting the request brings an error that states it cannot upgrade the PGP key remotely, which also terminates the upgrade.

So I ran :

 pacman -S archlinux-keyring

as suggested  in the entries above in this forum thread.

While it is installing, It has many warnings about being a Dev version only. It installed ok, so then I retried the daily upgrade which returns to its normal self  :=  brilliant.

Looking for confirmation that this will all turn out O.k. - - - usually this kind of thing gets handled permanently, eventually - go Artix Dev. team !!

Also, anything I else I should do toward this error situation ?

Thanks.


did you get a ke ring number?  sudo pacman-key --recv-keys (keyring number) && sudo pacman-key --lsign (keyring number)
Cat Herders of Linux
 

Re: keyring PGP key error on upgrade

Reply #4 –
I think it was simply a timing issue, the packages that gave me the error were from the Arch "community" repo. "archlinux-keyring" is from "universe" and the update was released yesterday on the 20th, vs the equivalent Arch "archlinux-keyring" which was updated nearly a week ago on the 14th:
https://archlinux.org/packages/core/any/archlinux-keyring/
So some of the packages in the Arch repos were starting to be built with the assumption you would already have the new keyring installed.
I guess having updated "archlinux-keyring" first it should be fine going forward now, no further action required, this sort of thing just happens now and again due to all the potential synchronizing details when you enable the Arch repos too.
Possibly the devs might give it some kind of "update this first" flag or something to automatically bypass this, but I've no idea if that's desirable or not.