[Logcheck-devel] Processed: tagging 495961

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.35 tags 495961 moreinfo Bug#495961: logcheck-database: ignore.d.server/sympa rules for sympa not sufficient There were no tags set. Tags added: moreinfo End of message, stopping

[Logcheck-devel] Processed: Re: Bug#491127: logcheck: please consider an option which will always check the entire log file

Processing commands for [EMAIL PROTECTED]: tags 491127 help Bug#491127: logcheck: please consider an option which will always check the entire log file There were no tags set. Tags added: help thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking

[Logcheck-devel] Bug#491127: logcheck: please consider an option which will always check the entire log file

tags 491127 help thanks also sprach Marc Haber [EMAIL PROTECTED] [2008.07.16.2215 +0100]: It would help with debugging to have an option that causes logcheck to always look through the entire log file, ie not using logtail. Patches welcome. -- .''`. martin f. krafft [EMAIL PROTECTED] :

[Logcheck-devel] Bug#474239: setting package to logcheck-database logtail logcheck, tagging 491694, tagging 474239, tagging 489172 ...

# Automatically generated email from bts, devscripts version 2.10.35 # via tagpending # # logcheck (1.3) unstable; urgency=low # # * Formalise the dropping of violations.d/logcheck. Please see #/usr/share/doc/logcheck-database/NEWS.Debian.gz for more information #(closes: #471072). # *

[Logcheck-devel] Processed: setting package to logcheck-database logtail logcheck, tagging 491694, tagging 474239, tagging 489172 ...

Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.35 # via tagpending # # logcheck (1.3) unstable; urgency=low # # * Formalise the dropping of violations.d/logcheck. Please see #/usr/share/doc/logcheck-database/NEWS.Debian.gz

[Logcheck-devel] Processing of logcheck_1.3.0_i386.changes

logcheck_1.3.0_i386.changes uploaded successfully to localhost along with the files: logcheck_1.3.0.dsc logcheck_1.3.0.tar.gz logcheck_1.3.0_all.deb logcheck-database_1.3.0_all.deb logtail_1.3.0_all.deb Greetings, Your Debian queue daemon

[Logcheck-devel] logcheck_1.3.0_i386.changes ACCEPTED

Accepted: logcheck-database_1.3.0_all.deb to pool/main/l/logcheck/logcheck-database_1.3.0_all.deb logcheck_1.3.0.dsc to pool/main/l/logcheck/logcheck_1.3.0.dsc logcheck_1.3.0.tar.gz to pool/main/l/logcheck/logcheck_1.3.0.tar.gz logcheck_1.3.0_all.deb to

[Logcheck-devel] Bug#494740: marked as done (logcheck: Kernel rules don't match messages of newer kernels)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#494740: fixed in logcheck 1.3.0 has caused the Debian Bug report #494740, regarding logcheck: Kernel rules don't match messages of newer kernels to be marked as done. This means that you

[Logcheck-devel] Bug#474239: marked as done (spamassassin: spamd logcheck file doesn't work with shortcircuit enabled)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#474239: fixed in logcheck 1.3.0 has caused the Debian Bug report #474239, regarding spamassassin: spamd logcheck file doesn't work with shortcircuit enabled to be marked as done. This means

[Logcheck-devel] Bug#489172: marked as done (logcheck: please add Auto-Submitted header field to mailouts)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#489172: fixed in logcheck 1.3.0 has caused the Debian Bug report #489172, regarding logcheck: please add Auto-Submitted header field to mailouts to be marked as done. This means that you

[Logcheck-devel] Bug#495923: marked as done (logcheck-database: Should include upsd rules)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#495923: fixed in logcheck 1.3.0 has caused the Debian Bug report #495923, regarding logcheck-database: Should include upsd rules to be marked as done. This means that you claim that the

[Logcheck-devel] Bug#493066: marked as done (logcheck-database: does not ignore OpenVPN's log if CN has @)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#493066: fixed in logcheck 1.3.0 has caused the Debian Bug report #493066, regarding logcheck-database: does not ignore OpenVPN's log if CN has @ to be marked as done. This means that you

[Logcheck-devel] Bug#471072: marked as done (logcheck-database: Moving most of violations.ignore.d to ignore.d.*)

Your message dated Sun, 31 Aug 2008 19:32:06 + with message-id [EMAIL PROTECTED] and subject line Bug#471072: fixed in logcheck 1.3.0 has caused the Debian Bug report #471072, regarding logcheck-database: Moving most of violations.ignore.d to ignore.d.* to be marked as done. This means that

[Logcheck-devel] Bug#497325: logcheck-database: please ignore NetworkManager Supplicant state changed

Package: logcheck-database Version: 1.2.68 Severity: normal Hello, When wireless is enabled on my laptops (ie all the time), NetworkManager floods the logs with 'info Supplicant state changed:' 0 or 1. Logcheck should ignore these dozens of messages. A dumb rule like these one works here: