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

Bug#471995: marked as done (RFA: logwatch -- log analyser with nice output written in Perl)

Your message dated Fri, 04 Jul 2008 16:48:28 +0200
with message-id <486E383C.60602@wm1.at>
and subject line closing
has caused the Debian Bug report #471995,
regarding RFA: logwatch -- log analyser with nice output written in Perl
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.)


-- 
471995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471995
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

I request an adopter for the logwatch package.

I won't have enough time to make logwatch ready for lenny. The biggest
issue in logwatch is that upstream has not really been aware of the need
of proper copyright statements[1]. I can't resolve that in time for lenny. 

In case nobody adopts this package, I'll file a removal request soon.

I've maintained the debian package as alioth project[2]. 

According to popcon, logwatch is installed on 1885 machines, or 2.44%
of all popcon submitters' machines[3].

If someone just wants to work on the copyright holders issue, I'd be 
willing to continue to maintain this package.

Willi

[1] http://lists.debian.org/debian-legal/2008/02/msg00035.html
[2] http://alioth.debian.org/projects/pkg-logwatch
[3] http://qa.debian.org/popcon.php?package=logwatch

CCed to my AM and my current sponsor for logwatch.

The package description is:
 Logwatch is a modular log analyser that runs every night
 and mails you the results. It can also be run from command line.
 .
 The output is by service and you can limit the output to one particular
 service. The subscripts which are responsible for the output, mostly
 convert the raw log lines in structured format.
 .
 Logwatch generally ignores the time component in the output, that means,
 you will know that the reported event was logged in the requested range of
 time, but you will have to go to the raw log files to get the exact details.
 .
 Homepage: http://www.logwatch.org/

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
closing, the copyright issues have been fixed.

--- End Message ---
Reply to: