Your message dated Sat, 08 Aug 2020 20:52:35 +0000
with message-id <e1k4vpt-0009bx...@fasolo.debian.org>
and subject line Bug#966753: fixed in libiptcdata 1.0.5-2.2
has caused the Debian Bug report #966753,
regarding libiptcdata: 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.)


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

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: libiptcdata
Source-Version: 1.0.5-2.2
Done: Matthias Klose <d...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libiptcdata, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <d...@debian.org> (supplier of updated libiptcdata 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: Sat, 08 Aug 2020 22:18:23 +0200
Source: libiptcdata
Architecture: source
Version: 1.0.5-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand <i...@debian.org>
Changed-By: Matthias Klose <d...@debian.org>
Closes: 966753 967163
Changes:
 libiptcdata (1.0.5-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build using python2. Closes: #967163, #966753.
Checksums-Sha1:
 14563368432de20443d953c509eb8b5f755b7689 2439 libiptcdata_1.0.5-2.2.dsc
 5dbfd583a12d83b30773692324fcfed21cc72638 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 5e3e7f50945f9c0328d70b3d4dbb805d3f4d3ae2 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Checksums-Sha256:
 7dcada987dfbae875616470faf2b53cd1a99ab94f8317e4049d71366ca46bbec 2439 
libiptcdata_1.0.5-2.2.dsc
 15e3958a7b0fe95571bc6ca899536bd052597a76cde446fda7e2f6d7cc49d4f2 7784 
libiptcdata_1.0.5-2.2.debian.tar.xz
 c0876eaf787d83c62a4b487d6f9d4509425a0008b12244d3fceef080b9f3ef4f 9247 
libiptcdata_1.0.5-2.2_source.buildinfo
Files:
 3f8055cc8689634a4d3a1cd5e45052d6 2439 libs optional libiptcdata_1.0.5-2.2.dsc
 7a720283e34e14cf2a2e5006904aaaa0 7784 libs optional 
libiptcdata_1.0.5-2.2.debian.tar.xz
 a4edd570b1521e12a53b1cee77959ff9 9247 libs optional 
libiptcdata_1.0.5-2.2_source.buildinfo

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

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8vCesQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9YlVD/sHwLpH0sCISkf+2XHG9HsVFGeQ+T9IovCh
mBqlcU0QKUWzYW98mS5Kdw9hp3+/3/ctNbsOldcCEGkecv8Q4OGWYaqvR9AM43ka
OoTyeA9JuXMpQUBoEUnC5AKUE28LT7N/i5b9MAK/P/ZytTjT7uDyfUhZbQbSwJzf
GOh7WUv2n3dM/lDanQLh9wLVueBdhClxBRAU9J25iWW6p9qadfmw/I4B2RS1KS1V
SN8Zn/ft5aLSU9hlI9Kw0nm0EUzXp+g5eXVI8p3hyMp1E26FcFD4ioSqcNFIznbL
4iJzqVTXuaRBFAIeloHHBnzQvND+SExd9oJoxVrgwl8bGGU2qWHYwoswNtEk/7oZ
2P38hUmzJS/Ahwv0oujsIZIOooKVEDRt7/jpehOZU8zoz0l+yxtOapUW/5Cc0u2D
rziSZMvFormO6xQ7T8kTDuBYbX/U3mn7aTXYYRYF3Fv0EQWTSxr8tbf17Y6bSGKa
oxlGLCsBOjezuuOyAIkHuBEo/G+iuvOpPkdM22aPCXL/xOZV5vORWGLPDgBErxnG
b9IJn2ClCAdwp3KNhA1hGPKGAece9rd2sh17fjdYx2NKOQhoioJg3+bhc9lUu6kb
kpcV+eOfXML2Y0uf1uS+daTLxYJ7mosgBetgnRIM7uRmqVRO9g2aGEgrve3kyfge
5Rmfb6gmoQ==
=gYsd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to