Your message dated Sun, 12 Jan 2020 23:34:22 +0000
with message-id <[email protected]>
and subject line Bug#945670: fixed in fail2ban 0.11.1-1~exp1
has caused the Debian Bug report #945670,
regarding fail2ban: 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.)
--
945670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945670
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: fail2ban
Version: 0.10.2-2.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_take3.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: fail2ban
Source-Version: 0.11.1-1~exp1
We believe that the bug you reported is fixed in the latest version of
fail2ban, 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.
Sylvestre Ledru <[email protected]> (supplier of updated fail2ban 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: Sun, 12 Jan 2020 23:13:31 +0100
Source: fail2ban
Architecture: source
Version: 0.11.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team
<[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 922539 945670 947926
Changes:
fail2ban (0.11.1-1~exp1) experimental; urgency=medium
.
[ Sylvestre Ledru ]
* New upstream release (Closes: #922539)
* Import fail2ban in the Debian Python Umbrella (Closes: #947926)
* Remove the old dep to Python (Closes: #945670)
* Run ./fail2ban-2to3 as part of the build to be Python 3 ready
* Update to SV: 4.4.1
.
[ Jelmer Vernooij ]
* Use secure URI in Vcs control header.
Checksums-Sha1:
a83bc33e9863fdb54ab061bf004b14dfe16c2f3a 2075 fail2ban_0.11.1-1~exp1.dsc
45b1e4320b079b193acfda7bdc60421f1e920077 538660 fail2ban_0.11.1.orig.tar.gz
a372dcf30f8740bd2eb5fab2135f57a106d148cf 28072
fail2ban_0.11.1-1~exp1.debian.tar.xz
90bb41dd15986a4167e9c832fb514c1d5928d849 6237
fail2ban_0.11.1-1~exp1_amd64.buildinfo
Checksums-Sha256:
aaed95115c21dbcaca96a7af8c5e977b58415f10b86898822f8fce5b4bb4657a 2075
fail2ban_0.11.1-1~exp1.dsc
71d2a52b66bb0f87ac3812246bdd3819ec561913cd44afd39130a342f043aa6d 538660
fail2ban_0.11.1.orig.tar.gz
3f0abe35462484946f61357c0f29907e8495da2d824532ede8d766a95ee4a8b5 28072
fail2ban_0.11.1-1~exp1.debian.tar.xz
49f3ac59ce47c7b6f173b9da906966e117447384c056a56c9b7ea3b9376e90e5 6237
fail2ban_0.11.1-1~exp1_amd64.buildinfo
Files:
f2f9ed7995787f064881fab2e93c4e5e 2075 net optional fail2ban_0.11.1-1~exp1.dsc
0be308ad62826030ba342b6b6012d523 538660 net optional
fail2ban_0.11.1.orig.tar.gz
c04243d3af681dc82e4d362546ce7cd6 28072 net optional
fail2ban_0.11.1-1~exp1.debian.tar.xz
8db90578e0fd76209b0d9866eb8bc053 6237 net optional
fail2ban_0.11.1-1~exp1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl4bqVUACgkQfmUo2nUv
G+H01Q/+O67WBOv3yarWYhqAcK+W/35MAe1e2ihT80Mh9cyNhTC5/yXLJfcbvbRe
zGSscBy/oFefeWIqrCPmfXKfinKevj9xc0x+OTXy8dKL3+JK1XSkI+VvpDjljcaX
lVmhT0XV/hT3CXSS0qEqSG+GlpWFHz/lFosNExGyDWI9RFpZVtNovVQ96mcwjCuD
QYOYJg6rkwHRWR83r/V9ynVGfG2W8NCI7SuDWxnqqpaUWqo5HwlYNO2zZc1Nr6j1
Js3Ps8dQMIVKPR3snTghPor0xQ4ZPGs34SjHioYOGp0xRLmOEbdCDOVLi9qzmE+A
EDxMl5x3c584wDFNaRsKJvtz8Nkt1MYQCpCjJ2qbhDr0v819cbFi3ScPK89udohl
epID29aeLL5xKOAynOKQPk9oFtyc2jjFFhoPRt8l9ugRc7yIw8JsJP3MrcruzDw9
CWhjNVkWARL8gILm4R+6isPeRNYtG73mnVaTfJH0TOrxS3ivdJvJWRzw7JfCvBtJ
0ZSGg7/lyp9OdMzoQBEbAd3d3WtreqrGYvBh1SBB8lxJAA9sPD6bJ0Nfg6yBytmq
gVX4fdx3Kx/Tkpn8fgPwkjHuI68sbceU4IPCndoNBlxtKI3+gj/ikega4tR6hd1C
CTvBmHqbPq+n5fniM/16O+RJR08crEaGU38paSDLuyefFZbVeAo=
=iDVg
-----END PGP SIGNATURE-----
--- End Message ---
