Archival of Jessie: where did jessie-updates went ?

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
Hi,

I just stumbled upon the fact that Jessie and Wheezy was removed from
the mirrors, except for the LTS. (cf.
https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html).
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
exception here.

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: 151.101.36.204 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: 151.101.36.204 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
date ?

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,
Pierre.

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Curt
On 2019-03-26, Pierre Fourès <[hidden email]> wrote:

> Hi,
>
> I just stumbled upon the fact that Jessie and Wheezy was removed from
> the mirrors, except for the LTS. (cf.
> https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html).
> 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
> exception here.
>
> 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: 151.101.36.204 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: 151.101.36.204 80]
>

For Jessie LTS "/etc/apt/sources.list should look like this one:"

 deb http://deb.debian.org/debian/ jessie main contrib non-free
 deb-src http://deb.debian.org/debian/ jessie main contrib non-free

 deb http://security.debian.org/ jessie/updates main contrib non-free
 deb-src http://security.debian.org/ jessie/updates main contrib non-free

 deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
 deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free

If that isn't your problem, sorry; it must mean I failed to read your post with
the necessary attention to detail.

https://wiki.debian.org/LTS/Using


Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
This is precisely what my problem is about. This is why I wondered
where jessie-updates/ went, or if https://wiki.debian.org/LTS/Using
was outdated since the archival of Jessie.

My "/etc/apt/sources.list" was :
> deb http://http.debian.net/debian jessie main
> deb http://http.debian.net/debian jessie-updates main
> deb http://security.debian.org/ jessie/updates main

I just replaced it verbatim with what you gaved me and here is what I get :

> Ign http://deb.debian.org jessie-updates InRelease
> Ign http://deb.debian.org jessie-updates Release.gpg
> Ign http://deb.debian.org jessie-updates Release
> Err http://deb.debian.org jessie-updates/main Sources
>   404  Not Found [IP: 151.101.36.204 80]
> Err http://deb.debian.org jessie-updates/contrib Sources
>   404  Not Found [IP: 151.101.36.204 80]
> Err http://deb.debian.org jessie-updates/non-free Sources
>   404  Not Found [IP: 151.101.36.204 80]
> W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/source/Sources  404  Not Found [IP: 151.101.36.204 80]
>
> W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/contrib/source/Sources  404  Not Found [IP: 151.101.36.204 80]
>
> W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/non-free/source/Sources  404  Not Found [IP: 151.101.36.204 80]
>
> E: Some index files failed to download. They have been ignored, or old ones used instead.


Le mar. 26 mars 2019 à 10:00, Curt <[hidden email]> a écrit :

>
> On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
> > Hi,
> >
> > I just stumbled upon the fact that Jessie and Wheezy was removed from
> > the mirrors, except for the LTS. (cf.
> > https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html).
> > 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
> > exception here.
> >
> > 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: 151.101.36.204 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: 151.101.36.204 80]
> >
>
> For Jessie LTS "/etc/apt/sources.list should look like this one:"
>
>  deb http://deb.debian.org/debian/ jessie main contrib non-free
>  deb-src http://deb.debian.org/debian/ jessie main contrib non-free
>
>  deb http://security.debian.org/ jessie/updates main contrib non-free
>  deb-src http://security.debian.org/ jessie/updates main contrib non-free
>
>  deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
>  deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
>
> If that isn't your problem, sorry; it must mean I failed to read your post with
> the necessary attention to detail.
>
> https://wiki.debian.org/LTS/Using
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
In the meantime of understanding what's happening with jessie-updates,
I removed the jessie-updates/ references in order to dig a little more
as I also require jessie-backports (which isn't anymore in the
mirrors, but is in the archive).

For the context, I have a multi-step process installing Jessie from
debootstrap on remote machines from their live rescue system. This
grants me that the base install of all my Debian instances is the same
accross our multiple server's providers (and is as I want and expect
it).

The first parts does it's job (albeit without jessie-updates) and it's
now time to add the backports to customise and finalize the install.

I just replaced :
> echo 'deb http://http.debian.net/debian jessie-backports main' >> /etc/apt/sources.list
with
> echo 'deb http://archive.debian.net/debian jessie-backports main' >> /etc/apt/sources.list

I now get the requirement to install apt-transport-https, which wasn't
required before. But even then, I get an 503 unavaible error while
trying to access the Packages of the backports from the archive. It's
seem here too I have miss-done or misunderstood something. But what
went wrong ?

Here is the console outputs :

root@...:/# apt-get update
Hit http://security.debian.org jessie/updates InRelease
Hit http://security.debian.org jessie/updates/main i386 Packages
Hit http://security.debian.org jessie/updates/main Translation-en
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

root@...:/# apt-get install apt-transport-https
[...]

root@...:/# apt-get update
Hit http://security.debian.org jessie/updates InRelease
Get:1 http://archive.debian.net jessie-backports InRelease [734 B]
Ign http://archive.debian.net jessie-backports InRelease
Hit http://security.debian.org jessie/updates/main i386 Packages
Get:2 http://archive.debian.net jessie-backports Release.gpg [734 B]
Ign http://archive.debian.net jessie-backports Release.gpg
Hit http://security.debian.org jessie/updates/main Translation-en
Get:3 http://archive.debian.net jessie-backports Release [734 B]
Ign http://archive.debian.net jessie-backports Release
Get:4 http://archive.debian.net jessie-backports/main i386 Packages [734 B]
Err http://archive.debian.net jessie-backports/main i386 Packages

Get:5 http://archive.debian.net jessie-backports/main Translation-en_US [734 B]
Get:6 http://archive.debian.net jessie-backports/main Translation-en
[734 B]
Get:7 http://archive.debian.net jessie-backports/main i386 Packages
[734 B]
Err http://archive.debian.net jessie-backports/main i386 Packages

Get:8 http://archive.debian.net jessie-backports/main Translation-en_US [734 B]
Get:9 http://archive.debian.net jessie-backports/main Translation-en
[734 B]
Get:10 http://archive.debian.net jessie-backports/main i386 Packages
[734 B]
Err http://archive.debian.net jessie-backports/main i386 Packages

Get:11 http://archive.debian.net jessie-backports/main Translation-en_US [734 B]
Get:12 http://archive.debian.net jessie-backports/main Translation-en
[734 B]
Get:13 http://archive.debian.net jessie-backports/main i386 Packages
[734 B]
Err http://archive.debian.net jessie-backports/main i386 Packages

Get:14 http://archive.debian.net jessie-backports/main Translation-en_US [734 B]
Get:15 http://archive.debian.net jessie-backports/main Translation-en
[734 B]
Get:16 http://archive.debian.net jessie-backports/main i386 Packages
[734 B]
Err http://archive.debian.net jessie-backports/main i386 Packages
  HttpError503
Get:17 http://archive.debian.net jessie-backports/main Translation-en_US [734 B]
Ign http://archive.debian.net jessie-backports/main Translation-en_US
Get:18 http://archive.debian.net jessie-backports/main Translation-en
[734 B]
Ign http://archive.debian.net jessie-backports/main Translation-en
Ign http://http.debian.net jessie InRelease
Hit http://http.debian.net jessie Release.gpg
Hit http://http.debian.net jessie Release
Hit http://http.debian.net jessie/main i386 Packages
Hit http://http.debian.net jessie/main Translation-en
W: Failed to fetch
http://archive.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages
 HttpError503

E: Some index files failed to download. They have been ignored, or old
ones used instead.

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Curt
In reply to this post by Pierre Fourès
On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
> This is precisely what my problem is about. This is why I wondered
> where jessie-updates/ went, or if https://wiki.debian.org/LTS/Using
> was outdated since the archival of Jessie.

Then I'm stumped, sorry; we'll have to wait for clearer and better
minds (than mine).

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
While still investigating on my backports problem, I just noticed the
wiki LTS/Using [1] has been updated. This seems the jessie-update/
should not be set anymore in the /etc/apt/sources.list.

However, I would like to know what it means and how to interpret it.
Like previously mentioned, does all updates have just vanished ? Or
does all updates have been integrated to the main jessie/ repository
as per the archival process ?

I realize I should maybe have posted this issue on debian-lts@ instead
of debian-user@. As it relate to an old distribution of Debian, this
maybe is more appropriate ?

[1] : https://wiki.debian.org/LTS/Using?action=diff&rev2=40&rev1=39


Pierre.

Le mar. 26 mars 2019 à 11:06, Curt <[hidden email]> a écrit :
>
> On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
> > This is precisely what my problem is about. This is why I wondered
> > where jessie-updates/ went, or if https://wiki.debian.org/LTS/Using
> > was outdated since the archival of Jessie.
>
> Then I'm stumped, sorry; we'll have to wait for clearer and better
> minds (than mine).
>

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Curt
In reply to this post by Pierre Fourès
On 2019-03-26, Pierre Fourès <[hidden email]> wrote:

> W: Failed to fetch
> http://archive.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages
>  HttpError503
>

When I go there in a browser (https://archive.debian.net/), I get:

 Service disabled!
 Unfortunately, this service is not available at this time. It is not
 known when its maintainer will be able to provide it again.
 This service is not provided by the Debian System Administration team
 but instead by an individual member of the Debian project.

 Please do not contact the DSA team with questions about this service.

> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
>


--
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Roberto C. Sánchez-2
On Tue, Mar 26, 2019 at 12:26:04PM -0000, Curt wrote:

> On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
>
> > W: Failed to fetch
> > http://archive.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages
> >  HttpError503
> >
>
> When I go there in a browser (https://archive.debian.net/), I get:
>
>  Service disabled!
>  Unfortunately, this service is not available at this time. It is not
>  known when its maintainer will be able to provide it again.
>  This service is not provided by the Debian System Administration team
>  but instead by an individual member of the Debian project.
>
Note that https://archive.debian.net and https://archive.debian.org are
two different sites/services.  You probably want the latter.

Regards,

-Roberto

--
Roberto C. Sánchez

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
In reply to this post by Curt
Thanks Curt,

Yauhen answered me an exemple who helped me spot a typo I made. The
archive shouldn't point at debian.net/ but at debian.org/, like
clearly mentionned in [1]. Doing so fixes both the "503 Service
Unavailable" error and the requirement to install the
apt-transport-https package. I thus could successfully reinstall my
Jessie instance. The backports works as expected (when well
configured).

Yauhen complete answer should soon appears on debian-user@ (he sent it
to me first by mistake, then re-sent it to the list). I copy paste him
in the meantime. He add something important to make all works. If not
set, apt-get still doesn't want to load the backports repository. I
wonder if it's meant to be a temporary fix or not ?

> The last one is actually expired. To work around it, you can create file /etc/apt/apt.conf.d/10no--check-valid-until with the following content:
> Acquire::Check-Valid-Until "0";

It now just feel strange to have the main source on http.debian.net
and the backports on http://archive.debian.org. I guess I will update
my two-stage procedure to converge in order to grab everything from
the archive. Or would it be advisable to still grab the non-backports
packages from the mirrors ? I ponder this both 1/ not to add avoidable
load to the archive server (who could be handled throught the mirrors
network), 2/ speed and bandwidth wise regarding the reinstallation of
my instances. What would be recommanded ?

My current /etc/apt/sources.list looks like this :
> deb http://http.debian.net/debian jessie main
> deb http://security.debian.org/ jessie/updates main
> deb http://archive.debian.org/debian jessie-backports main

Pierre.

[1] : http://archive.debian.org/debian/README


Le mar. 26 mars 2019 à 13:26, Curt <[hidden email]> a écrit :

>
> On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
>
> > W: Failed to fetch
> > http://archive.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages
> >  HttpError503
> >
>
> When I go there in a browser (https://archive.debian.net/), I get:
>
>  Service disabled!
>  Unfortunately, this service is not available at this time. It is not
>  known when its maintainer will be able to provide it again.
>  This service is not provided by the Debian System Administration team
>  but instead by an individual member of the Debian project.
>
>  Please do not contact the DSA team with questions about this service.
>
> > E: Some index files failed to download. They have been ignored, or old
> > ones used instead.
> >
> >
>
>
> --
> “Let us again pretend that life is a solid substance, shaped like a globe,
> which we turn about in our fingers. Let us pretend that we can make out a plain
> and logical story, so that when one matter is despatched--love for instance--
> we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves
>

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
In reply to this post by Roberto C. Sánchez-2
Thanks Roberto,

This indeed what my mistake. Hard not to make a typo while using
http.debian.net. By the way, Curt mention the use of
http://deb.debian.org instead of http://http.debian.net. Does one of
them supersede the other ? Is there some pointers to compare the both
service. I'm a bit lost in all this possibilities.

Pierre.




Le mar. 26 mars 2019 à 13:31, Roberto C. Sánchez <[hidden email]> a écrit :

>
> On Tue, Mar 26, 2019 at 12:26:04PM -0000, Curt wrote:
> > On 2019-03-26, Pierre Fourès <[hidden email]> wrote:
> >
> > > W: Failed to fetch
> > > http://archive.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages
> > >  HttpError503
> > >
> >
> > When I go there in a browser (https://archive.debian.net/), I get:
> >
> >  Service disabled!
> >  Unfortunately, this service is not available at this time. It is not
> >  known when its maintainer will be able to provide it again.
> >  This service is not provided by the Debian System Administration team
> >  but instead by an individual member of the Debian project.
> >
> Note that https://archive.debian.net and https://archive.debian.org are
> two different sites/services.  You probably want the latter.
>
> Regards,
>
> -Roberto
>
> --
> Roberto C. Sánchez
>

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
In reply to this post by Pierre Fourès
Yauhen's mail seems not to find its way towards debian-user@, so he
asked me to foward it. Here it is :


Le mar. 26 mars 2019 à 12:11, Yauhen Shulitski <[hidden email]> a écrit :

>
> The following repositories work for me:
>
> deb http://deb.debian.org/debian/ jessie main contrib non-free
> deb-src http://deb.debian.org/debian/ jessie main contrib non-free
>
> deb http://security.debian.org/ jessie/updates main contrib non-free
> deb-src http://security.debian.org/ jessie/updates main contrib non-free
>
> deb http://archive.debian.org/debian jessie-backports main
>
> The last one is actually expired. To work around it, you can create file /etc/apt/apt.conf.d/10no--check-valid-until with the following content:
>
> Acquire::Check-Valid-Until "0";
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Nicholas Geovanis-2
On Tue, Mar 26, 2019 at 8:06 AM Pierre Fourès <[hidden email]> wrote:
Yauhen's mail seems not to find its way towards debian-user@, so he
asked me to foward it. Here it is :

Le mar. 26 mars 2019 à 12:11, Yauhen Shulitski <[hidden email]> a écrit :
>
> The following repositories work for me:
>
> deb http://deb.debian.org/debian/ jessie main contrib non-free
....
> deb http://archive.debian.org/debian jessie-backports main
>
> The last one is actually expired. To work around it, you can create file /etc/apt/apt.conf.d/10no--check-valid-until with the following content:

I'm pretty sure that I encountered this in the past but I don't have any proof to hand.
IIRC when the release enters LTS the backports stop being augmented. Is that (still)
correct? Therefore there will be no repository for them. IIRC I once found a statement
to that effect in the debian wiki. But again my evidence is not right now available. 

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
Le mar. 26 mars 2019 à 14:20, Nicholas Geovanis
<[hidden email]> a écrit :
> I'm pretty sure that I encountered this in the past but I don't have any proof to hand.
> IIRC when the release enters LTS the backports stop being augmented. Is that (still)
> correct? Therefore there will be no repository for them. IIRC I once found a statement
> to that effect in the debian wiki. But again my evidence is not right now available.
>

This seems like a sound explanation. Would be nice to have it
confirmed or infirmed.

BTW, a similar issue [1] have been reported to debian-lts@. I linked
this thread and Bernie's thread in it. I hope we get a clear answer
about the jessie-updates/ impact.

[1] https://lists.debian.org/debian-lts/2019/03/msg00117.html

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Curt
On 2019-03-26, Pierre Fourès <[hidden email]> wrote:

> Le mar. 26 mars 2019 à 14:20, Nicholas Geovanis
><[hidden email]> a écrit :
>> I'm pretty sure that I encountered this in the past but I don't have any proof to hand.
>> IIRC when the release enters LTS the backports stop being augmented. Is that (still)
>> correct? Therefore there will be no repository for them. IIRC I once found a statement
>> to that effect in the debian wiki. But again my evidence is not right now available.
>>
>
> This seems like a sound explanation. Would be nice to have it
> confirmed or infirmed.

https://backports.debian.org/

 Backports are packages taken from the next Debian release (called "testing"),
 adjusted and recompiled for usage on Debian stable.

>From that I infer that jessie-backports are like woolly mammoths.  The old
bones may still be around somewhere, but the animals themselves are extinct.

> BTW, a similar issue [1] have been reported to debian-lts@. I linked
> this thread and Bernie's thread in it. I hope we get a clear answer
> about the jessie-updates/ impact.
>
> [1] https://lists.debian.org/debian-lts/2019/03/msg00117.html
>
>


--
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
Le mar. 26 mars 2019 à 16:21, Curt <[hidden email]> a écrit :
>
> https://backports.debian.org/
>
> > Backports are packages taken from the next Debian release (called "testing"),
> > adjusted and recompiled for usage on Debian stable.
>
> From that I infer that jessie-backports are like woolly mammoths.  The old
> bones may still be around somewhere, but the animals themselves are extinct.
>

Nice metaphor ! I admit it's playing with fire, but it might be
necessary on some situations. However, of what I understand, backports
are just packages from the release N+1 applied to the release. They
live within the life cycle of the N+1 release. They are not taken
totally out of the blue (in the sense that there are not from extinct
animals, but fully related to the N+1 release). For instance, the
packages in jessie-backports comes from stretch (who was then in
testing when the backports was first initiated for jessie). So IIRC,
major updates to stretch are then propagated to the backports in
jessie (within its lifecycle). You also have backports-sloppy, who
takes the jump of two release. But I never used theses. To big of a
stretch for me.

Thanks for your reference, because I still thought in the line of an
outdated policy that Debian expected to apply the LTS also to the
backports. It seems that it didn't worked out from the first
experiment in Squeeze so it was decided to put the backports in the
archive. This seems to be the reference Nicholas talked about. So now,
of course, if you're like me, bound to keep Jessie running while it's
in LTS lifespan while also depending on packages from jessie-backports
who are not maintained anymore, you've got to stretch yourself. Looks
likes this will eventually bumps our priorities to move everything to
stretch !

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Nicholas Geovanis-2

On Tue, Mar 26, 2019, 2:46 PM Pierre Fourès <[hidden email]> wrote: 
of course, if you're like me, bound to keep Jessie running while it's
in LTS lifespan while also depending on packages from jessie-backports
who are not maintained anymore, you've got to stretch yourself. Looks
likes this will eventually bumps our priorities to move everything to
stretch !

As of end of November, my employer didn't have any 9 production machines but were actively deploying 8 for new applications. I think jessie was pretty solid and there was no real need felt to move to the next release. They also had a few 7 servers chugging along. Is jessie a victim of its own success here?

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Roberto C. Sánchez-2
On Tue, Mar 26, 2019 at 11:12:04PM -0500, Nicholas Geovanis wrote:

>    On Tue, Mar 26, 2019, 2:46 PM Pierre Fourès <[1][hidden email]>
>    wrote: 
>
>      of course, if you're like me, bound to keep Jessie running while it's
>      in LTS lifespan while also depending on packages from jessie-backports
>      who are not maintained anymore, you've got to stretch yourself. Looks
>      likes this will eventually bumps our priorities to move everything to
>      stretch !
>
>    As of end of November, my employer didn't have any 9 production machines
>    but were actively deploying 8 for new applications. I think jessie was
>    pretty solid and there was no real need felt to move to the next release.
>    They also had a few 7 servers chugging along. Is jessie a victim of its
>    own success here?
>
I don't think that it is a victim of its own success.

It would be no different than if you were deploying Windows and decided
to continue using Windows Server 2012 R2, even though its mainstream
support ended 6 months ago, because it is solid and you do not feel the
need to move to the next release.

The fact is that everything in the technology world has a finite
lifetime.  Granted, some things, like zOS, AIX, HP/UX, tend to have much
longer lifetimes for a given release.  Yet, even those eventually reach
and end of support for each release.

Deploying a new system using an OS or major application platform release
that is past its standard supported release timeline is a risky
proposition at best.  Granted, the advantage here is that if you really
like Debian Jessie, you actually have the ability to find someone to
continue to support it for you for as long as you as you are willing to
pay for that.  You cannot do the same for Windows or commercial Unix
systems.

Regards,

-Roberto

--
Roberto C. Sánchez

Reply | Threaded
Open this post in threaded view
|

Re: Archival of Jessie: where did jessie-updates went ?

Pierre Fourès
In reply to this post by Pierre Fourès
Le mar. 26 mars 2019 à 13:45, Pierre Fourès <[hidden email]> a écrit :

>
> My current /etc/apt/sources.list looks like this :
> > deb http://http.debian.net/debian jessie main
> > deb http://security.debian.org/ jessie/updates main
> > deb http://archive.debian.org/debian jessie-backports main
>
> It now just feel strange to have the main source on http.debian.net
> and the backports on http://archive.debian.org. I guess I will update
> my two-stage procedure to converge in order to grab everything from
> the archive. Or would it be advisable to still grab the non-backports
> packages from the mirrors ? I ponder this both 1/ not to add avoidable
> load to the archive server (who could be handled throught the mirrors
> network), 2/ speed and bandwidth wise regarding the reinstallation of
> my instances. What would be recommanded ?

Here is my follow up to relate that I eventually took a decision on
this particular point. I will still keep http.debian.net for the
stable source of jessie as it is still active (as maintained in the
LTS), while using archive.debian.org for the backports in order to
emphasize the backports are archived and not maintained anymore.
Thankfully, I don't use the backports on every instances of jessie
currently running and this will help me prioritize which of them
should be upgraded first to stretch. This will look odd, but for a
good reason.