Your message dated Sat, 26 Oct 2019 06:55:48 +0000
with message-id <[email protected]>
and subject line Bug#938375: fixed in ros-gencpp 0.6.2-3
has caused the Debian Bug report #938375,
regarding ros-gencpp: 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.)


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

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-gencpp
Source-Version: 0.6.2-3

We believe that the bug you reported is fixed in the latest version of
ros-gencpp, 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-gencpp 
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, 26 Oct 2019 08:36:46 +0200
Source: ros-gencpp
Architecture: source
Version: 0.6.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Jochen Sprickerhof <[email protected]>
Closes: 938375
Changes:
 ros-gencpp (0.6.2-3) unstable; urgency=medium
 .
   * Drop Python 2 package (Closes: #938375)
   * Bump policy versions (no changes)
   * simplify d/watch
Checksums-Sha1:
 db3e89d23451d68741ea101f22df1b9b38a8ebba 2107 ros-gencpp_0.6.2-3.dsc
 83a0ef943192909f4c92d51fbdd0c476d19b036a 3652 ros-gencpp_0.6.2-3.debian.tar.xz
 87866f2d5fe4937b25ff67bf212f8b5d76f13819 8031 
ros-gencpp_0.6.2-3_source.buildinfo
Checksums-Sha256:
 7d3a8adc6cb1dfa137b3e8fa22634e2aaac3a1e83876257f66e4eacba677e26b 2107 
ros-gencpp_0.6.2-3.dsc
 7d93a7d1244f6b392146643020d312eadefa791023a8bf18c911231e92b6012d 3652 
ros-gencpp_0.6.2-3.debian.tar.xz
 fb9e5e6ba230490c4d2cf2797181dd529ae6e59fa2788bbe6d55c89c1b3afe53 8031 
ros-gencpp_0.6.2-3_source.buildinfo
Files:
 bcec4ac15b067689e7fb6998666cc556 2107 python optional ros-gencpp_0.6.2-3.dsc
 27be473404bd83ff6542318cae5dfc06 3652 python optional 
ros-gencpp_0.6.2-3.debian.tar.xz
 8f1e0e7d6aa5bd64bb47e858761b360a 8031 python optional 
ros-gencpp_0.6.2-3_source.buildinfo

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

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl2z6gIACgkQW//cwljm
lDMldhAAov7DCxRk725XqAcDoqoCkGHcvTej4/An5GksgaQKzGvEyxnt0WV4zIm1
jLhhXqOtRtQLHaiblERy68KoojKBM14A6L2NfRAQhW0B3oyXtJmsSV4cAst0wBC7
rTELvcAsJP4aDO73Psb/0RAqMFPEQQsyAfHXBbkR6CFonUC8Znh6vAToU5QVgjUz
dJw/uOkJeZyMHt98ai4zeis+Bt3cFQV0wmmZb55OcDMxhyoNuNfv1BnT35XlveDv
8WYkBguvIjXhLzgkyTuQemLTcwYnCed+R6sz7v652rmq5Qs4ZsQTX53pqjSMyixk
202C4keVCIlLxWawET1yEhNEhBsFo+Y6wTxWZScOM19yA4BdPSr8HlIQz1OHdDYL
BVP7//euwIzS85GDfIT5HsgGlJZvjLj1i8EuCPWdwXlyC4OAhIAOshmEPQiOwmK4
f+me3iViPMEjQTrdneiCpBUgbcsfdqIxw5JViibBXsplYoScpUIcarDl4mGhCoqm
lvaccvjNrmFqOijK9AYkSGu+aGfHUjLjvH9DrtctDS96BxKxuRnxOZ8JeoQF19Dj
GFePZJRHOwPI00w+xlGpNsGtkNY6X/UEck7rkCFEwGUqWTP0rkdKQ4bGRS9FI4XJ
7w/yC8ZwXs4aXcnQ2bVW0EUZWMiSP6SH4uh1cNtWlwExtsWRBIE=
=+ruG
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to