GPG key imported successfully, package still won't build

Trying to install iozone, it has a GPG public key that wasn’t recognized, so I added it using gpg --recv-key with a custom key server.
This way it got imported successfully but the package still refuses to be built.
I tried refreshing the package lists and cleaning caches.

gpg --keyserver (link) --recv-key 8C004C2F93481F6B
gpg: key 8C004C2F93481F6B: 3 duplicate signatures removed
gpg: key 8C004C2F93481F6B: 3 signatures reordered
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 8C004C2F93481F6B: public key “Brent Timothy Saner <(link)>” imported
gpg: Total number processed: 1
gpg: imported: 1

Package manager says:

Cloning iozone build files…
Checking iozone dependencies…
Resolving dependencies…
Checking inter-conflicts…

Building iozone…
==> Making package: iozone 3.490-2 (Sun 30 Aug 2020 03:55:17 PM EEST)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
-> Found iozone3_490.tar
-> Found iozone3_490.tar.sig
==> Validating source files with sha512sums…
iozone3_490.tar … Passed
iozone3_490.tar.sig … Skipped
==> Verifying source file signatures with gpg…
iozone3_490.tar … FAILED (unknown public key 8C004C2F93481F6B)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build iozone

Why is it saved in ?

You should probably run gpg as user, not as root.

I use gpg always as user and pamac builds it then without any problems.


That didn’t cross my mind, I was indeed running gpg as root.

The package installed now. Thank you

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.