Bug 156036
| Summary: | New logwatch-6.0.2 available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | bjorn l. <bl_fedora> |
| Component: | logwatch | Assignee: | Ivana Varekova <varekova> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | reuben-redhatbugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.logwatch.org | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-06-28 13:46:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
bjorn l.
2005-04-26 20:11:58 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 ? :)
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 logwatch.org.
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
patch-free.
Version 6.1 is now available from http://www.logwatch.org. Thank you for your notices. The last devel version is logwatch-6.1.2-1 now. |