I already go this installed:

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

But i got an error whenupgrading 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?)


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.

  • 3
    Worth adding that these keys are upstream keys, not AUR maintainer keys. – jasonwryan Feb 23 '17 at 2:08
  • You're right. Fixed. :) – Mio Rin Feb 23 '17 at 12:39

gpg --recv-keys 8F0871F202119294

  • 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

  • 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! – Limited Atonement Apr 18 '19 at 17:38
  • that what fixed the issue.. thanks – dzgeek Jun 17 '19 at 8:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.