Re: jessie-backports Release file expiry

To: debian-mirrors@lists.debian.org, mirrors@debian.org
Subject: Re: jessie-backports Release file expiry
From: Jain Johny <jain.johny@flipkart.com>
Date: Tue, 2 Apr 2019 14:39:30 +0530
Message-id: <[🔎] CABX7zJ0UdkJ1za2eEXR8=VSYjYqXR3UWO6fgEH_xNiHRFeTfiA@mail.gmail.com>
In-reply-to: <[🔎] CABX7zJ26+mBBt6rj=yam=0+7f=-Pvb8rDVeABjLwmZvJVS0jUA@mail.gmail.com>
References: <[🔎] CABX7zJ26+mBBt6rj=yam=0+7f=-Pvb8rDVeABjLwmZvJVS0jUA@mail.gmail.com>

+mirrors@debian.org

On Mon, Apr 1, 2019 at 10:49 AM Jain Johny <jain.johny@flipkart.com> wrote:

Hi,

When this repo was archived, shouldn't it be set not to expire?

$ curl -s http://archive.debian.org/debian/dists/jessie-backports/Release | grep Valid
Valid-Until: Tue, 19 Feb 2019 20:25:43 UTC

This is forcing users to use "check-valid-until=no" [1].

The wheezy-backports do not have this problem.

I am not sure if "check-valid-until=no" is the right way forward or will the repo get updated in the future to remove this expiry date. Can any of you please confirm?

Jain.

[1] https://unix.stackexchange.com/questions/508724/failed-to-fetch-jessie-backports-repository

Reply to:

Follow-Ups:
- Re: jessie-backports Release file expiry
  - From: Julien Cristau <jcristau@debian.org>

References:
- jessie-backports Release file expiry
  - From: Jain Johny <jain.johny@flipkart.com>

Prev by Date: jessie-backports Release file expiry
Next by Date: hello debian people
Previous by thread: jessie-backports Release file expiry
Next by thread: Re: jessie-backports Release file expiry
Index(es):
- Date
- Thread