diehn.net/blog

Got this the other day when I tried to update the package lists on one of our Debian Etch servers:

mdiehn@imlcvs:~$ sudo aptitude update
Get:1 http://security.debian.org etch/updates Release.gpg [189B]   
.
.
.
W: GPG error: http://security.debian.org etch/updates Release: The following
signatures were invalid: BADSIG A70DAF536070D3A1 Debian Archive Automatic
Signing Key (4.0/etch) <ftpmaster@debian.org>

W: Couldn't stat source package list http://security.debian.orgetch/updates/main Packages
(/var/lib/apt/lists/security.debian.org_dists_etch_updates_main_binary-i386_Packages)
- stat (2 No such file or directory)

W: Couldn't stat source package list http://security.debian.orgetch/updates/main Packages
(/var/lib/apt/lists/security.debian.org_dists_etch_updates_main_binary-i386_Packages)
- stat (2 No such file or directory)

W: You may want to run apt-get update to correct these problems

So, I went googling and found not too much. I did find two posts (see below) suggesting that I install a package named debian-archive-keyring. It was already on the system and I wondered if maybe it’d been corrupted somehow. So I reinstalled it and that seems to have solved the problem. Here’s what I used to do the reinstallation:

sudo apt-get install debian-archive-keyring --reinstall

Seems to have worked. Now, if only I can get through the congestion on our network here so I can download the new kernel and samba packages…. 🙂

Here are those two posts I referenced above:

1. http://changelog.complete.org/posts/496-How-to-solve-The-following-packages-cannot-be-authenticated.html
2. http://www.debianhelp.org/node/6150

The second was the real help as it describe troubles closest to my symptoms.