You are not logged in.
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
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
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 remotelydoes 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
You did not find any relevant search results for the following?
error: required key missing from keyringYou could post a patch or feature request against pacman asking for the messages to be reworked.
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
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
@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
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