Re: squeeze-backports archive repo "Release file expired"
On Wed, 21 Sep 2016, Niall Chapman wrote:
> On Tue, 2016-09-20 at 23:37 +0200, Alexander Wirt wrote:
> > On Tue, 20 Sep 2016, Niall Chapman wrote:
> >
> > > Hi,
> > >
> > > I've been trying to set up the "squeeze-backports" repo on an old server
> > > that I can't do a dist-upgrade on, but am hitting the following problem
> > > when I try to "apt-get update":
> > >
> > > E: Release file expired, ignoring
> > > http://archive.debian.org/debian-backports/dists/squeeze-backports/Release (invalid since 188d 18h 15min 13s)
> > >
> > > I notice that the Release file has a "valid until" field in it which
> > > corresponds to the "188d":
> > >
> > > "Valid-Until: Tue, 15 Mar 2016 21:20:23 UTC",
> > >
> > > ...but I also notice that there is no such field in the "etch-backports"
> > > repo for example, and I can run "apt-get update" using that repo with no
> > > error generated.
> > >
> > > It seems to me that it would be strange to have the all the files hosted
> > > in a repo on archive.debian.org but not be able to pull them using
> > > apt-get, especially seeing as the etch-backports repo seems to work
> > > fine, so I can only assume this is unintended behaviour.
> > >
> > > I've tried a few mirrors, and they all seem to be the same. It seems to
> > > me that there is a simple solution to this - remove the "valid until"
> > > field from the Release file, but I'm not sure exactly where or how to
> > > request this, so I hope this is the correct place to start. Can anyone
> > > help?
> > Thats by design. It is an archive and files are archived as they are. You
> > should not use those distributions anymore.
> >
> > Alex
>
> Hi Alex,
>
> Thanks for your reply.
>
> I realise that I "shouldn't" use those distributions any more, but I
> have a squeeze server that I cannot upgrade but which I need to be able
> to upgrade some packages on it and continue using, and I'm trying to
> find the most sensible way to do so.
>
> (Of course, I could download and install each .deb file manually, but it
> would be much easier if I could let apt-get sort out the dependencies
> for me rather than have to trudge through that manually...)
>
> I understand that the files have been put in "archive", but most of the
> repos are still functional, including the etch-backports repo (which is
> even older than the squeeze one), in addition to the main squeeze repo
> itself. Neither of those have a "valid until" field in their "Release"
> file.
>
> I can't think of any reason why the squeeze-backports repo should be any
> different than the others, or why it would be "by design" that I'm able
> to use the etch-backports repo which is even older?...
It is not different every newer repo will have have this header. It just
wasn't implemented for etch.
You can tell apt to ignore the header:
Acquire::Check-Valid-Until=false
Alex
Reply to: