You are not logged in.
Hi,
I'm attempting to use the Arch way of modifying and building a kernel.
I'm following these two wiki articles:
How to build the linux kernel on Arch
How to create a patch
I'm stuck on running
makepkg --nobuild --nodeps
to fetch the source code. The error I get is
linux-6.9.8.tar ... FAILED (Unknown public key 38DBBDC86092693E)
linux-v6.9.8-arch1.patch.zst ... FAILED (Unknown public key B8AC08600F108CDF)
To make sure I had the newest keys I reset the keys and then ran
pacman-key --refresh-keys
. This did not change the error message. I did a google search for the first key and it appears to belong to GKH but shouldn't it then be fetched by the latter command?
I am aware that I could just add the key by hand but before I do that I'd like to understand why I have to do that when it seemingly is a key that belongs to someone as important and high up the 'food chain' as GKH.
Last edited by Sidekick (2024-07-29 12:49:15)
Offline
--skippgpcheck
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
pacman-key has nothing to do with this, pacman has nothing to do with this.
Online
@ugjka: that is not a solution
You'll have to import the gpg keys in your user keyring i.e. by doing a "gpg --import keys/gpg/*" or "gpg --recv-keys <key-id>".
Offline
pacman-key has nothing to do with this, pacman has nothing to do with this.
oh, ok. Thank you!
@ugjka: that is not a solution
You'll have to import the gpg keys in your user keyring i.e. by doing a "gpg --import keys/gpg/*" or "gpg --recv-keys <key-id>".
yeah, I found how to import it by hand I just didn't understand why that is neccessary, but Scimmia explained it. Thanks though!
Last edited by Sidekick (2024-07-29 12:46:45)
Offline