Your Linux Data Center Experts

As of November 1st, 2005, debian testing has finally switched to a new version of apt that uses gpg key signatures for secure verification of packages (see the announcement). Unfortunately, package updates released since the new year have been signed with a new key, causing some error messages when updating.

Here's the error message I saw when trying to apply the most recent updates:

# apt-get update
Get:1 http://mirrors.tummy.com testing Release.gpg [378B]
Hit http://mirrors.tummy.com testing Release
Hit http://mirrors.tummy.com testing/main Packages
Hit http://mirrors.tummy.com testing/main Sources
Fetched 378B in 0s (3567B/s)
Reading package lists... Done
W: GPG error: http://mirrors.tummy.com testing Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 010908312D230C5F
W: You may want to run apt-get update to correct these problems

After being frustrated by stale google results, I turned to the Technocrati blog search engine. Fortunately, someone has already figured out the fix.

As root run:

wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | apt-key add -

or, if you're using sudo:

sudo wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key add -

Have a happy and secure year!

comments powered by Disqus

Join our other satisfied clients. Contact us today.