Your message dated Fri, 31 May 2024 10:41:18 +0100
with message-id <[email protected]>
and subject line Re: Bug#1071829: fail2ban: spurious ">" character in
paths-debian.conf
has caused the Debian Bug report #1071829,
regarding fail2ban: spurious ">" character in paths-debian.conf
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 [email protected]
immediately.)
--
1071829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071829
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fail2ban
Version: 1.1.0-3
Severity: grave
Justification: renders package unusable
The /etc/fail2ban/paths-debian.conf file starts with
># Debian
which yields an error:
May 25 10:39:45 qaa systemd[1]: Started fail2ban.service - Fail2Ban Service.
May 25 10:39:45 qaa fail2ban-server[172274]: 2024-05-25 10:39:45,628 fail2ban
[172274]: ERROR Failed during configuration: File contains no
section headers.
May 25 10:39:45 qaa fail2ban-server[172274]: file:
'/etc/fail2ban/paths-debian.conf', line: 1
May 25 10:39:45 qaa fail2ban-server[172274]: '># Debian\n'
May 25 10:39:45 qaa fail2ban-server[172274]: 2024-05-25 10:39:45,630 fail2ban
[172274]: ERROR Async configuration of server failed
May 25 10:39:45 qaa systemd[1]: fail2ban.service: Main process exited,
code=exited, status=255/EXCEPTION
May 25 10:39:45 qaa systemd[1]: fail2ban.service: Failed with result
'exit-code'.
The first hunk in debian/patches/update_backend_system.diff, which
adds this character, should be removed:
Index: fail2ban/config/paths-debian.conf
===================================================================
--- fail2ban.orig/config/paths-debian.conf
+++ fail2ban/config/paths-debian.conf
@@ -1,4 +1,4 @@
-# Debian
+># Debian
[INCLUDES]
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
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.11.8-1
ii python3-systemd 235-1+b3
Versions of packages fail2ban recommends:
ii iptables 1.8.10-3
ii nftables 1.0.9-2
ii python3-pyinotify 0.9.6-2
ii whois 5.5.23
Versions of packages fail2ban suggests:
ii mailutils [mailx] 1:3.17-1.1+b2
pn monit <none>
ii sqlite3 3.45.3-1
pn system-log-daemon <none>
-- Configuration Files:
/etc/fail2ban/action.d/mikrotik.conf [Errno 2] No such file or directory:
'/etc/fail2ban/action.d/mikrotik.conf'
/etc/fail2ban/filter.d/dante.conf [Errno 2] No such file or directory:
'/etc/fail2ban/filter.d/dante.conf'
/etc/fail2ban/filter.d/nginx-error-common.conf [Errno 2] No such file or
directory: '/etc/fail2ban/filter.d/nginx-error-common.conf'
/etc/fail2ban/filter.d/nginx-forbidden.conf [Errno 2] No such file or
directory: '/etc/fail2ban/filter.d/nginx-forbidden.conf'
/etc/fail2ban/filter.d/routeros-auth.conf [Errno 2] No such file or directory:
'/etc/fail2ban/filter.d/routeros-auth.conf'
-- no debconf information
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 1.1.0-4
On Sat, May 25, 2024 at 11:44:33AM +0200, Vincent Lefevre wrote:
> The /etc/fail2ban/paths-debian.conf file starts with
>
> ># Debian
This was fixed recently, but wasn't automatically closed due to writing
"Fixes:" rather than "Closes:" in the changelog entry:
fail2ban (1.1.0-4) unstable; urgency=medium
* Fix spurious ">" character in paths-debian.conf
(Fixes: #1071829)
-- Sylvestre Ledru <[email protected]> Sat, 25 May 2024 12:06:07 +0200
Sylvestre, could you please push these changes to git, along with the
tags for 1.1.0-3 and 1.1.0-4? I spent a couple of minutes preparing a
fix for this before realizing that it was already fixed in the archive.
Thanks,
--
Colin Watson (he/him) [[email protected]]
--- End Message ---
