Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
Tags: patch
Dear Maintainer,
on our setups we have a symlink in /var/log/ named fail2ban.log.1 that's
broken. This is probably the relic of a logrotate script, but that's not the
point of this message.
This symlink sadly causes the postinst script of fail2ban to fail. While it's
clear to me that the symlink was generated incorrectly by our system a broken
symlink for a log file shouldn't cause the installation of the package to fail.
Hence I suggest the following patch to the postinst script:
--- /var/lib/dpkg/info/fail2ban.postinst.orig 2019-04-01 22:43:00.768261036
+0200
+++ /var/lib/dpkg/info/fail2ban.postinst 2019-04-01 22:43:35.476379563
+0200
@@ -25,8 +25,8 @@
LOG=/var/log/fail2ban.log
touch $LOG
- chown root:adm ${LOG}*
- chmod 640 ${LOG}*
+ chown root:adm ${LOG}* || true
+ chmod 640 ${LOG}* || true
# Note regarding changed configuration file
# Note regarding changed configuration file
Thank you for your time.
Sincerely,
Kim-Alexander Brodowski
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fail2ban depends on:
ii lsb-base 10.2019031300
ii python3 3.7.2-1
Versions of packages fail2ban recommends:
ii iptables 1.8.2-4
ii python 2.7.15-4
pn python3-pyinotify <none>
pn python3-systemd <none>
ii whois 5.4.1
Versions of packages fail2ban suggests:
pn mailx <none>
pn monit <none>
ii rsyslog [system-log-daemon] 8.1901.0-1
ii sqlite3 3.27.2-2
-- Configuration Files:
/etc/logrotate.d/fail2ban changed [not included]
-- no debconf information
