Your message dated Sat, 28 Sep 2019 11:36:52 +0000
with message-id <[email protected]>
and subject line Bug#938396: fixed in ros-rosdistro 0.7.4-2
has caused the Debian Bug report #938396,
regarding ros-rosdistro: 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.)


-- 
938396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938396
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:ros-rosdistro
Version: 0.7.4-1
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:ros-rosdistro

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: ros-rosdistro
Source-Version: 0.7.4-2

We believe that the bug you reported is fixed in the latest version of
ros-rosdistro, 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.
Jochen Sprickerhof <[email protected]> (supplier of updated ros-rosdistro 
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: SHA512

Format: 1.8
Date: Sat, 28 Sep 2019 13:22:11 +0200
Source: ros-rosdistro
Architecture: source
Version: 0.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Jochen Sprickerhof <[email protected]>
Closes: 938396
Changes:
 ros-rosdistro (0.7.4-2) unstable; urgency=medium
 .
   * Drop Python 2 package (Closes: #938396)
Checksums-Sha1:
 bfe8c82958a5880afbf92797119bc6f82974c934 2206 ros-rosdistro_0.7.4-2.dsc
 95106b4ab52c864d7ff639c453845bd187e6921d 3572 
ros-rosdistro_0.7.4-2.debian.tar.xz
 5fdda3f6fcfea67fa1b487ca82add6557b75bf52 6546 
ros-rosdistro_0.7.4-2_source.buildinfo
Checksums-Sha256:
 caee1e0861d26d62cc089a32d83bb1269a090a3a2d2c25710a5abba307552ef2 2206 
ros-rosdistro_0.7.4-2.dsc
 f300ffe1e7f26407f67ba092331df20d33cbea35dfefdaceef709875cba0332a 3572 
ros-rosdistro_0.7.4-2.debian.tar.xz
 41b1631d73b288d3f98b1342d9c425849c0d45da2260a6bcc028774f2aa327b1 6546 
ros-rosdistro_0.7.4-2_source.buildinfo
Files:
 e70df63624e781f4a8147ce5bdce655a 2206 python optional ros-rosdistro_0.7.4-2.dsc
 04d17cbb520a80ce0fe5f3c628d7a93f 3572 python optional 
ros-rosdistro_0.7.4-2.debian.tar.xz
 cf1d07fc2b8ef8c2081dc902ffeb846c 6546 python optional 
ros-rosdistro_0.7.4-2_source.buildinfo

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

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl2PQm8ACgkQW//cwljm
lDPF/g/8DyKSx9O7W4SaQSVGCZ4FHmWWTWXXoolTHYsueCpFVvhE0ehUlTEQ/hwr
lJzE0CsqQ4Z1vpK9r94tNThHlm4w6TlUEYNb3pqIozFNwb3N8RhSjrv7xdIieo5L
iUroqkgvaUl8AvtM37+8/MizQmBN5O4mQmA0PoHuG5HiP6Rh6StQwUIOnNswT9dz
HgGsrq82gW/PZNU/5+DBpCq+R431X9qESxJhmeW9Q6uNTQgqEwI7IbOz8wlTl8Tj
RwVz/3rpy5jZl0dBbMTU9w6iw8VK963TAY+CttNGeNNJBN9feVFsILGQtivDAUlI
n6PsaOzVS3EekX51LbVAWxdSaILEOITA14Nob1dCvcy5Tv/EMXehiKlAq/0/AWox
sw6bvKP/c4EQJRc/5WMh1jbbL3iPIr3BRx9fxFujXQSMb/SY6x37jhyLe7ef2oc7
6idcde8LlqrXfPLcQc+S0F+mmWnrqchj6ga32GCyrYaTuUISDfkEDYMgYin3PsaH
Eit3KUXN/fOjG6R04JpZncBnTs1GV800VfLa6ouWFBswafNOdd8KNvau33iTehKK
2qhstoPeJtbWkvlcKSB2SQY2iivoJyhhqGS4TlW/HQPMf2ZAMu4hNlyKsIR5ACRq
W0XWQhsyz3YVZMN3Tb37wE8zl2p0GK3R1Cum7F6zrRT84UqxwXQ=
=OkQS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to