Apt-get. GPG error.
From MyWiki
(Difference between revisions)
m (Protected "Apt-get. GPG error." [edit=sysop:move=sysop]) |
(Updated with a better way of doing it using gpg) |
||
| Line 1: | Line 1: | ||
| - | apt-get. | + | I found a [http://muzso.hu/2007/05/25/how-to-fix-no_pubkey-errors-in-apt-get-update-operations better way to do it] that I originally thought would be the way. |
| + | |||
| + | So, what I wanted to fix was this: error message when I was trying to do <tt>apt-get update</tt> on a system that was quite old by then: | ||
GPG error: http://http.us.debian.org sid Release: The following | GPG error: http://http.us.debian.org sid Release: The following | ||
| Line 5: | Line 7: | ||
available: NO_PUBKEY 010908312D230C5F | available: NO_PUBKEY 010908312D230C5F | ||
| + | To fix it I run: | ||
| - | + | gpg --keyserver subkeys.pgp.net --recv 010908312D230C5F | |
| - | + | gpg --export --armor 010908312D230C5F | apt-key add - | |
| + | |||
| + | Then: | ||
| - | |||
apt-get update | apt-get update | ||
| + | |||
| + | NOTE: Some people said that they had to use a different key server (for example wwwkeys.eu.pgp.net). | ||
Revision as of 11:32, 15 March 2010
I found a better way to do it that I originally thought would be the way.
So, what I wanted to fix was this: error message when I was trying to do apt-get update on a system that was quite old by then:
GPG error: http://http.us.debian.org sid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
To fix it I run:
gpg --keyserver subkeys.pgp.net --recv 010908312D230C5F gpg --export --armor 010908312D230C5F | apt-key add -
Then:
apt-get update
NOTE: Some people said that they had to use a different key server (for example wwwkeys.eu.pgp.net).
