1 Apr
2010
1 Apr
'10
6:17 a.m.
Hi Andy,
On 3/31/2010 6:23 PM, Andy Smith wrote:
On Wed, Mar 31, 2010 at 10:28:01AM +0900, Joseph
Heenan wrote:
Thanks for the thoughts. I do definitely have this new key in the apt
key list now, but still get the problem.
http://forum.nginx.org/read.php?31,69929,69929 suggests the uk archives
are still being signed with the old key and/or are out of date.
I've tried to switch my sources.list to volatile.debian.org, but it
seems my VPS tries to contact this over ipv6 and fails to connect. (I've
not deliberately enabled ipv6 on my VPS, but it seems to be getting an
ipv6 address from somewhere...)
Joseph
I seem to have started getting this error in the
last 24 hours:
W: GPG error: http://apt-cacher.lon.bitfolk.com lenny/volatile Release:
The following signatures were invalid: KEYEXPIRED 1269969909 KEYEXPIRED
1269969909 KEYEXPIRED 1269969909
W: You may want to run apt-get update to correct these problems
$ wget -qO - http://www.debian.org/volatile/lenny-volatile.asc | gpg --import -
gpg: key 6D849617: public key "Debian-Volatile Archive Automatic
Signing Key (5.0/lenny)" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
$ gpg --list-keys 6D849617
pub 2048R/6D849617 2009-01-24 [expires: 2013-01-23]
uid Debian-Volatile Archive Automatic Signing Key (5.0/lenny)
Looks like they generated a new key.