Your message dated Thu, 23 Jan 2020 22:50:04 +0000
with message-id <[email protected]>
and subject line Bug#943111: fixed in gpgme1.0 1.13.1-2
has caused the Debian Bug report #943111,
regarding gpgme1.0: 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.)
--
943111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943111
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.13.1-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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
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 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: gpgme1.0
Source-Version: 1.13.1-2
We believe that the bug you reported is fixed in the latest version of
gpgme1.0, 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.
Daniel Kahn Gillmor <[email protected]> (supplier of updated gpgme1.0
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, 23 Jan 2020 17:11:25 -0500
Source: gpgme1.0
Architecture: source
Version: 1.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <[email protected]>
Changed-By: Daniel Kahn Gillmor <[email protected]>
Closes: 943111 943390 944774
Changes:
gpgme1.0 (1.13.1-2) unstable; urgency=medium
.
* rebuild, pulling in python 3.8 (Closes: #944774)
- requires patching upstream, changes to cross-building logic
* Update standards version to 4.4.1, no changes needed.
* add buildtime and runtime tests for platform time limits
* remove python-gpg autopkgtest entirely (Closes: #943390, #943111)
* update lintian-overrides for untracked C++ symbols
* fix json tests
* d/control: drop unused ${shlibs:Depends} from libgpgmepp-dev
* d/control: added ${python3:Versions} to python3-gpg
Checksums-Sha1:
9bbddb05ec952566ee04383b0f6ef2ed73bff8b6 2258 gpgme1.0_1.13.1-2.dsc
1ca56c058541a8318bb988558664bb4a49efe6a4 19768 gpgme1.0_1.13.1-2.debian.tar.xz
04add7c3f8d33e76b90e135f95ba2cc467693a60 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Checksums-Sha256:
81d8a2db4746c8fdfb3b9ff2bf18ddc0e1df74d23f0cad6db3c992e4afd5a783 2258
gpgme1.0_1.13.1-2.dsc
bddc4d6725af83c38a1b9953683bb9c2e40049867bef205e428cea307207925d 19768
gpgme1.0_1.13.1-2.debian.tar.xz
2664dcdd10cd7de57f0a3c253f2b4c690f04a388cfb53065b480c6ca9493f40e 18420
gpgme1.0_1.13.1-2_amd64.buildinfo
Files:
9e98e39414139a0715bc591a009b5f1b 2258 libs optional gpgme1.0_1.13.1-2.dsc
edd5f7455ef8ec0f3fc1df0867f04fa1 19768 libs optional
gpgme1.0_1.13.1-2.debian.tar.xz
0973764309265760b6737b192e741bf8 18420 libs optional
gpgme1.0_1.13.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXiog8wAKCRDEDyVUMvKB
D6+BAPwLZHTK7GdDRpAgA8qL2VYE0EB3xHIEtdFlW/L4J3pJjQEAnaLN3n8qUlR9
H3k2O0JEMxP/YxcSeyoSv7K3xlX1gQw=
=2R8I
-----END PGP SIGNATURE-----
--- End Message ---
