Your message dated Tue, 24 Mar 2020 14:44:51 +0000
with message-id <e1jgknt-0001ll...@fasolo.debian.org>
and subject line Bug#937009: fixed in mercurial 5.3.1-1+exp1
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 ow...@bugs.debian.org
immediately.)


-- 
937009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mercurial
Version: 4.9-2
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: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 debian-pyt...@lists.debian.org mailing list.

--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 5.3.1-1+exp1
Done: Julien Cristau <jcris...@debian.org>

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 937...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <jcris...@debian.org> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 24 Mar 2020 15:21:35 +0100
Source: mercurial
Architecture: source
Version: 5.3.1-1+exp1
Distribution: experimental
Urgency: medium
Maintainer: Python Applications Packaging Team 
<python-apps-t...@lists.alioth.debian.org>
Changed-By: Julien Cristau <jcris...@debian.org>
Closes: 937009
Changes:
 mercurial (5.3.1-1+exp1) experimental; urgency=medium
 .
   * Use python3 (closes: #937009).
   * mercurial Provides python3-mercurial so extensions can depend on
     that instead of a hazardous versioned dependency.
   * Add Breaks on all extensions.  To be updated as we don't know what
     version will use python3.
   * Pull patches from upstream repo to fix python3.8 compat.
Checksums-Sha1:
 92cafdf91b0f60a025846eaa783f65553aed4ead 2802 mercurial_5.3.1-1+exp1.dsc
 1e71fd1ac5ddfde60ea9d3ed4eb145353bd7a913 60380 
mercurial_5.3.1-1+exp1.debian.tar.xz
Checksums-Sha256:
 17ab261591a316839e301c01ff358b3a0e8ffadf38ae52f85cf8e0e80ea7fafa 2802 
mercurial_5.3.1-1+exp1.dsc
 59cff162c357962294cac7bd26e7270fec4010ca35009b32c9a9543041d00df5 60380 
mercurial_5.3.1-1+exp1.debian.tar.xz
Files:
 509b36578d0e5abaf83763047f44c434 2802 vcs optional mercurial_5.3.1-1+exp1.dsc
 451b6cd31e383ac3d1a7a659c53bf2e7 60380 vcs optional 
mercurial_5.3.1-1+exp1.debian.tar.xz

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

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl56GVAUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z60WPQ/8D+rpzrtZK1ZQpKeQX9BUgGwnhj6z
VDl0XmJZhVsarpfJzyl4y8BPn5kN7EiJb4K4W8UPBpb4JEVAuzGAsyF8OwA8u95Y
ABZjHcLSQtsBSSfpUn7++iymvbG6C6jXwRrYyYD0RYR5fYRDHG4oYQM/6upKCfY3
sn+iBpvtHMOdF+5qngNIoR+D8GSPjg9DesImaDLhSWSaHcQ7+2+UbnwrxNr0otvF
8AolrvwuNRTLOARZwAIG+PMT16V7m3ZDA2RZtWKysjgjBec/qqPO2urVcXMQzuKW
YdhGaxzW2KlPrbCQIze6Q54gYFNVuYEAk0p9w3ANlDZRb5MOKel806zxvg0PMLwT
2zMHb7w+hJi87j+rEOwpznNpLu2ZWK5aJsqyE1PD8DVx976cVhUDHmrdjQN3zGSw
94TsxkMKQEhqYJfFbBDW6xeqP0oZm4E6xrsLOqv1PpSUiRex4pcVuj1G5vQ+IVcL
s8bYum1m+JIcOE1A6lPNG2LhWJrdEt7tPbJOwjah00OzrwWILHCqbo6/gVXoMhKs
uJ5u0DZ7cHxRZR8ec//ygBeq3odbq5zfy+0RyYj6K4Eru4oYDLsdn3D7lhXQc9Ze
N5HW0KXhPV54vQnTaLcQIUIibNDg2AVcDSTLr4HfXPgcnp4uikS0Fh2qlpFD4Kqs
Py3z3kvlWecab6Y=
=i1dX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to