Bug #3049
Keys are messed up, cannot pacman -Syu
Status:
not-a-bug
Priority:
bug
Assignee:
-
% Done:
0%
Description
- steps to reproduce:
1) # pacman -Syu
- expected result:
A regular update.
- actual result:
downloading required keys...
error: key "7258734B41C31549" could not be looked up remotely
error: key "6D42BDD116E0068F" could not be looked up remotely
error: key "3B94A80E50A477C7" could not be looked up remotely
error: key "686B063AC4BC0EC9" could not be looked up remotely
error: key "9D4C5AA15426DA0A" 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.
History
Updated by bill-auger almost 3 years ago
did you just install the system?
try adding this line to /etc/pacman.d/gnupg/gpg.conf
keyserver pool.sks-keyservers.net
if there are new keyrings to be installed, those often must be installed separately and first
# pacman -Sy archlinux-keyring archlinux32-keyring parabola-keyring --needed
Updated by bill-auger almost 3 years ago
- Status changed from unconfirmed to not-a-bug
closing as stale
Updated by arojas0609 over 2 years ago
Hi, I have the same error, in a new Parabola installation I try to update the keyring packages:
# pacman -Sy archlinux-keyring archlinuxarm-keyring archlinux32-keyring parabola-keyring
error: no se pudo buscar la clave «6D42BDD116E0068F» de forma remota
error: la clave necesaria no está presente en el depósito
error: no se pudo realizar la operación (error inesperado)
Ocurrieron errores, por lo que no se actualizaron los paquetes
I try to change keyserver to pool.sks-keyservers.net with the same result ...
Updated by telur over 2 years ago
im usually do these:
1.pacman -Sy parabola-keyring archlinux-keyring
2.pacman-key --init
3.pacman-key --populate parabola arch
4.pacman-key --refresh-keys
those are just example on my x86 machine, if you use other repos such arch32 be sure to list them as well