fail2ban fails to build with Python 3.12.0a5. + /usr/bin/python3 bin/fail2ban-testcases --verbosity=2 --no-network Traceback (most recent call last): File "/builddir/build/BUILD/fail2ban-1.0.2/bin/fail2ban-testcases", line 40, in <module> from fail2ban.tests.utils import getOptParser, initProcess, gatherTests File "/builddir/build/BUILD/fail2ban-1.0.2/fail2ban/tests/utils.py", line 46, in <module> from ..server import asyncserver File "/builddir/build/BUILD/fail2ban-1.0.2/fail2ban/server/asyncserver.py", line 28, in <module> import asynchat ModuleNotFoundError: No module named 'asynchat' asynchat and asyncore have been removed according to the schedule in PEP 594, having been deprecated in Python 3.6. Use asyncio instead. (Contributed by Nikita Sobolev in gh-96580.) https://github.com/python/cpython/issues/96580 https://docs.python.org/3.12/whatsnew/3.12.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05573413-fail2ban/ For all our attempts to build fail2ban with Python 3.12, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/fail2ban/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.12: https://copr.fedorainfracloud.org/coprs/g/python/python3.12/ Let us know here if you have any questions. Python 3.12 is planned to be included in Fedora 39. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.12. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Reported upstream
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
*** Bug 2237479 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 2219991 ***