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

Re: expiration of jessie-backports Release files



On Wed, 03 Apr 2019, Vincent.Mcintyre@csiro.au wrote:

> Hi,
> 
> this seems to be a new issue with the Jessie release.
> 
> The issue:
> 
>   - in the Release file on archive.d.o [1] we have
>     Codename: jessie-backports
>     Date: Tue, 12 Feb 2019 20:25:43 UTC
>     Valid-Until: Tue, 19 Feb 2019 20:25:43 UTC
>     NotAutomatic: yes
> 
>   - in the Release file for wheezy-backports [2] we have
>     Codename: wheezy-backports
>     Date: Wed, 24 Jan 2018 08:51:34 UTC
>     NotAutomatic: yes
> 
> which causes apt to rightly complain that the Release file is out
> of date and refuse to use the package source.
> 
> However it would be useful to me to be able to access packages from
> that suite from time to time as we phase out our jessie machines.
> 
> Are there any plans to remove the Valid-Until lines from the
> archive.d.o copy of the Release and InRelease files and re-sign them?
No, thats the way its supposed to work, valid-until was added to indicate
that a release is out of support. Valid-until support in apt was added after
wheezy support, therefore it isn't a suprise that wheezy doesn't have that
header. 

Alex


Reply to: