lol, this is comical. The problem was identified 4 months ago. The
precise cause and a working patch submitted shortly afterwards. I'm
unsubscribing from the bug now. Reading this comment train should tell
anyone all they need to know about the Ubuntu support process. It's been
an education.
--
I've just tried the proposed 1.0.2-3ubuntu0.1 package on a clean Noble
VM and it fixed the startup issues, as expected, for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban
Have just tried this myself in a freshly-created Noble install. I can
confirm Åka Sikrom (akrosikam) is absolutely correct; Python3-setuptools
is a runtime dependency of fail2ban1.0.2-3ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fortunately for me, I only have to manage a single server and I patched
this problem on that server myself (the comments from Aka Sikrom here
provide some very useful pointers in this regard) so this no longer
matters to me personally. But it's getting embarrassing how long this
simple fix is
