PDA

View Full Version : [ubuntu] a problem whit update



alis313
January 30th, 2009, 12:23 PM
alis313@Tux:~$ sudo apt-get update

Hit http://ir.archive.ubuntu.com intrepid-backports/multiverse Packages
Hit http://ir.archive.ubuntu.com intrepid-backports/main Sources
Hit http://ir.archive.ubuntu.com intrepid-backports/restricted Sources
Hit http://ir.archive.ubuntu.com intrepid-backports/universe Sources
Hit http://ir.archive.ubuntu.com intrepid-backports/multiverse Sources
Fetched 3400B in 37s (90B/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 60D11217247D1CFF
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 FE8956A73C5EE1C9
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 978228591BD3A65C
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 C5E6A5ED249AD24C
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 632D16BB0C713DA6
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 9BDB3D89CE49EC21
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 4874D3686E80C6B7
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 665F9AEFE1098513
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 5DC4E17435661D98
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 28A8205077558DD0
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 CA1F91146F087E5A
W: You may want to run apt-get update to correct these problems

odinb
January 30th, 2009, 04:30 PM
I get the same thing. Seems to be with the openoffice Repo, Do not get this message when I disable it.

mikhmv
January 30th, 2009, 04:50 PM
I have same problem

SmileManVesa
January 30th, 2009, 05:06 PM
same problem here

paranoid_humanoid
January 30th, 2009, 11:12 PM
i think something is new with the way ppas work and they all have to be signed now or something. i'm trying to map the pub_keys to their ppa pages so i could import their keys individually. this really sucks cause i have a lot of ppas in my list, but the message is really annoying since i "sudo apt-get update" a lot.

blazingnikons
January 30th, 2009, 11:36 PM
I'm having the same problem. When I try to check synaptic package manager or update manager, I get the following:


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 60D11217247D1CFF

Zeedok
January 30th, 2009, 11:55 PM
Someone has written a script which fixes the problem for me. You can find it here (http://ubuntuforums.org/showthread.php?t=1047743&page=5).

blazingnikons
January 31st, 2009, 12:15 AM
Someone has written a script which fixes the problem for me. You can find it here (http://ubuntuforums.org/showthread.php?t=1047743&page=5).
That didn't do anything. Besides, I've been able to update since then -- I think that issue was fixed a while back.

odinb
February 2nd, 2009, 05:06 PM
If you have not found a solution yet, here is some info:

Launchapad has added keys to all PPAs: http://news.launchpad.net/ppa/adding-a-ppas-key-to-ubuntu

Solution found elsewhere in these forums:

Issues with missing Public Keys?
Enter this command, replacing 247D1CFF with your NO_PUBKEY-key last eight digits from the error-message to import the key:
gpg --keyserver keyserver.ubuntu.com --recv 247D1CFF

Then add the key to your software sources, again, replace 247d1cff with the keynumber used in above command:
gpg --export --armor 247D1CFF | sudo apt-key add -

Then update your software sources:
sudo apt-get update

Done!

TCMuffin
February 8th, 2009, 09:34 PM
If you have not found a solution yet, here is some info:

Launchapad has added keys to all PPAs: http://news.launchpad.net/ppa/adding-a-ppas-key-to-ubuntu

Solution found elsewhere in these forums:

Issues with missing Public Keys?
Enter this command, replacing 247D1CFF with your NO_PUBKEY-key last eight digits from the error-message to import the key:
gpg --keyserver keyserver.ubuntu.com --recv 247D1CFF

Then add the key to your software sources, again, replace 247d1cff with the keynumber used in above command:
gpg --export --armor 247D1CFF | sudo apt-key add -

Then update your software sources:
sudo apt-get update

Done!

Awesome - thank you :)

LouisZepher
February 15th, 2009, 10:51 PM
If you have not found a solution yet, here is some info:

Launchapad has added keys to all PPAs: http://news.launchpad.net/ppa/adding-a-ppas-key-to-ubuntu

Solution found elsewhere in these forums:

Issues with missing Public Keys?
Enter this command, replacing 247D1CFF with your NO_PUBKEY-key last eight digits from the error-message to import the key:
gpg --keyserver keyserver.ubuntu.com --recv 247D1CFF

Then add the key to your software sources, again, replace 247d1cff with the keynumber used in above command:
gpg --export --armor 247D1CFF | sudo apt-key add -

Then update your software sources:
sudo apt-get update

Done!

Ditto, here. Thanks.

forger
February 15th, 2009, 11:33 PM
Here's a script that fixes ppa links and gets ppa keys:
http://ubuntuforums.org/showthread.php?t=1056099

KerryLB
March 6th, 2009, 03:18 AM
Thanks from me too Odinb! :)

mkrahmeh
April 12th, 2009, 10:17 PM
thx Odinb..it workt like a treat :)

brew1086
May 14th, 2009, 03:47 AM
Thanks odinb (http://ubuntuforums.org/member.php?u=334499) that did it for me too !!!! :)

OnOffPT
June 4th, 2009, 12:07 PM
That's perfect.
Thank you.

comicosmos
March 30th, 2011, 01:37 PM
If you have not found a solution yet, here is some info:

Launchapad has added keys to all PPAs: http://news.launchpad.net/ppa/adding-a-ppas-key-to-ubuntu

Solution found elsewhere in these forums:

Issues with missing Public Keys?
Enter this command, replacing 247D1CFF with your NO_PUBKEY-key last eight digits from the error-message to import the key:
gpg --keyserver keyserver.ubuntu.com --recv 247D1CFF

Then add the key to your software sources, again, replace 247d1cff with the keynumber used in above command:
gpg --export --armor 247D1CFF | sudo apt-key add -

Then update your software sources:
sudo apt-get update

Done!

Good. This solved my problem perfectly.:)

NZJem
July 11th, 2011, 01:24 AM
If you have not found a solution yet, here is some info:.....

July 2011 and this solution still works a treat. Thanks 10^6 :)

erikson879
August 24th, 2011, 09:51 PM
Awesome - thank you :)


The best jejejeje done!

farstrider
March 6th, 2012, 11:44 PM
If you have not found a solution yet, here is some info:

Launchapad has added keys to all PPAs: http://news.launchpad.net/ppa/adding-a-ppas-key-to-ubuntu

Solution found elsewhere in these forums:

Issues with missing Public Keys?
Enter this command, replacing 247D1CFF with your NO_PUBKEY-key last eight digits from the error-message to import the key:
gpg --keyserver keyserver.ubuntu.com --recv 247D1CFF

Then add the key to your software sources, again, replace 247d1cff with the keynumber used in above command:
gpg --export --armor 247D1CFF | sudo apt-key add -

Then update your software sources:
sudo apt-get update

Done!

Thanks, I know that this is pretty old but thanks nonetheless, I appreciate the help! :popcorn:

oldos2er
March 6th, 2012, 11:57 PM
Old thread is old. Closed.