Hi Ondřej, (please Cc, I am not subscribed to debian-devel)
thanks for your work on the Python2 removal. On Mon, 11 Nov 2019, Ondřej Nový wrote: > We are going to raise the severity of the py2removal bugs to "serious" > in several steps. In the ... Could you please give a time line of how you are planning to proceed? The next Debian release is still about 1.5 years away (extrapolating from the last N releases), so I don't see any extreme urgency to purge Debian from Py2 packages *now* at a time when it is even still supported? Do you have any timeline? Plans beside "...we are going to raise ...remove..."? I would strongly suggest to wait till january at least to start this process, upstream authors might wait till the last moment ... Furthermore, > We will also then file bug reports against ftp.debian.org to remove > such packages from unstable. We are going to do this semi- I think requesting the removal of packages that you are **not** maintaining is - to be polite - a bit unconventional (at least). This remains at the discretion of the maintainer as far as I remember. > All dependency fields in debian/control and debian/tests/control must > also be updated to stop using the unversioned python Are all you "must" statements "policy decisions"? Or your personal wish list items? Thanks Norbert (again, please CC, I am not subscribed to debian-devel) -- PREINING Norbert http://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
