You are not logged in.
Here is how to reproduce the problem:
Create a chroot
$ export CHROOT=/home/me/arch_builds
$ mkarchroot $CHROOT/root base-devel
Download a package
$ asp checkout zsh
$ cd zsh/repos/extra-x86_64
Make the package
$ makechrootpkg -cr $CHROOT
# (usual output...)
==> Verifying source file signatures with gpg...
zsh-5.9.tar.xz ... FAILED (unknown public key ACF8146CAE8CBBC4)
zsh-5.9-doc.tar.xz ... FAILED (unknown public key ACF8146CAE8CBBC4)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Could not download sources.
How strange, let me update archlinux-keyring
$ arch-nspawn $CHROOT/root pacman -Syu archlinux-keyring
# (say Yes)
# (usual output... until...)
gpg: Warning: using insecure memory!
==> Appending keys from archlinux.gpg...
gpg: Warning: using insecure memory!
gpg: Warning: using insecure memory!
# (same warning many many times)
gpg: Warning: using insecure memory!
==> Updating trust database...
gpg: Warning: using insecure memory!
gpg: next trustdb check due at 2022-08-09
==> Updating trust database...
gpg: Warning: using insecure memory!
gpg: next trustdb check due at 2022-08-09
I also tried resetting with pacman-key --init etc... But I always get the same warning. It doesn't say that it fails, but given the above problem it looks suspicious. If I run
$ arch-nspawn $CHROOT/root pacman-key --refresh-keys
I get the same warning many times and also
==> ERROR: Could not update key: 6BC26A17B9B7018A
The warnings and the problem might however be unrelated. Indeed I get the same error if I run makepkg plain and simple even though pacman on my main system doesn't give those warning.
Last edited by mane.andrea (2022-07-19 07:44:01)
Offline
Offline
Thanks, I learned something.
But what about the warnings? Is it ok to ignore them?
Offline
The warnings are from gpg when pacman's keyring is updated. Pacman's keyring only contains public keys.
Offline
I understand
Offline