You are not logged in.

#1 2017-12-03 18:04:31

bmentink
Member
From: New Zealand
Registered: 2009-08-23
Posts: 442

Upgrade failed with errors in keys

Hi,

After my last attempt at upgrade I get this:

(455/455) checking keys in keyring                              [##################################] 100%
downloading required keys...
error: key "6BC26A17B9B7018A" could not be looked up remotely
error: key "EEEEE2EEEE2EEEEE" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

There is no indication which is the offending key(s) and nothing in pacman.log ..
How can I resolve this?

Thanks.

Last edited by bmentink (2017-12-03 18:06:53)

Offline

#2 2017-12-03 18:13:27

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,210

Re: Upgrade failed with errors in keys

Of course there is indication, they are mentioned directly in the error message... How long  ago has your last system update been?

That said, this exact error case is handled in https://wiki.archlinux.org/index.php/Pa … p_remotely

Offline

#3 2017-12-03 19:20:44

bmentink
Member
From: New Zealand
Registered: 2009-08-23
Posts: 442

Re: Upgrade failed with errors in keys

V1del wrote:

Of course there is indication, they are mentioned directly in the error message... How long  ago has your last system update been?

That said, this exact error case is handled in https://wiki.archlinux.org/index.php/Pa … p_remotely

Thank's for the link, but your original statement is a bit harsh ....

Where exactly in the line:

 error: key "6BC26A17B9B7018A" could not be looked up remotely

does it say: "go update your keys or upgrade the archlinux-keyring first ??"  You would think a couple of helpful suggestions "in" the  error message would save lot's of forum requests for help.

Oh well,  .. My 2c.

Last edited by bmentink (2017-12-03 19:22:59)

Offline

#4 2017-12-03 19:31:16

loqs
Member
Registered: 2014-03-06
Posts: 18,894

Re: Upgrade failed with errors in keys

You did not find any relevant search results for the following?

error: required key missing from keyring

You could post a patch or feature request against pacman asking for the messages to be reworked.

Offline

#5 2017-12-03 19:37:34

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Upgrade failed with errors in keys

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#6 2017-12-04 03:16:46

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,726

Re: Upgrade failed with errors in keys

You only got the error because your gpg is broken. Fix that and it would have been looked up remotely and everything would have been fine.

And remember, pacman isn't Arch specific. There's no way anyone's going to accept a patch telling you to update the archlinux-keyring package, especially since that's not the real fix.

Last edited by Scimmia (2017-12-04 03:17:52)

Offline

#7 2017-12-05 16:52:35

forumache
Member
From: Netherlands
Registered: 2011-09-02
Posts: 57

Re: Upgrade failed with errors in keys

@bmentink If your gpg is not "broken", but your company broke its remote key lookup due to a proxy (mine did), try changing the default keyserver in /etc/pacman.d/gnupg/gpg.conf from the default hkp://pool.sks-keyservers.net to hkps://hkps.pool.sks-keyservers.net:443

You might need to kill dirmngr too (I did), before running pacman -Syu again.

Last edited by forumache (2017-12-05 16:53:02)

Offline

#8 2017-12-05 17:08:47

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: Upgrade failed with errors in keys

Relevant bug regarding the default hkp:// keyserver: https://bugs.archlinux.org/task/55278

Last edited by eschwartz (2017-12-05 17:09:13)


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

Board footer

Powered by FluxBB