Re: Maintaining intermediary versions in *-backports
On Wed, May 24, 2017 at 03:06:07PM +0100, Neil Williams wrote:
>...
> Upgrading 1.7 to 1.10 without going via 1.8 will break all packages
> with django as a dependency. That is not a "normal risk", that is RC -
> causes data loss.
Why is no RC bug filed against the version in stretch?
>...
> It is quite something else to say that NOBODY can upgrade existing
> installations from jessie because the critical package in
> jessie-backports has been removed.
>...
This is not an upgrade path documented in the current draft of the
release notes, and a package in backports being required for an
upgrade is simply wrong.
Based on what you say the only real options are:
- ship both 1.8 and 1.10 in stretch
- go back to 1.8 for stretch
As a side effect, either of these would permit 1.8 in jessie-backports
under the existing rules.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: