Bug#595801: same thing in upgraded vm
On Wed, 22 Sep 2010, Peter Palfrader wrote:
> On Wed, 22 Sep 2010, Yaroslav Halchenko wrote:
>
> > just my .1 cents which might be misleading
> > > > I'm getting this same error in an VM that I just upgraded
> > > > from stable (Lenny) to testing (Squeeze). It won't go away.
> > > Of course not. But this is not a bug in snapshot.
> > > It's, if anything, a missing feature in apt.
> > or
> > http://en.wikipedia.org/wiki/Proxy_server#Intercepting_proxy_server
> >
> > which could be overcome with
> > -o Acquire::http::No-Cache=True
hedges@vm6:~$ sudo apt-get -o Acquire::http::No-Cache=True update
Get:1 http://ftp.us.debian.org testing Release.gpg [835B]
Get:2 http://security.debian.org testing/updates Release.gpg [835B]
Ign http://security.debian.org/ testing/updates/main Translation-en
Ign http://security.debian.org/ testing/updates/main Translation-en_US
Ign http://ftp.us.debian.org/debian/ testing/main Translation-en
Ign http://ftp.us.debian.org/debian/ testing/main Translation-en_US
Hit http://security.debian.org testing/updates Release
E: Release file expired, ignoring http://security.debian.org/dists/testing/updates/Release (invalid since 20d 12h 54min 0s)
hedges@vm6:~$ sudo aptitude -o Acquire::http::No-Cache=True update
Get:1 http://ftp.us.debian.org testing Release.gpg [835B]
Ign http://ftp.us.debian.org/debian/ testing/main Translation-en
Ign http://ftp.us.debian.org/debian/ testing/main Translation-en_US
Get:2 http://security.debian.org testing/updates Release.gpg [835B]
Ign http://security.debian.org/ testing/updates/main Translation-en
Get:3 http://ftp.us.debian.org testing Release [89.9kB]
Ign http://security.debian.org/ testing/updates/main Translation-en_US
Hit http://security.debian.org testing/updates Release
E: Release file expired, ignoring http://security.debian.org/dists/testing/updates/Release (invalid since 20d 12h 54min 13s)
> Wait. You aren't even using snapshot URLs. What are you doing in this
> bug report? :)
Sorry. This was the only place I found this error anywhere.
What package should I file it against? apt?
> What you have does indeed look like a broken proxy. It
> has nothing to do with the original issue reported here
> tho.
Nope, the network does not use a proxy, and it uses a simple
outbound route.
Are you sure your bug is really in snapshot, that there
isn't something else going on here?
Mark
Reply to: