Your message dated Thu, 16 Jul 2020 20:42:12 +0000
with message-id <[email protected]>
and subject line Bug#937009: fixed in mercurial 5.4.1-2
has caused the Debian Bug report #937009,
regarding mercurial: 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 [email protected]
immediately.)


-- 
937009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937009
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:mercurial
Version: 4.9-2
Severity: normal
Tags: sid bullseye
User: [email protected]
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 [email protected] 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:mercurial

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 [email protected] mailing list.

--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 5.4.1-2
Done: Sandro Tosi <[email protected]>

We believe that the bug you reported is fixed in the latest version of
mercurial, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <[email protected]> (supplier of updated mercurial 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 16 Jul 2020 15:05:37 -0400
Source: mercurial
Architecture: source
Version: 5.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 
<[email protected]>
Changed-By: Sandro Tosi <[email protected]>
Closes: 937009 948610
Changes:
 mercurial (5.4.1-2) unstable; urgency=medium
 .
   * Upload to unstable, switch to python3; Closes: #937009, #948610
Checksums-Sha1:
 1ef57565bd487383036a9c0594ced91e223cad68 2503 mercurial_5.4.1-2.dsc
 09aaf096d8b17d8c264ad92f2bb679af4ebbac6c 62672 mercurial_5.4.1-2.debian.tar.xz
 900cb2b77631c0b4c593079bac4bdc10b16d4216 6876 
mercurial_5.4.1-2_source.buildinfo
Checksums-Sha256:
 eb3695ccf72fa9ee03fc4cfcf1b6159930a3cd646e7225c5cc2c524cecfd1869 2503 
mercurial_5.4.1-2.dsc
 65f64e81b99ce51ef51532aeef27f43131ae292d247046f193e629a1b9865e4d 62672 
mercurial_5.4.1-2.debian.tar.xz
 af7fb67afbf372eee30834163431b64fdf669ccab1ab4202589b6c1d65edefb6 6876 
mercurial_5.4.1-2_source.buildinfo
Files:
 926caa217d6462d07ff2e229a6daf1b5 2503 vcs optional mercurial_5.4.1-2.dsc
 6d37b669a47c02c15d279cc06aa24b72 62672 vcs optional 
mercurial_5.4.1-2.debian.tar.xz
 596d9b46212d0e99fe0931904902e0e8 6876 vcs optional 
mercurial_5.4.1-2_source.buildinfo

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

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl8QrtYACgkQh588mTgB
qU9X+xAAgG+2kzgfN6O2+uqlR7tB20HrlioN9ZMKfC4Dg8Q6HYILZQOEiydpl67a
ZVUmElPwYGzBxF2rafWJWpzZpGX3oOUjsYuZnm7lUNz9gMpPiWmSXkGScEYbczrC
WR+3rMOVYY9GUZmnplutS7RzKPPiuJoab+b34gi7J/YCcVolWxJ3HC654liJnVr5
CIcjLALZiklb+DH4dYRabEPBGhFgC/gOGHBFVAaXhSIicXnfKf/CHTx1oyqtOgAI
EiAmlOdv2sePd65W5jue7l/YGhEJWIaWMbbtlIzDgLilvBeZqTxHLoy6TZC860US
z4d/Ew84RHiAfvmdd1ElRxay8aIvLYEOuI9L2362IYG3KL71qtHoMbRdT3RbwJIS
IWbofVZTvz5gAWeWquDorV++2oLibmFbhs/12K6Lj2FhWCMMOTsUmJBkf3qnZ2sv
ecHN+cRxPSkMcMNdhI2tAr2WcvYrdZs6baEB9bqJvpK4/1A03itWTfJ4KiX/qSF1
DHhKcpQf9rWS2HevI2wm/hbzsKUGDq/388WgRq9gT2ehWMze5Mqi74xmb2VR5bOY
ed4/fVJiHJBLrH7n6Qkc0tewTNXYxrK5m4alhxVB2UE8piqn21qf2Nf/SiVV5V7S
vSQsJGUlmbuFohdW/Q4cKv+dBc+wSfaMhgnaH4OvB7wIUk2xljk=
=EICt
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to