Adrian, now people are closing these bugs thinking they are handling
the py2unversioned requests while they are also closing the py2removal
bugs, because you decided to merge them! While your intentions may
have been good, this was a mistake (as the 2 requests are *not* the
same) that will cause great consequences in tracking and handling the
py2removal process.

Now please: unmerge all the bugs you merged; close the ones that need
to be closed and leave the ones still pending open; next time make
sure to coordinate further action on the python2 removal process with
debian-python@ first

Regards,
Sandro

On Mon, Aug 3, 2020 at 3:21 AM Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the src:fvwm-crystal package:
>
> #945673: fvwm-crystal: Python2 removal in sid/bullseye
>
> It has been closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> 
> (reply to Vincent Bernat <ber...@debian.org>).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
> <ftpmas...@ftp-master.debian.org> (reply to Vincent Bernat 
> <ber...@debian.org>) by
> replying to this email.
>
>
> --
> 966735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966735
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> ---------- Forwarded message ----------
> From: Debian FTP Masters <ftpmas...@ftp-master.debian.org>
> To: 966735-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 03 Aug 2020 07:18:57 +0000
> Subject: Bug#966735: fixed in fvwm-crystal 3.4.1+dfsg-2
> Source: fvwm-crystal
> Source-Version: 3.4.1+dfsg-2
> Done: Vincent Bernat <ber...@debian.org>
>
> We believe that the bug you reported is fixed in the latest version of
> fvwm-crystal, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 966...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Vincent Bernat <ber...@debian.org> (supplier of updated fvwm-crystal package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Format: 1.8
> Date: Mon, 03 Aug 2020 08:19:33 +0200
> Source: fvwm-crystal
> Architecture: source
> Version: 3.4.1+dfsg-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Vincent Bernat <ber...@debian.org>
> Changed-By: Vincent Bernat <ber...@debian.org>
> Closes: 966735
> Changes:
>  fvwm-crystal (3.4.1+dfsg-2) unstable; urgency=medium
>  .
>    * d/control: B-D on python2 (Closes: #966735)
>    * d/control: use debhelper-compat
>    * d/NEWS: rename from d/NEWS.Debian to d/NEWS
>    * d/control: update Vcs-* fields
>    * d/lintian: remove unused overrides
>    * d/NEWS: fix versions
> Checksums-Sha1:
>  5ff090b87289858f3698cf77db5569fd286e3ab5 1976 fvwm-crystal_3.4.1+dfsg-2.dsc
>  3dddca9fe374bead4a9c4a8d6bfb726b6e3a9f4a 5452811 
> fvwm-crystal_3.4.1+dfsg.orig.tar.gz
>  3bf38052669fc15a37a0aae502a1cba40dc64fe1 10312 
> fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz
>  9e4b0f36ce25a0259c6d1239da6c24a6139a6470 6079 
> fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo
> Checksums-Sha256:
>  752723b94db598ba4ac9196ba2e9e3ebf5d4b72ba764f937c7665abf5d473593 1976 
> fvwm-crystal_3.4.1+dfsg-2.dsc
>  7f0c2fe738d6c3ef37834a051baeafc5170feb9b10b1fb3ee0472727e574d6e4 5452811 
> fvwm-crystal_3.4.1+dfsg.orig.tar.gz
>  5871097d52d67a81dbaa26fd5c99ec1c1e203e747ab5568ce674673f68ae453f 10312 
> fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz
>  cfea15a2d05698f1b637ce2efa19e420a5ab191ae5d58056d1cee49a21677595 6079 
> fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo
> Files:
>  7b8798dfa1afc44c1513a504c9c71deb 1976 x11 optional 
> fvwm-crystal_3.4.1+dfsg-2.dsc
>  b6d0bae13067d6422388ba25bbaa55f9 5452811 x11 optional 
> fvwm-crystal_3.4.1+dfsg.orig.tar.gz
>  4086fa2d763c785d4ee9ce284cbe5cbc 10312 x11 optional 
> fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz
>  0d30296045e833d262b839790c17ffc5 6079 x11 optional 
> fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo
>
> -----BEGIN PGP SIGNATURE-----
>
> iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl8ntv4SHGJlcm5hdEBk
> ZWJpYW4ub3JnAAoJEJWkL+g1NSX5MC4P/RY9Y14OtcX0K29DW11ilVmqXVTiSbFU
> z5POkTIL3whKWpHRg/ZQbYrkDEwfJAlsuA83s5ZCH0NY1Xcj5BG0wxH509Qrcora
> nQpXGINbq9nHpU1GH1QBobVI0aC4ZqHqpNuKcvAPnGlhR9nEeckq9OO00LELwjPN
> 70PK37kvYZZl8PQ9eA/3qyvTPrBwshtVzSnWtRHRRxq0VsJAWcBlVOi/lMA89m+i
> 8LS7d2gtP1DPd2NKIx8waKGUX4trgGxH2Bak555IvE94AYQiqi8QJ5DNGe5wXYOD
> fBydh/MZcDSVxnnoNgeVOiZsJZHOP525iEO4/SQdesDx8fLX2PneVXB4rPRASp5U
> YM6knUq1enrFINEc4wpiM4qMnC1ZsugeHFLdWu+/tFwwZaPa6+g6/9/eVtQ53OrL
> 1Xc/YyB3EKCKJcq3iSIVuStvBP511UE3H3JZNxhyT+6/IlbvjOfXw0Rw64tKgkUF
> 0uzUXRvrK/NoHn+YFxNkxXJManHtiicYg5du5Tg2ebm25J+IMFkHvMxPbs5GF5LG
> In5qKtNED2mYRui4vyDtrPHYIvIKkf+4mPPBnKo9XfhequO6+6xudrbRks70ogF/
> N9fdoSVu4pTBNqx5H75VVEDv10x4A8HQ/qKf26mEus6BH7R3uhSlLhyASsZJ3gIa
> E2m0vlgNHu4M
> =AiTa
> -----END PGP SIGNATURE-----
>
>
> ---------- Forwarded message ----------
> From: Sandro Tosi <mo...@paradis.debian.org>
> To: mainto...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 27 Nov 2019 23:58:48 +0000
> Subject: fvwm-crystal: Python2 removal in sid/bullseye
> Source: fvwm-crystal
> Version: 3.4.1+dfsg-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
>
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests (the specific reason can be found searching this
> source package in
> https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
> Please stop using Python2, and fix this issue by one of the following
> actions.
>
> - Convert your Package to Python3. This is the preferred option.  In
>   case you are providing a Python module foo, please consider dropping
>   the python-foo package, and only build a python3-foo package.  Please
>   don't drop Python2 modules, which still have reverse dependencies,
>   just document them.
>
>   This is the preferred option.
>
> - If the package is dead upstream, cannot be converted or maintained
>   in Debian, it should be removed from the distribution.  If the
>   package still has reverse dependencies, raise the severity to
>   "serious" and document the reverse dependencies with the BTS affects
>   command.  If the package has no reverse dependencies, confirm that
>   the package can be removed, reassign this issue to ftp.debian.org,
>   make sure that the bug priority is set to normal and retitle the
>   issue to "RM: PKG -- removal triggered by the Python2 removal".
>
> - If the package has still many users (popcon >= 300), or is needed to
>   build another package which cannot be removed, document that by
>   adding the "py2keep" user tag (not replacing the py2remove tag),
>   using the debian-pyt...@lists.debian.org user.  Also any
>   dependencies on an unversioned python package (python, python-dev)
>   must not be used, same with the python shebang.  These have to be
>   replaced by python2/python2.7 dependencies and shebang.
>
>   This is the least preferred option.
>
> If there are questions, please refer to the wiki page for the removal:
> https://wiki.debian.org/Python/2Removal, or ask for help on IRC
> #debian-python, or the debian-pyt...@lists.debian.org mailing list.



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Reply via email to