Bug 2295265 - fail2ban-systemd should depend on python3-setuptools
Summary: fail2ban-systemd should depend on python3-setuptools
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fail2ban
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-02 18:58 UTC by fussel
Modified: 2024-10-26 02:57 UTC (History)
3 users (show)

Fixed In Version: fail2ban-1.1.0-5.fc40 fail2ban-1.1.0-5.fc41
Clone Of:
Environment:
Last Closed: 2024-10-25 02:08:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fail2ban fail2ban pull 3728 0 None Merged replace distutils for python 3.12 2024-10-16 02:04:04 UTC

Description fussel 2024-07-02 18:58:55 UTC
As python 3.12 core does not longer ship with the distutils module in favor of using setuptools, the fail2ban-systemd backend shows the following error, if python3-setuptools is not installed:

Backend 'systemd' failed to initialize due to No module named 'distutils'

So I think, a dependency on python3-setuptools should be added to fail2ban-systemd as the error is not very convincing, if you don't know that the distutils module was dropped in python 3.12.

Reproducible: Always

Steps to Reproduce:
1. install fail2ban and fail2ban-systemd
2. ensure python3-setuptools is not installed
3. enable sshd jail
4. start fail2ban
Actual Results:  
Error Backend 'systemd' failed to initialize due to No module named 'distutils' shows up in fail2ban.log

Expected Results:  
fail2ban should work

Comment 1 Richard Shaw 2024-10-15 22:25:33 UTC
Should distutils/setuptools be a run time dependency?

Comment 2 Fedora Update System 2024-10-16 02:27:46 UTC
FEDORA-2024-bd519e6370 (fail2ban-1.1.0-5.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-bd519e6370

Comment 3 Fedora Update System 2024-10-16 02:27:47 UTC
FEDORA-2024-6e75d8b28e (fail2ban-1.1.0-5.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-6e75d8b28e

Comment 4 Fedora Update System 2024-10-17 02:17:10 UTC
FEDORA-2024-6e75d8b28e has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6e75d8b28e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6e75d8b28e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2024-10-17 02:39:52 UTC
FEDORA-2024-bd519e6370 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-bd519e6370`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-bd519e6370

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-10-25 02:08:18 UTC
FEDORA-2024-bd519e6370 (fail2ban-1.1.0-5.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2024-10-26 02:57:25 UTC
FEDORA-2024-6e75d8b28e (fail2ban-1.1.0-5.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.