Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40108 - [python] Python 3.4 bug causes Fail2ban jails not to work in 0.9.0-3
Attached to Project:
Arch Linux
Opened by Abc (Morrad) - Sunday, 27 April 2014, 03:23 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 27 April 2014, 16:43 GMT
Opened by Abc (Morrad) - Sunday, 27 April 2014, 03:23 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 27 April 2014, 16:43 GMT
|
DetailsDescription: fail2ban-0.9.0-3 has moved to using python3, but in the process has brought in a bug wherein due to an upstream python bug, fail2ban no longer works (won't start jails, (un)ban IPs, ...). In short, the bug appears to be due to how fail2ban open/closes /dev/urandom through Python.
The issue has been noticed upstream, and a patch has been committed to Python3.4's tree, but it hasn't arrived in a release yet. See upstream reports: https://github.com/fail2ban/fail2ban/issues/687 http://bugs.python.org/issue21207 |
This task depends upon
Closed by Felix Yan (felixonmars)
Sunday, 27 April 2014, 16:43 GMT
Reason for closing: Implemented
Additional comments about closing: 3.4.0-3
Sunday, 27 April 2014, 16:43 GMT
Reason for closing: Implemented
Additional comments about closing: 3.4.0-3