unknown public key 8F0871F202119294 on Arch Linux

Question

I already got this installed:

1 core/archlinux-keyring 20170104-1 [installed]
10 blackarch/blackarch-keyring 20140118-3 [installed]

But I get an error when upgrading libc++abi from AUR:

==> Verifying source file signatures with gpg...
    llvm-3.9.1.src.tar.xz ... FAILED (unknown public key 8F0871F202119294)
    libcxx-3.9.1.src.tar.xz ... FAILED (unknown public key 8F0871F202119294)
    libcxxabi-3.9.1.src.tar.xz ... FAILED (unknown public key 8F0871F202119294)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build libc++.
==> Restart building libc++abi ? [y/N]

How to resolve this? Is there a way to know which keyring I should install to solve this issue?

Stuart Cardall · Answer 1 · 2022-10-05T17:14:32.340

73

gpg --recv-keys 8F0871F202119294 (AUR)

the missing key needs to be added to your USER keyring

I did not need to trust the key for makepkg to finish the build.

~/.gnupg/gpg.conf also needed:

keyserver-options no-honor-keyserver-url

in my particular case

Missing keys for official Arch repos are normally missing an updated archlinux-keyring

edited Oct 05 '22 at 17:14

answered May 14 '17 at 01:39

Stuart Cardall

1,972

3

I was so proud of myself for remembering the command pacman-key --recv-keys KEY, and so sad when it didn't work. I see that it's my user keyring that needs adjusting, not the pacman keyring. Thanks! – lmat - Reinstate Monica Apr 18 '19 at 17:38
i also needed to create that conf file and add that line – austin Mar 18 '22 at 02:51
and i had to download and import their public key – austin Mar 18 '22 at 02:58

Mio Rin · Accepted Answer · 2017-02-23T12:37:23.957

14

Keys from AUR are not in the keyrings provided by the distributions' repositories.

You will need to find and add the AUR package/upstream keys manually, if you trust them.

Start by checking the PKGBUILD file of the package, then the comments in the AUR to see where/if to get and add the keys.

edited Feb 23 '17 at 12:37

answered Feb 23 '17 at 01:50

Mio Rin

3,040

score -1 · Answer 3 · edited Jul 31 '20 at 19:19

-1

Try: sudo pacman -U /path/to/file.tar.xz

Do that for all of the file types, then try your upgrade again.

edited Jul 31 '20 at 19:19

Jeff Schaller

67,283
35
116
255

answered Jul 31 '20 at 18:58

Germain Campman

1

unknown public key 8F0871F202119294 on Arch Linux

3 Answers3