Arch Linux

olive

Member

From: Belgium

Registered: 2008-06-22

Posts: 1,490

[SOLVED] makepkg and pgp signature

This topic has already been discussed but I can't find a solution. When I try to build a package (for example linux) with makepkg, I have the following error:

==> Verifying source file signatures with gpg...
    linux-3.18.tar ... FAILED (unknown public key 79BE3E4300411886)
    patch-3.18.2 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!

The only workaround I have been able to find is to disable the pgp check entirely with --skippgpcheck. I have tried (according to the wiki: https://wiki.archlinux.org/index.php/makepkg ).

Adding keyserver-options auto-key-retrieve in $HOME/.gnupg/gpg.conf -> no difference

gpg --recv-keys 79BE3E4300411886
gpg: keyserver receive failed: Address family not supported by protocol

I am quite unfamiliar with gpg, but isn't there a simple way to just have makepkg working?

Last edited by olive (2015-01-22 14:07:29)

Lone_Wolf

Forum Moderator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,971

Re: [SOLVED] makepkg and pgp signature

$ gpg --recv-keys 79BE3E4300411886
gpg: key 00411886: public key "Linus Torvalds <torvalds@linux-foundation.org>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1
$ 

Works flawless here , which keyserver do you have in ~/.gnupg/gpg.conf ?

i use this one :    keyserver hkp://keys.gnupg.net

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

olive

Member

From: Belgium

Registered: 2008-06-22

Posts: 1,490

Re: [SOLVED] makepkg and pgp signature

@Lone_Wolf. It works now. In fact I had nothing at all, because I had never used gnupg. At the first attempt it fails but generate a workable default .gnupg directory. At the second attempt, it works correctly. I still find this gnupg behaviour a little buggy. It would make more sense to generate a correct .gnupg directory and use it directly.

Last edited by olive (2015-01-22 14:11:57)