Also you could have a look at the current logwatch upstream git repo and
see if there is already a commit that address the situation you are
fixing yourself before submitting upstream.
I did a quick search and I found a major rework for named report, which might
solve the situation...
I think it's worth looking at the existing git repo and see if problem is solve
already.
If it already in place in logwatch git, then you can request a backport
in Xenial and other affected releases.
If not already in place, then submit your fix upstream, and then once
approve/merged we can then backport it into Ubuntu affected releases.
* Upstream repo :
$ git clone git://git.code.sf.net/p/logwatch/git logwatch-git
* Potential candidate that IMHO is worth reviewing:
commit 22c55d1246c8d2295e416105b0bef695349fcb04
[named] Major rework for named report
- Catch connection timed out zone transfer failures
- Catch zone expired and other messages that have view names
- Move important messages/errors to the top of the report
- Always report deniend zone transfers
- Ignore client signer approved messages
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652764
Title:
[Patch] Unmatched named lines
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1652764/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
