This bug was fixed in the package logwatch -
7.4.0+svn20130529rev144-1ubuntu1.1
---
logwatch (7.4.0+svn20130529rev144-1ubuntu1.1) trusty; urgency=medium
* debian/patches/fix-match-samba-logs.patch: Fix match rules for samba logs
(LP: #1010602)
-- Wesley Wiedenmeier
Since this bug had been inactive for quite a while previously the
original reporter may no longer be following it.
I tested out the version in proposed, and can verify that the version in
proposed finds the samba logs correctly. Since the patch only adds an
additional rule to match the samba log
Hello Jacob, or anyone else affected,
Accepted logwatch into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/logwatch/7.4.0+svn20130529rev144-1ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
ACK on the debdiff in comment #9. I've uploaded a package to trusty-
proposed (with a slight version change) for sponsoring by the SRU team.
Thanks!
** Changed in: logwatch (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of
** Also affects: logwatch (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: logwatch (Ubuntu)
Status: Triaged => Fix Released
** Changed in: logwatch (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Tags removed: regression
** Tags added: regression-release
** Tags added: precise trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Title:
samba logs are not being reported in
The attachment "fix_match_samba_logs.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Here's a debdiff for trusty that brings in the fix as it went into
upstream. Note that it is slightly different than the patch attached to
the bug.
A build including the this debdiff is available at:
https://launchpad.net/~wesley-wiedenmeier/+archive/ubuntu/test
** Patch added:
The fix in upstream was at revision 246:
https://sourceforge.net/p/logwatch/code/246/#diff-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Title:
samba logs are not being reported in
Hi,
This was fixed in upsteam as of release 7.4.2, which is present in
Xenial. The fix is not present in Trusty though, so I will prepare a
debdiff including your patch as it was added by upstream for sru.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I will give it a whirl... not sure the exact (best) steps but I assume:
Submit a bug against Logwatch at SourceForge.net
Follow/answer questions there as needed.
If it gets patched then would I need to try to get Debian to pickup the
patch before Ubuntu would consider an SRU to 12.04?
--
You
Jacob,
You've got the steps right.
The latest development version of Ubuntu (currently Quantal) must be
fixed before considering an SRU.
But how the development version is fixed is a little subjective. There
isn't a specific rule; just the goal of minimising present and future
work. The least
Just for the record and if anyone wants to check on it.
Upstream bug submitted:
http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824#
** Bug watch added: SourceForge.net Tracker #3536008
http://sourceforge.net/support/tracker.php?aid=3536008
--
You received this
** Also affects: logwatch via
http://sourceforge.net/support/tracker.php?aid=3536008
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
I will give it a whirl... not sure the exact (best) steps but I assume:
Submit a bug against Logwatch at SourceForge.net
Follow/answer questions there as needed.
If it gets patched then would I need to try to get Debian to pickup the
patch before Ubuntu would consider an SRU to 12.04?
--
You
Jacob,
You've got the steps right.
The latest development version of Ubuntu (currently Quantal) must be
fixed before considering an SRU.
But how the development version is fixed is a little subjective. There
isn't a specific rule; just the goal of minimising present and future
work. The least
Just for the record and if anyone wants to check on it.
Upstream bug submitted:
http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824#
** Bug watch added: SourceForge.net Tracker #3536008
http://sourceforge.net/support/tracker.php?aid=3536008
--
You received this
** Also affects: logwatch via
http://sourceforge.net/support/tracker.php?aid=3536008
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Title:
** Changed in: logwatch (Ubuntu)
Importance: Undecided = Medium
** Changed in: logwatch (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the detail in your report.
We certainly do want the default supplied by the logwatch package to
match the default supplied by the samba package here, and it is clearly
a bug that it doesn't.
I don't
** Changed in: logwatch (Ubuntu)
Importance: Undecided = Medium
** Changed in: logwatch (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Title:
samba
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the detail in your report.
We certainly do want the default supplied by the logwatch package to
match the default supplied by the samba package here, and it is clearly
a bug that it doesn't.
I don't
** Attachment added: Fix to revert back to prior working settings
https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
Here is the source commit that changed the samba.conf. The reason listed was:
samba.conf patch to deal with cores dir -mgt
I have no idea what that means honestly but maybe it would be of help to know...
http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5
--
You
** Attachment added: Fix to revert back to prior working settings
https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010602
Here is the source commit that changed the samba.conf. The reason listed was:
samba.conf patch to deal with cores dir -mgt
I have no idea what that means honestly but maybe it would be of help to know...
http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5
--
You
26 matches
Mail list logo
