Archival of Jessie: where did jessie-updates went ?
- Date: Tue, 26 Mar 2019 09:50:55 +0100
- From: Pierre Fourès <pierre.foures@xxxxxxxxx>
- Subject: Archival of Jessie: where did jessie-updates went ?
I just stumbled upon the fact that Jessie and Wheezy was removed from
the mirrors, except for the LTS. (cf.
I still currently use Jessie and my automated install build just broke
this morning. I only use i386 and amd64, so I'm concerned by the LTS
If I understand well, all I need should then stay in the mirrors. But
the lookup to jessie-updates/ break the script.
> Err http://http.debian.net jessie-updates/main i386 Packages
> 404 Not Found [IP: 184.108.40.206 80]
> Fetched 1,041 kB in 3s (324 kB/s)
> W: Failed to fetch http://http.debian.net/debian/dists/jessie-updates/main/binary-i386/Packages 404 Not Found [IP: 220.127.116.11 80]
I'm note sure what I should do about it, as this folder is neither in
the mirrors nor the archive.
It just seems to have disappeared. Also, when I look at
https://packages.debian.org/jessie-updates/ there is no updates listed
anymore. Where did the updates went ? What does this mean ?
However when looking at https://wiki.debian.org/LTS/Using
documentation, it stipulate the use of jessie-updates. Is it out of
I'm not sure how to interpret all of this. This is the first time I
encounter the archival (thus the removal of the -updates/ packages) on
instances I still have to reinstall periodically. Does all updates
have just vanished ? Or does all updates have been integrated to the
main jessie/ repository as per the archival process ? Thus, does this
means I just have to remove the occurrence of jessie-updates/
repositories in my configurations files ?
I'm currently trying the reinstall the instance with removing the
reference to jessie-updates (ie: http://http.debian.net/debian
jessie-updates main). Nonetheless, I would like some feedback to
confirm I'm doing the right thing, just to be sure I won't skim over
the jessie-updates/ packages.
One the side note, I still use the Wheezy distribution on some old
instances. I will have to reinstall at least on instance of them in
the future. I guess the way to handle the wheezy-updates/ case will be
the same as the jessie-updates/ one. Except for this previous specific
case, if I understand well, I just have to replace in my scripts
"http://http.debian.net/debian wheezy main" with
"http://archive.debian.org/debian/dists/ wheezy main". Am I right on
this one ?
Thanks for your time,