Your message dated Fri, 09 May 2025 10:39:14 +0000
with message-id <e1udl8m-007djm...@fasolo.debian.org>
and subject line Bug#1104790: fixed in fail2ban 1.1.0-8
has caused the Debian Bug report #1104790,
regarding fail2ban fails to start without python3-setuptools installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1104790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 1.1.0-7
Severity: normal

Hello,

Please considering bumping python3-setuptools from Recommends to Depends.
Without it, the default configuration fails to start:

    (journal)
    Jan 11 11:07:30 jubjub systemd[1]: Started fail2ban.service - Fail2Ban 
Service.
    Jan 11 11:07:30 jubjub fail2ban-server[3163989]: Server ready
    Jan 11 11:07:31 jubjub systemd[1]: fail2ban.service: Main process exited, 
code=exited, status=255/EXCEPTION
    Jan 11 11:07:31 jubjub systemd[1]: fail2ban.service: Failed with result 
'exit-code'.

    (fail2ban.log)
    2025-01-11 11:07:30,988 fail2ban.server         [3163989]: INFO    
--------------------------------------------------
    2025-01-11 11:07:30,989 fail2ban.server         [3163989]: INFO    Starting 
Fail2ban v1.1.0
    2025-01-11 11:07:30,989 fail2ban.observer       [3163989]: INFO    Observer 
start...
    2025-01-11 11:07:30,990 fail2ban.database       [3163989]: INFO    
Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
    2025-01-11 11:07:30,991 fail2ban.jail           [3163989]: INFO    Creating 
new jail 'sshd'
    2025-01-11 11:07:30,991 fail2ban.jail           [3163989]: ERROR   Backend 
'systemd' failed to initialize due to No module named 'distutils'
    2025-01-11 11:07:30,991 fail2ban.jail           [3163989]: ERROR   Failed 
to initialize any backend for Jail 'sshd'
    [snip]

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fail2ban depends on:
ii  python3          3.12.8-1
ii  python3-systemd  235-1+b5

Versions of packages fail2ban recommends:
ii  iptables            1.8.11-2
ii  nftables            1.1.1-1
pn  python3-pyinotify   <none>
ii  python3-setuptools  75.6.0-1
ii  whois               5.5.23

Versions of packages fail2ban suggests:
pn  mailx              <none>
pn  monit              <none>
pn  sqlite3            <none>
pn  system-log-daemon  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 1.1.0-8
Done: Colin Watson <cjwat...@debian.org>

We believe that the bug you reported is fixed in the latest version of
fail2ban, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1104...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated fail2ban package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 09 May 2025 11:19:16 +0100
Source: fail2ban
Architecture: source
Version: 1.1.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1104790
Changes:
 fail2ban (1.1.0-8) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sylvestre Ledru ]
   * Add autopkgtest testing.  Thanks to Zaiba Sanglikar for the patch
   * Remove patch deb_path_to_common. Thanks to Zaiba Sanglikar
     for the patch
 .
   [ Colin Watson ]
   * Revert patch to fail on any invalid ssh public key, since this would ban
     legitimate users with multiple public keys.  See
     https://github.com/fail2ban/fail2ban/issues/3922 for the rationale.
 .
   [ Antoine Beaupré ]
   * Remove runtime calls to distutils, crashing in trixie (Closes: #1104790)
 .
   [ MichaIng ]
   * Fix log identifier for OpenSSH 10.0.
Checksums-Sha1:
 0da278e56c8d6eb6a917dbb58e365aba84732bc1 2319 fail2ban_1.1.0-8.dsc
 aebe1efb597e1d1876483b67c7fe993a76c2466e 31388 fail2ban_1.1.0-8.debian.tar.xz
Checksums-Sha256:
 ae88563ebc9b6416583ac0fe2a94a6f586e37b528ea6a52185d3d864e913de84 2319 
fail2ban_1.1.0-8.dsc
 48427f0a83b9bccd6fa1d16bec86646e78ebfd3c342a9142444e75f9102ab6ae 31388 
fail2ban_1.1.0-8.debian.tar.xz
Files:
 3bb032642874b45671add84b966549dd 2319 net optional fail2ban_1.1.0-8.dsc
 94ad20eeac98e948adbe49d54ecbe839 31388 net optional 
fail2ban_1.1.0-8.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmgd1zYACgkQOTWH2X2G
UAv9OA//Up59HBXAWAjwRTWdbqNOB+EbZwZaq2agYoTM86mG6xAVagQYJsbwB5Ty
tnFc+eoLOS51wMqz26symQ8iJJaWOY2e7c9uEnuSvQ1vvof/6Q8zGxT9nhSwCJgS
3Guk8XJ/p9jyEVqUwwoB6eSfzu5V1v9cbfJSkPzO0gSZUgFgnyofRliWt+lWneVa
XXaZjZ3p2kdnYxEsFrzuMJ4tU5rq7QsBOBMCzet1a9BEaBvvocp9wbjGnIkBP1sy
jj6A7kURasR/SW4U9CvPj1jq32LbX/CPQ/MMTmRkPs4jQs+cpUU5jXlxXWuQO5Ih
VitWDqsI8gCfyZJvRqYeT+6feLnk018ieUdzl/zz0AFh1pdTu4Y2/R2g2hiXUtE/
AYYrRh9ddOMdp3E0RqxopB2rNPZVoCBcben2NCl6vkoC+xkl7PYqA9Zit3r5xSpj
OI0GfNOx+nkOQAR+TsYz2xya2Ww1/H/NgszXMsu3c+WmuA8GKLreqEMuv5FXe8i7
Ai03GVIg3Qs4BGtHcUDKMj9x7lAo0jNpkaMCz8QWzIl2kH9nXTAviaFaiMRu6dMy
smKYelx2uWQsKXBdEBc92AYJR6kSvgtYGxAryRwgOaJpyVxdTC2G8B61Q7FP68Iz
w2KM220ajrqFoTEY8VWs9mqrpMQ3DzOFzvV9IRUDGOFs8Pe7zQ8=
=lSOH
-----END PGP SIGNATURE-----

Attachment: pgpt83t9NL0NU.pgp
Description: PGP signature


--- End Message ---

Reply via email to