[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian error

On 02-10 23:25, Munder Abbas wrote:
> E: Release file expired, ignoring
> http://linux.csua.berkeley.edu/debian/dists/squeeze/Release (invalid
> since 9d 8h 6min 10s)
> I dont know what this is

Most of the files in debian archive are signed by public keys,
to make sure proper content is delivered to end-users.
This also means that if needed users are handling most fresh
packages, including security upgrades (so some evil ftp admin
do not server you correctly signed package, but from last year).
You (or debian archive master server, which is very improbable)
have incorrect data and time setting on your system,
or mirror you are using was not synchronized with upstream mirrors.

It is also possible that someone (mirror administrator,
or someone in your network) is trying to perform some kind
of attack on your computer. Possibly it is giving you old Release
file becuase some important security upgrades are in effect now.
Please look at http://www.debian.org/security/#DSAS
and check if there are any package from last month which can affect you,
and for some reason was not upgraded.
But security updates are server by security.debian.org anyway,
so it should not be a problem IMHO.
And squeeze is too fresh probably to be there any upgrades
which will fix anythin.

I just tested, and I have same error as you.

Inspecting this release file gives:
  Suite: testing
  Date: Tue, 25 Jan 2011 14:17:25 UTC
  Valid-Until: Tue, 01 Feb 2011 14:17:25 UTC
  Description: Debian x.y Testing distribution - Not Released

but should be (today)
  Suite: stable
  Version: 6.0
  Date: Sat, 05 Feb 2011 12:29:37 UTC
  Description: Debian 6.0 Released 05 February 2011

Valid-Until was given becuase of prepared change for this in squeeze release cycle.

So i blame server admin. Just switch to http://cdn.debian.net/debian/
temporarly. Conntact admin if you can.

Witold Baryluk
JID: witold.baryluk // jabster.pl

Attachment: signature.asc
Description: Digital signature

Reply to: