[Python-modules-team] Bug#880409: python-django: add Breaks: openstack-dashboard (<< 3:12)

Andreas Beckmann anbe at debian.org
Wed Nov 1 02:16:47 UTC 2017

On 10/31/2017 10:34 PM, Chris Lamb wrote:
> Hi Andreas,
>> Oh, #867254 was only filed for the "trivial" case in sid. But the
>> problem also occurs on upgrades from stretch (openstack-dashboard gets
>> triggered after python-django was upgraded and blows up), which is the
>> case we need the Breaks for.
>> https://piuparts.debian.org/stretch2buster/fail/openstack-dashboard_None.log
> Perhaps I'm missing something, but isn't there a solution in
> openstack-dashboard itself? (Pre-Depends...?)
> Again, it just feels really wrong to fix it here..

It would only be possible to fix this by adding
  Depends: python-django (<< 1:1.11)
to python-django-horizon in *stretch* which sounds even more wrong and
I'm not sure whether that would be approved by the SRM.

Currently there is no openstack-dashboard in buster, and upgrading from
stretch to buster fails if openstack-dashboard is installed in stretch.
The package will stay installed, but trigger processing (it has many
triggers on javascript packages to rebuild caches or whatever) will fail
after python-django got upgraded, see above linked piuparts log.

Even with openstack-dashboard 3:12.x (currently only in experimental and
compatible with python-django 1:1.11.x) available in buster we will
still need the Breaks in python-django to ensure a working upgrade ordering.

So perhaps even more correct would be to add a

    Breaks: python-django-horizon (<< 3:12)

to python-django. openstack-dashboard (from the same source package:
horizon) is just the user that exposes the bug, while the python module
seems to be the incompatible bit.


More information about the Python-modules-team mailing list