Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69559 - install archlinux-keyring failed due to verification
Attached to Project:
Arch Linux
Opened by Juerg Oehler (SwissGeorge) - Saturday, 06 February 2021, 11:48 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 06 February 2021, 11:56 GMT
Opened by Juerg Oehler (SwissGeorge) - Saturday, 06 February 2021, 11:48 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 06 February 2021, 11:56 GMT
|
Detailshi
today (6 febrary 2021) i started to upgrade 5.2.13-arch1-1-ARCH system. steps: - pacman -Sy to make sure everything is working before upgrade - pacman-key --populate archlinux - pacman -Syu archlinux-keyring every question was answered by default. system downloaded all packages without any problems. but checking keys in keyring failed: key ... could not be looked up remotely. i so looked for alike problems on the internet. i then went through <wiki.archlinux.org/index.php/Pacman/Package_signing>. at the end i followed <Resseting all keys>. this usualy helps. goal was to install an uptodate keyring package. pacman -S archlinux-keyring solved: core/archlinux-keyring 20190827-1 20210110-1 0.38MiB errror: key "6D42BDD116E0068F could not be looked up remotely [core] mirrorlist point to http://mirror.puzzle.ch... http://pkg.adfinis-sygroup.ch i got the actual pacman-mirrorlist (without any problems) and used the first two servers from germany. with the same result. i so do think the package <archlinux-keyring> is signed with a unknown key. is there any functionality to have packages verified on the original site? of course configuring <SigLevel> to <Never> works but would mean opening the miracle at it's core. please recommend the process for resolving this problem. thank you. |
This task depends upon
Closed by Antonio Rojas (arojas)
Saturday, 06 February 2021, 11:56 GMT
Reason for closing: Not a bug
Additional comments about closing: Please use the forum for support
Saturday, 06 February 2021, 11:56 GMT
Reason for closing: Not a bug
Additional comments about closing: Please use the forum for support