Re: Proposal on how to proceed with Python 2 removal from bullseye

2020-01-06 Thread Sandro Tosi
On Sun, Dec 22, 2019 at 5:58 AM Simon McVittie wrote: > > On Wed, 18 Dec 2019 at 01:08:11 -0500, Sandro Tosi wrote: > > let me know if this makes sense or additional changes are required. > > #942941 in src:dbus-python was bumped to serious because: > > python-dbus-tests is a module and has 0

Re: Proposal on how to proceed with Python 2 removal from bullseye

2019-12-22 Thread Simon McVittie
On Wed, 18 Dec 2019 at 01:08:11 -0500, Sandro Tosi wrote: > let me know if this makes sense or additional changes are required. #942941 in src:dbus-python was bumped to serious because: > python-dbus-tests is a module and has 0 external rdeps or not in testing Please could you give

Re: Proposal on how to proceed with Python 2 removal from bullseye

2019-12-17 Thread Sandro Tosi
> 1) all Python 2 removal bugs *can* be raised to RC level by the > maintainers of the packages they belong to, but: > > 2) maintainers of non-key packages should carefully consider the > backslash for their transitive reverse (normal, build and test) > dependencies before raising the bug severity

Proposal on how to proceed with Python 2 removal from bullseye

2019-12-14 Thread Paul Gevers
Dear all, TL;DR: as the subject suggests, proposal included, although not fully aligned with others. On 08-12-2019 20:55, Sandro Tosi wrote: > there seems to be disagreement on how to proceed, so for the time > being i suspended the severity bump part of the py2removal tracking > script. let me