There appears to be a bug in Debian’s key signing system. Depending on your apt sources you may run in to packages signed by a key that Debian doesn’t like. Annoyingly, these are Debian-signed packages, but unless you want to fix it, here is a workaround.<\/p>\n
http:\/\/non-us.debian.org is a repository signed with F1D53D8C4F368D5D, but Debian does not trust that key (because it is expired). Go figure.<\/p>\n
To resolve the irritating error:
\nW: GPG error: http:\/\/non-us.debian.org stable\/non-US Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY [some key]<\/p>\n
Do this:<\/p>\n
1) Make sure you have the newest keys from Debian the automagical way: 2) Update your keys manually:<\/p>\n 3) Try again. If it was indeed a key issued by Debian that you were missing, you should have it now. My guess is you have stumbled across packages signed by a key that Debian forgot to include in their trusted keys list.<\/p>\n 4) The Icky part<\/p>\n Now, not to rag on the Debian group, but the key I have been fighting with is F1D53D8C4F368D5D on non-us.debian.org. That key is expired which is why it is not distributed. No packages should be signed with it.<\/p>\n","protected":false},"excerpt":{"rendered":" There appears to be a bug in Debian’s key signing system. Depending on your apt sources you may run in to packages signed by a key that Debian doesn’t like. Annoyingly, these are Debian-signed packages, but unless you want to … Continue reading apt-key update<\/code>
\nThis will probably do nothing.<\/p>\n\n
wget [URL] -O - | apt-key add -<\/code> (replace [URL] with the link to the key, silly)<\/li>\n<\/ul>\n\n
apt-get install gnupg<\/code><\/li>\ngpg --keyserver keyring.debian.org --recv-keys [KEY]<\/code><\/li>\ngpg --armor --export [KEY] | sudo apt-key add -<\/code><\/li>\ngpg --export [KEY] >> \/etc\/apt\/trusted.gpg<\/code><\/li>\ngpg --list-keys<\/code><\/li>\n<\/ul>\n