Southend Linux Wiki Site

Aptitude Updates Errors & Howto resolve them

Installing packages from anything other than the main distribution repository can be fraught with difficulties, the problem can manifests itself when you run from the command line the command

#> sudo apt-get update

Your errors may look similar to this. ....
Hit http://packages.linuxmint.com felicia/community Packages
Hit http://packages.linuxmint.com felicia/romeo Packages
Fetched 8795B in 0s (10.3kB/s)
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9ED9A781DD9300F1
W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2BBD133164234534
W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C1FE1A7B426FF7FA
W: You may want to run apt-get update to correct these problems These errors occur because a specific Pgp encryption key is missing for the third party repository you have added you will seldom if ever see these errors when using any Ubuntu repository. However it can be very simple to resolve such errors.

#> sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com C1FE1A7B426FF7FA

You should note the key I have entered here which I have copied from the above list of errors bottom entry, from the console then add your own password and presto no more untidy annoying key signature errors repeat this command for each of the displayed errors by substituting the failed NO_PUBKEY No.

#> sudo apt-get update

Running the above command again and you will see no more Gpg errors.