Andreas Beckmann <a...@debian.org> writes: > On 20/05/2021 11.07, Julien Cristau wrote: >> Do we know what specifically causes old python to be removed? > > buster: > > Package: python > Source: python-defaults > Version: 2.7.16-1 > Depends: python2.7 (>= 2.7.16-1~), libpython-stdlib (= 2.7.16-1), python2 (= > 2.7.16-1) > Pre-Depends: python-minimal (= 2.7.16-1) > > bullseye: > > Package: python2 > Source: python-defaults > Version: 2.7.18-2 > Depends: python2.7 (>= 2.7.18~), libpython2-stdlib (= 2.7.18-2) > Pre-Depends: python2-minimal (= 2.7.18-2) > > ==> python/buster is not co-installable with python2/bullseye > ==> python/buster must be removed to upgrade python2 > > Package: python2.7 > Version: 2.7.18-7 > Depends: python2.7-minimal (= 2.7.18-7), libpython2.7-stdlib (= 2.7.18-7), > mime-support > Breaks: libpython-stdlib (<< 2.7.18), python (<< 2.7.18), python-minimal (<< > 2.7.18), python-virtualenv (<< 1.7.1.2-2~), vim-athena (<< 2:7.3.547-4), > vim-gnome (<< 2:7.3.547-4), vim-gtk (<< 2:7.3.547-4), vim-nox (<< 2:7.3.547-4) > > The explicit versioned Breaks in python2.7 against unversioned > python packages are there to help apt making the right decision: > remove unversioned python and upgrade python2 to bullseye > (otherwise it would try to not upgrade python2/buster in order > to keep python/buster installed in quite a bunch of upgrade > scenarios) > > @apollon: > Would it be possible to build ganeti-2.16 in bullseye (with > reduced dependencies?) s.t. it depends on python2 instead of > python? Then it could be reintroduced into bullseye like buster > had ganeti-2.15 in addition to ganeti (2.16).
It would be possible, but that would also have to be done for at least python-simplejson, python-fdsend and possibly others. To be honest, I'd much prefer promoting upgrades via buster-backports for Ganeti, it's much more straightforward. Regards, Apollon
