[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#769311: marked as done (unblock: logwatch/7.4.1-2)

Your message dated Wed, 12 Nov 2014 19:29:32 +0000
with message-id <20141112192932.GF21455@lupin.home.powdarrmonkey.net>
and subject line Re: Bug#769311: unblock: logwatch/7.4.1-2
has caused the Debian Bug report #769311,
regarding unblock: logwatch/7.4.1-2
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 owner@bugs.debian.org
immediately.)


-- 
769311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769311
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package logwatch

This upload fixes a regression that was introduced in the latest upstream
release, and that completely disables reporting on fail2ban log messages.
The patch simply reverts the "config" file where the problem was introduced
to its state before the problematic change.

debdiff attached.

unblock logwatch/7.4.1-2

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

diff -Nru logwatch-7.4.1/debian/changelog logwatch-7.4.1/debian/changelog
--- logwatch-7.4.1/debian/changelog	2014-10-08 19:32:36.000000000 +0200
+++ logwatch-7.4.1/debian/changelog	2014-11-03 20:02:44.000000000 +0100
@@ -1,3 +1,10 @@
+logwatch (7.4.1-2) unstable; urgency=medium
+
+  * Revert upstream change on fail2ban service config. This makes fail2ban
+    reporting work again. Closes: #766901
+
+ -- Willi Mann <willi@debian.org>  Mon, 03 Nov 2014 20:02:30 +0100
+
 logwatch (7.4.1-1) unstable; urgency=medium
 
   * Imported Upstream version 7.4.1 (svn rev 242)
diff -Nru logwatch-7.4.1/debian/patches/0006-Revert-upstream-change-on-fail2ban-service-config.patch logwatch-7.4.1/debian/patches/0006-Revert-upstream-change-on-fail2ban-service-config.patch
--- logwatch-7.4.1/debian/patches/0006-Revert-upstream-change-on-fail2ban-service-config.patch	1970-01-01 01:00:00.000000000 +0100
+++ logwatch-7.4.1/debian/patches/0006-Revert-upstream-change-on-fail2ban-service-config.patch	2014-11-03 19:55:06.000000000 +0100
@@ -0,0 +1,33 @@
+From: Willi Mann <willi@debian.org>
+Date: Mon, 3 Nov 2014 19:45:20 +0100
+Subject: Revert upstream change on fail2ban service config
+
+Upstream started to use OnlyService and RemoveHeaders in fail2ban conf.
+Unfortunately, this does not work with fail2ban because it uses a different
+"header" format in log entries as compared to syslog.
+---
+ conf/services/fail2ban.conf | 9 ++-------
+ 1 file changed, 2 insertions(+), 7 deletions(-)
+
+diff --git a/conf/services/fail2ban.conf b/conf/services/fail2ban.conf
+index 4326a52..b74236f 100644
+--- a/conf/services/fail2ban.conf
++++ b/conf/services/fail2ban.conf
+@@ -1,5 +1,5 @@
+ ###########################################################################
+-# $Id: fail2ban.conf 205 2014-09-08 19:15:49Z stefjakobs $
++# $Id: fail2ban.conf 149 2013-06-18 22:18:12Z mtremaine $
+ ###########################################################################
+ # $Log: fail2ban.conf,v $
+ # Revision 1.1  2006/05/30 19:04:26  bjorn
+@@ -22,9 +22,4 @@ Title = fail2ban-messages
+ # Which logfile group...
+ LogFile = fail2ban
+ 
+-# Only give lines pertaining to the fail2ban service...
+-# Note: fail2ban logs using "service" names fail2ban, fail2ban.jail,
+-# fail2ban.filter, and many more.  We want to exclude fail2ban-client
+-# so we accept either fail2ban or fail2ban\..+
+-*OnlyService = fail2ban(|\..+)
+-*RemoveHeaders
++
diff -Nru logwatch-7.4.1/debian/patches/series logwatch-7.4.1/debian/patches/series
--- logwatch-7.4.1/debian/patches/series	2014-10-06 19:45:49.000000000 +0200
+++ logwatch-7.4.1/debian/patches/series	2014-11-03 19:55:06.000000000 +0100
@@ -3,3 +3,4 @@
 0003-Bug-656806-Support-alternative-OoM-kernel-message-in.patch
 0004-logfiles-vsftpd.conf-Use-custom-pattern-for-applystd.patch
 0005-Deb-specific-Print-full-path-to-freshclam-log.patch
+0006-Revert-upstream-change-on-fail2ban-service-config.patch

--- End Message ---
--- Begin Message --- 
On Wed, Nov 12, 2014 at 06:23:55PM +0100, Willi Mann wrote:
> Please unblock package logwatch
> 
> This upload fixes a regression that was introduced in the latest upstream
> release, and that completely disables reporting on fail2ban log messages.
> The patch simply reverts the "config" file where the problem was introduced
> to its state before the problematic change.

Unblocked.

-- 
Jonathan Wiltshire                                      jmw@debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: