Originally published at: How to fix GPG NO_PUBKEY Error: "The following signatures couldn't be..."
You may occasionally encounter GPG errors during an apt-get update or apt-get upgrade when maintaining a Debian-based systems. These errors typically indicate that your system is missing one or more public keys required for verifying the integrity and authenticity of packages from its repositories. This guide will walk you through resolving “NO_PUBKEY” errors, ensuring your…
Out of curiosity, I tried the gpg --list-keys command and was surprised to get:
gpg: directory '/home/pi/.gnupg' created
gpg: keybox '/home/pi/.gnupg/pubring.kbx' created
gpg: /home/pi/.gnupg/trustdb.gpg: trustdb created
Should I be concerned?
1 Like
Good question. When you ran the gpg --list-keys command for the first time, GnuPG (GPG) initialized its environment because it was likely not used before on your system. There’s no need for concern.