Your message dated Sun, 26 Jan 2020 21:21:01 +0000
with message-id <e1ivpl3-000irn...@fasolo.debian.org>
and subject line Bug#937422: fixed in pyenchant 2.0.0-3
has caused the Debian Bug report #937422,
regarding pyenchant: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
937422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyenchant
Version: 2.0.0-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.  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 the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects <bug number of blocking py2removal bug> + src:pyenchant

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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.

--- End Message ---
--- Begin Message ---
Source: pyenchant
Source-Version: 2.0.0-3

We believe that the bug you reported is fixed in the latest version of
pyenchant, 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 937...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <mo...@debian.org> (supplier of updated pyenchant 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: Sun, 26 Jan 2020 16:01:44 -0500
Source: pyenchant
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski <pi...@debian.org>
Changed-By: Sandro Tosi <mo...@debian.org>
Closes: 912964 937422
Changes:
 pyenchant (2.0.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #937422, #912964
Checksums-Sha1:
 1e7317bfcfd22e406b4fde67c9728ace6bddb01e 2058 pyenchant_2.0.0-3.dsc
 67c2c3219fe2f5925ebca112008b75e2f0bec808 5684 pyenchant_2.0.0-3.debian.tar.xz
 b1bea25b98d2ddb26d8b9eb62d17b4c6a5b6f564 7304 
pyenchant_2.0.0-3_source.buildinfo
Checksums-Sha256:
 154d2a5425071d05159578dfe36e0e596cddea59dca451d2b6d85040ab0449a8 2058 
pyenchant_2.0.0-3.dsc
 c0bbaf357e86800d6b0af6267cf556e889e6ba1df86f0d1126c2ff74e5a6ecd3 5684 
pyenchant_2.0.0-3.debian.tar.xz
 7f6b9ad333dbe7b9c2f0aebd56384439ab8489f34b6668fada96940b0a187a9f 7304 
pyenchant_2.0.0-3_source.buildinfo
Files:
 1e4e4702962f0bade268182d95b1ceb9 2058 python optional pyenchant_2.0.0-3.dsc
 d4e877b1ef14572b1232f444f48dc51e 5684 python optional 
pyenchant_2.0.0-3.debian.tar.xz
 5ff9821f05d3e6fc9cfec496c58ad1ab 7304 python optional 
pyenchant_2.0.0-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4t/qgACgkQh588mTgB
qU/z1RAA2vXh5QoYYr+2tax5BU3WQ6fJ4D8CKHSjY21H3G0wDtSsTdN+NKIvicag
p4AXQ5POjbaeg/K+sdOdY+Q6vAubmfDkaQsmbYA60/h1DKSlNR9jarAwIu7elMAy
M9P1NBWRzsBB6qFKyT6b75aZCTxpIzjv+FGqo+GRy7LoIJok/JuspQYGJhoXbpW6
3gxN6S92wCSWwfZTfPTgLshQo3XVrP9OXBgsjKUv23v5JRPTO2Ab38V8Z2toySz7
ZlDSo4TUpvfPrCRvR4p1cTUw1w5/CNS3TMFa56SPvxwIunj6eVJexFXBiZnTvxSY
ox9iKJ+Atb2RA0ZyeZUbQU/3UQEOo2MVuloYyaCPa6Amd4Y5OUWVif1Y9bIzo8Q1
70XtOL8BA+zDXlYxxzH0aFOF6kI14f3ImxqWDppQR4B/5qx+/zB+9OKoRWa9AU1Y
bjBr95J3/EDwWYhh2IxyRH//b5eaD/ZN/87HQXs5jocPqpG9mAwHxia6saGeoo7s
YP5qg6sCndlKeeMxjljuXjlOi36ePqrtJGHQfwFHgEm7m8Yyc4qqI3PvSInc5yib
C3hziVlW3eLlDhDtcAk5DpE4hfquYSY3j5GE/axUBBXGOaayq7Dgsxtthk+0YrfZ
sKFhEA0nnlPv6z3LxRvuQvBZvRz+7PKBeE2hpo5IgpMqkPW9NXs=
=S10t
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to