You are not logged in.
Hi,
(Solution)
gpg --search-keys <key id from validpgpkeys section>
Now i see the error message cut off part of the key id, hence i could not find it. So the solution is to look in the PKGBUILD / validpgpkeys section and use that id to resolve the key.
i am on arch x86_64 and did install other AUR packages successfully before.
I am currently trying to install seamonkey, which pulls the dependency Python-2.7.18 with the -s option.
I already did the following:
sudo pacman -Syu
sudo pacman-key --refresh-keys
gpg --refresh-keys
,which all ran without fatal errors, timeouts and no data errors on the pacman-key but it did say unchanged for some, so i guess it can get data? Can post the log if someone can tell me how, "sudo pacman-key --refresh-keys > ../../temp/pac.log" does not capture the errors.
Error is:
==> Erstelle Paket: seamonkey 2.53.15-1 (Mo 29 Mai 2023 13:50:16 CEST)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Prüfe Buildtime-Abhängigkeiten...
==> Empfange Quellen...
-> seamonkey-2.53.15.source.tar.xz gefunden
-> mozconfig gefunden
-> Python-2.7.18.tar.xz gefunden
-> Python-2.7.18.tar.xz.asc gefunden
==> Überprüfe source Dateien mit sha256sums...
seamonkey-2.53.15.source.tar.xz ... Erfolg
mozconfig ... Erfolg
Python-2.7.18.tar.xz ... Erfolg
Python-2.7.18.tar.xz.asc ... Übersprungen
==> Überprüfe Signaturen der Quell-Dateien mit gpg...
Python-2.7.18.tar.xz ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 04C367C218ADD4FF)
==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden!
Please excuse the german, the error translates to "[...] Unknown public signature 04C367C218ADD4FF \n ERROR: One or more PGP-signatures could not be verified!"
So, should i focus on the errors from pacman-key or do something else? How can i view the key 04C367C218ADD4FF? "gpg --list-key 04C367C218ADD4FF" says it is not a public key.
Last edited by screenfox (2023-05-29 13:29:50)
Offline
https://wiki.archlinux.org/title/Makepk … e_checking
As for the pacman-key errors, they're completely unrelated, but you should still fix whatever problem is there. Your attempt to redirect the errors to the log failed as you only redirected stdout, not stderr:
http://mywiki.wooledge.org/BashGuide/In … edirection
Last edited by Trilby (2023-05-29 13:22:22)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Online
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thank you all, this solved my problem.
Specifically:
gpg --search-keys <key id from validpgpkeys section>
Now i see the error message cut off part of the key id, hence i could not find it. So the solution is to look in the PKGBUILD / validpgpkeys section and use that id to resolve the key.
And sorry for misplacing the post, now i know there is an AUR section.
Offline