Your message dated Wed, 24 May 2017 23:57:46 -0400
with message-id <1530639.3EspIQlAHj@kitterma-e6430>
and subject line Re: [Python-modules-team] Bug#863267: python-django: Upgrades
from jessie to stretch
has caused the Debian Bug report #863267,
regarding python-django: Upgrades from jessie to stretch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
863267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.10.7-1
Severity: serious
Control: block 847277 by -1
Control: block 863259 by -1
This bug is based on #847277, #863259, and the related
discussion on the debian-backports list.
If upgrading from 1.7 in jessie to 1.10 in stretch is not
fully supported unless upgrading through 1.8, then 1.8 is
required in stretch.
Either in addition to 1.10 (with properly supported and
documented 1.7 -> 1.8 -> 1.10 upgrade paths), or as 2:1.8
If lava-server is in a special situation due to doing
something very uncommon, then this bug should be closed
and the severity of #847277 set back to RC (with the likely
consequence that lava-server won't be part of stretch).
--- End Message ---
--- Begin Message ---
On Wednesday, May 24, 2017 07:01:38 PM Adrian Bunk wrote:
> Source: python-django
> Version: 1:1.10.7-1
> Severity: serious
> Control: block 847277 by -1
> Control: block 863259 by -1
>
> This bug is based on #847277, #863259, and the related
> discussion on the debian-backports list.
>
> If upgrading from 1.7 in jessie to 1.10 in stretch is not
> fully supported unless upgrading through 1.8, then 1.8 is
> required in stretch.
>
> Either in addition to 1.10 (with properly supported and
> documented 1.7 -> 1.8 -> 1.10 upgrade paths), or as 2:1.8
>
> If lava-server is in a special situation due to doing
> something very uncommon, then this bug should be closed
> and the severity of #847277 set back to RC (with the likely
> consequence that lava-server won't be part of stretch).
This bug is not at all correct. I don't know about LAVA, but Django upgrades
just fine.
Scott K
--- End Message ---
