PDA

View Full Version : [ubuntu] W: GPG error: http://ftp.debian.org etch Release: The following signatures couldn't



ammk
January 20th, 2009, 03:40 AM
Hi,

sorry if I wrong place to post..

I just add new repository. I follow from this https://help.ubuntu.com/8.04/add-applications/C/extra-repositories-adding.html

The problem is, when I go to Software System>Administration>Software Sources .. then I reload it...

Suddenly, the message like this is appeared:
W: GPG error: http://ftp.debian.org etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A70DAF536070D3A1 NO_PUBKEY B5D0C804ADB11277

I just google it to find the solutions.. I found one... here: http://osterman.com/wordpress/2007/09/08/debian-apt-get-update-fails-with-no_pubkey-a70daf536070d3a1

But the problem is still there...

What should I do?

Is it safe to run this command?:
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys A70DAF536070D3A1
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys B5D0C804ADB11277
gpg --armor --export A70DAF536070D3A1 | apt-key add -
gpg --armor --export B5D0C804ADB11277 | apt-key add -

*I get it from http://osterman.com/wordpress/2007/09/08/debian-apt-get-update-fails-with-no_pubkey-a70daf536070d3a1

Thank you..

zvacet
January 20th, 2009, 07:21 AM
gpg --keyserver hkp://subkeys.pgp.net --recv-keys B5D0C804ADB11277
gpg --export --armor B5D0C804ADB11277 | sudo apt-key add -

But it is not a good practice to have mixed repos.

seshomaru samma
January 20th, 2009, 09:04 AM
the link you posted just gives you an example of a new repository
the example is from Debian etch and not Ubuntu
you are not supposed to add "deb http://ftp.debian.org etch main"

what repos are you trying to add?

karim.rahim
June 19th, 2010, 06:42 PM
I have the same problem and I managed to fix one issue. However I still get
W: There is no public key available for the following key IDs:
9AA38DCD55BE302B

I added etch because I use g77.

It may not be good practice to mix repositories, but it is a good practice to not make g77 available in lucid?

Perfect Storm
June 19th, 2010, 06:49 PM
I have the same problem and I managed to fix one issue. However I still get
W: There is no public key available for the following key IDs:
9AA38DCD55BE302B

I added etch because I use g77.

It may not be good practice to mix repositories, but it is a good practice to not make g77 available in lucid?

Get it here; http://packages.ubuntu.com/hardy-updates/g77