Sync fail2ban 0.11.2-6 (universe) from Debian unstable (main)
Bug #1965544 reported by
Sylvestre Ledru
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| fail2ban (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Please sync fail2ban 0.11.2-6 (universe) from Debian unstable (main)
Changelog entries since current jammy version 0.11.2-5:
fail2ban (0.11.2-6) unstable; urgency=medium
* Cherry-pick upstream fix to fix a startup issue with Python 3.10
(LP: #1958505)
* Cherry-pick upstream fix for courier-auth (Closes: #1004466)
* ignore false positive
fail2ban: read-in-
-- Sylvestre Ledru <email address hidden> Thu, 10 Mar 2022 22:52:59 +0100
| Changed in fail2ban (Ubuntu): | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Jeremy Bícha (jbicha) wrote | #1 |
| Changed in fail2ban (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package fail2ban - 0.11.2-6
Sponsored for Sylvestre Ledru (sylvestre)
---------------
fail2ban (0.11.2-6) unstable; urgency=medium
* Cherry-pick upstream fix to fix a startup issue with Python 3.10
(LP: #1958505)
* Cherry-pick upstream fix for courier-auth (Closes: #1004466)
* ignore false positive
fail2ban: read-in-
-- Sylvestre Ledru <email address hidden> Thu, 10 Mar 2022 22:52:59 +0100