Your message dated Sat, 25 Jan 2020 04:49:28 +0000
with message-id <e1ivdnw-0009da...@fasolo.debian.org>
and subject line Bug#937271: fixed in pep8 1.7.1-9
has caused the Debian Bug report #937271,
regarding pep8: 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.)


-- 
937271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pep8
Version: 1.7.1-3
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:pep8

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: pep8
Source-Version: 1.7.1-9

We believe that the bug you reported is fixed in the latest version of
pep8, 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 pep8 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: Fri, 24 Jan 2020 23:26:56 -0500
Source: pep8
Architecture: source
Version: 1.7.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Sandro Tosi <mo...@debian.org>
Closes: 937271 940736
Changes:
 pep8 (1.7.1-9) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #937271
   * Drop transitional pep8 package; Closes: #940736
Checksums-Sha1:
 16b2d159a94af2cbbb3bed261faa90e587c755db 2034 pep8_1.7.1-9.dsc
 df9aa80933933f29a9348729d6e23dae3a94543c 4948 pep8_1.7.1-9.debian.tar.xz
 01e2bca78ac89bdeed97b2ff32c8aef102d2f61b 6317 pep8_1.7.1-9_source.buildinfo
Checksums-Sha256:
 b06e3176d64c0174ddfceed628773f7e5c22a719c8952e4951d49b7842b34be4 2034 
pep8_1.7.1-9.dsc
 742ffbb0ae0473e99d2d80d739b4b499709551e1635a937e7340e671b517dd4a 4948 
pep8_1.7.1-9.debian.tar.xz
 c876d0f3dc20377b2ab74b41401696b03f4496161832341e14383a80bb4e9329 6317 
pep8_1.7.1-9_source.buildinfo
Files:
 cd3dbc7bbf5a252c6034d7e09f1f63e5 2034 python optional pep8_1.7.1-9.dsc
 0989cbf9070d8ec94875b866802ccbf9 4948 python optional 
pep8_1.7.1-9.debian.tar.xz
 187184ebcb8f02728f72c823e9ba5898 6317 python optional 
pep8_1.7.1-9_source.buildinfo

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

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4rxF4ACgkQh588mTgB
qU83gg//Vl+yJKa66pBsPdupkNviLE0yl2o382SqwOIoz6N1jDJxah2DUuudorf5
QkXETRkmI9ykguDTbxHgksTX7qpQE4Fp796tysseqB4kbiaBba7+U/F/zYhIW2lL
HuGr+R4TR8tzFqqw68DlMAQ8sAMODKzk4wCIOUX4LXQ+E55cczaQk5zvfp4V+LiD
bWqM3UlGK5eRmSHj1IpIVEEYax9FYo9YL7IWpV+3MLJNNJwYvFuwCeQWOxrMp8Sl
mkZcbjL5zVWEJ9Guw5zc+ir8P7JwftXAQCPjnr/7/iVbXu7BF2m6deGrINXWoIC5
379ncHV8fan74Axe1YfDIjWRpsNgA24OXJf9AhFiqtCoAZUAX8yc9Usfi1ju59u6
JxNlogiGLrmsFpxTDJtep/lVEQF1Yl3W8mZBXF5AyPJjbsfRYQPidNhxsg7ulI/z
wREjCyKY4Tgbs+eIitpnog+KaTKylAAZp/ArLkJK2SjUTgmZRhWewABCCLv55gZr
bk8Jf/MPbRB8curBYyF5VfrXX7SKsB1Om2sZc4QqAwxZnSGQ/KK24a8a0JO313vE
oEpj/n5ejPXvjhDs3hBoQlBxkjFCueZWO4y77va0SvZB4vRguicJCzOdhZXmQthi
ht+fZIXk8zxf56NK/TAwd56WGTVhDV0MyGFeVdqQ+y159A8LGDA=
=ERea
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to