Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 156036 - New logwatch-6.0.2 available
Summary: New logwatch-6.0.2 available
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-26 20:11 UTC by bjorn l.
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-28 13:46:55 UTC

Attachments (Terms of Use)

Description bjorn l. 2005-04-26 20:11:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-2 Firefox/1.0.3

Description of problem:
New logwatch available from  The
new 6.0.2 supersedes the 6.0.1 currently in the development
directory.  logwatch-6.0.2 should go into FC4test3.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Check

Additional info:

I believe that version 6.0.2 addresses the following open bugs:


Bug 153980 appears to be a diskcheck issue, not a logwatch issue.
I could not reproduce 119287, so it probably got fixed since it
was filed.

Comment 1 Reuben Farrelly 2005-05-08 05:40:56 UTC
Agreed, a cursory look here seems to suggest that a heap of open bugzilla
entries some listed above, could be killed by this minor upgrade.

Unfortunately all the existing patches would have to remain in, as none seem to
have been picked up upstream.

Having noted that, why have these not been pushed upstream by anyone?  Seems
silly to carry forward patches which look like they fix real problems.

Or were they pushed upstream and rejected?  It would make life easier on the
Redhat maintainer if there were less patches to maintain, and obviously sending
them upstream would achieve this.

I don't mind liasing with logwatch people if no-one else has had a go already.

But for now, can the maintainer possibly upgrade to 6.0.2 ? :)

Comment 2 bjorn l. 2005-05-09 00:36:27 UTC
Thanks for the comment, Reuben.  I did not realize there were patches in
the Fedora rpm; I just assumed it was a copy of the one in
I recently started helping with updating the logwatch source, so I can
help move the patches upstream.  Here is my take on them:

-logwatch-2.6-101744-up2date.patch:      This appears to have been fixed
                in the scripts/logfiles/up2date/removeheaders file.

-logwatch-4.3.2-nosegfault.patch:        I couldn't find the original
                bug report for this.  I am concerned about just ignoring
                those strings.  For example, any error message with
                the word "allocated" will also be ignored, or any
                error with the word "module".  Usually it is better
                to define a more specific line in the filter for the
                service in question (kernel, in this case).

-logwatch-4.3.2-nounicode.patch:         It mentions bug #81144, but I
                can't access it.  Again, it would be good to know what
                the problem is before applying patches.

-logwatch-5.1-http400.patch:             This was fixed.

-logwatch-6.0.1-spaces.patch:            This will go in next release.

-logwatch-6.0.1-zz_disk_space.patch:     This will go in next release.

So more info on the logwatch-4.3.2* patches would be helpful; it's possible
the problem was fixed in a different way upstream.

A new release is being readied, so maybe 6.0.2 can wait.  If we can solve
the remaining two logwatch-4.3.2* patches now the next release might be

Comment 3 bjorn l. 2005-05-17 15:28:34 UTC
Version 6.1 is now available from

Comment 4 Ivana Varekova 2005-06-28 13:46:55 UTC
Thank you for your notices. 
The last devel version is logwatch-6.1.2-1 now.

Note You need to log in before you can comment on or make changes to this bug.