Update Ubuntu, NO_PUBKEY, GPG error, The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10

If you get the following NO_PUBKEY error

sjam@kh:~# sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-security InRelease
Get:2 http://debian.koha-community.org/koha stable InRelease [49.7 kB]
Err:2 http://debian.koha-community.org/koha stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10
Reading package lists... Done
W: GPG error: http://debian.koha-community.org/koha stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3C9356BBA2E41F10
E: The repository 'http://debian.koha-community.org/koha stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

sjam@kh:~# sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3C9356BBA2E41F10


Comments

Popular posts from this blog

Solution to Moodle Error: Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write.

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

(Solved) (Fixed )MariaDB Unmet Dependencies on Ubuntu 20.04.