Re: what about jessie backports ?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 2 May 2019 16:15:45 +0200
Alexander Wirt <formorer@formorer.de> wrote:
> On Thu, 02 May 2019, andrew glaeser wrote:
>
> It doesn't exist anymore.
>
> https://lists.debian.org/debian-backports-announce/2018/07/msg00000.html
>
> Alex
>
debian-backports@lists.debian.org> With jessie entering LTS we are following
up with shutting down
> jessie-backports (and jessie-backports-sloppy). We deprecated LTS
> support for backports already with the release of stretch, and a thread
> that we started on debian-backports about it didn't raise any new ideas
> how to make this working, so if you are using backports on jessie we
> suggest you to take this as a strong recommendation to finally do the
> upgrade to stretch.
>
Personally I used jessie-backports until some time ago, but then found
yesterday, that the repositories are not workable anymore..
I would have expected, that backports for a particular release are not
deprecated before the release becomes old-oldstable.
> Almost 2000 packages were uploaded to jessie-backports during its life
> cycle, and nearly 100 to jessie-backports-sloppy. We thank all the
> contributors for their continued effort to keep these package in a good
> shape, which added to the usefulness of the Debian ecosystem.
>
> The suites will soon be moved to the archive, no new upload will get
> processed, and it is planned to get removed from the regular mirror
> network to reduce confusion about continuing support of it.
I currently cannot upgrade the host to Stretch because of this issue with
Hugin:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927851
> hugin: performance in finding image control-points is quite poor
This has been troubling me since the stretch-release.
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCXMwZQQAKCRDn6sEfJS3n
C1rZAJ9nGIUa75061bIfz19odqJvcwdvkACfVKl5gmoodJK9Nsx0xvElbA8AAAA=
=YKP9
-----END PGP SIGNATURE-----
Reply to: