Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I get a lot of this errors when runnong apt-get update command

Ign lenny/volatile/main Sources/DiffIndex
Ign lenny/volatile/contrib Sources/DiffIndex
Ign lenny/volatile/non-free Sources/DiffIndex
Hit lenny/updates/main Packages
Hit lenny/updates/contrib Packages
Hit lenny/updates/non-free Packages
W: GPG error: lenny/updates Release: The following signatures were invalid: KEYEXPIRED 1356982504
W: GPG error: lenny/volatile Release: The following signatures were invalid: KEYEXPIRED 1358963195
W: You may want to run apt-get update to correct these problems

Why can't I update? .. All this was done after running the upgrade command.

Here's my sources.list

deb lenny main contrib non-free
deb-src lenny main contrib non-free
deb lenny/updates main contrib non-fre
deb-src lenny/updates main contrib non
deb lenny/volatile main contrib non-fr
deb-src lenny/volatile main contrib no

All this with Debian GNU/Linux 6.0

share|improve this question

marked as duplicate by Michael Hampton, jscott, Dave M, Jacob, mdpc Feb 9 '13 at 0:16

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

I don't see any actual error. Are you referring to the GPG warnings? – mgorven Feb 8 '13 at 19:45
@mgorven yes all those warnings and the fact that it suggest to run update to correct. But I keep getting al that.. – AAlvz Feb 8 '13 at 19:49
Debian 6.0 is not Lenny, Lenny is 5.0. The GPG signatures for the lenny archive are expired, and since the arch is EOL, checking GPG won't work, and will probably not be updated. You have to disable checks, if you wnat to still use lenny. – Zoredache Feb 8 '13 at 19:51
@Zoredache So the best I can do is update my sources.list to squeeze ? – AAlvz Feb 8 '13 at 20:03

The key used to sign the archive probably got rotated. You need to update the package containing the archive keys:

sudo apt-get --allow-unauthenticated install debian-archive-keyring
share|improve this answer
I don't think this will help. Lenny is end of life, and I don't believe the debian-archive-keyring has, or will be updated to reflect updated keys. – Zoredache Feb 8 '13 at 19:55
up vote 0 down vote accepted

The problem was the Debian 6.0 and Lenny match. I just updated all to squeeze replacing the source.list with:

# main repo
deb squeeze main
deb-src squeeze main
deb squeeze/updates main
deb-src squeeze/updates main

And then upgraded.

It's all working better now.

share|improve this answer
You may want to consider tracking "stable" instead of "squeeze". Regardless, glad you resolved this. Be sure to mark your answer "accepted" when you are able. – jscott Feb 8 '13 at 21:10
@jscott, I don't really like using stable. If someone is asleep at the wheel when applying updates, they might do a release upgrade, when they only meant to apply security updates. – Zoredache Feb 8 '13 at 22:21
@Zoredache so is it better to keep squeeze rather than stable to have better control? – AAlvz Feb 9 '13 at 0:45

Not the answer you're looking for? Browse other questions tagged or ask your own question.