[Logcheck-commits] r1141 - logcheck/trunk/debian

madduck at users.alioth.debian.org madduck at users.alioth.debian.org
Sat Jul 8 14:11:01 UTC 2006


Author: madduck
Date: 2006-07-08 14:11:00 +0000 (Sat, 08 Jul 2006)
New Revision: 1141

Added:
   logcheck/trunk/debian/logcheck-database.NEWS
Modified:
   logcheck/trunk/debian/logcheck-database.config
   logcheck/trunk/debian/logcheck-database.templates
Log:
moving news-style message from debconf to logcheck-database.NEWS

Added: logcheck/trunk/debian/logcheck-database.NEWS
===================================================================
--- logcheck/trunk/debian/logcheck-database.NEWS	2006-07-08 12:16:38 UTC (rev 1140)
+++ logcheck/trunk/debian/logcheck-database.NEWS	2006-07-08 14:11:00 UTC (rev 1141)
@@ -0,0 +1,30 @@
+logcheck-database (1.1.1-8) unstable; urgency=low
+
+  [This message was previously issued with debconf and has now been moved to
+  a NEWS file (where it should be). If you are seeing this again, do note that
+  it applies to an ancient version and you probably know all this already.]
+
+  From version 1.1.1-8, logcheck supports run-parts controled rule
+  directories:
+  
+  - /etc/logcheck/cracking.d
+  - /etc/logcheck/cracking.ignore.d [for local use only]
+  - /etc/logcheck/violations.d
+  - /etc/logcheck/violations.ignore.d
+  - /etc/logcheck/ignore.d.workstation
+  - /etc/logcheck/ignore.d.server
+  - /etc/logcheck/ignore.d.paranoid
+
+  The ignore.d.{workstation,server,paranoid} directory to be used is set by
+  the REPORTLEVEL option in the file "/etc/logcheck/logcheck.conf".
+
+  These directories may contain files prefixed with "logcheck-" (containing
+  generic alert/override patterns), named "(packagename)" (containing patterns
+  specific to that one package), or named "local" respectively prefixed with
+  "local-" (created by the local administrator to contain patterns tailored
+  for a particular site).  Logcheck will then use rules collected from all the
+  files found in the appropriate directories.
+
+  Please see /usr/share/doc/logcheck for more details.
+
+ -- martin f. krafft <madduck at debian.org>  Sat,  8 Jul 2006 16:00:09 +0200

Modified: logcheck/trunk/debian/logcheck-database.config
===================================================================
--- logcheck/trunk/debian/logcheck-database.config	2006-07-08 12:16:38 UTC (rev 1140)
+++ logcheck/trunk/debian/logcheck-database.config	2006-07-08 14:11:00 UTC (rev 1141)
@@ -13,14 +13,13 @@
 # Only show messages about changes on an upgrade
 if [ "$action" = "configure" -a -n "$version" ]; then
     if dpkg --compare-versions "$version" lt "1.2.1"; then
-        db_text low logcheck-database/rules-directories-note || true
         db_text low logcheck-database/standard-rename-note || true
-	db_go || true
+        db_go || true
     fi
 
     if dpkg --compare-versions "$version" lt "1.2.6"; then
-	db_text medium logcheck-database/conffile-cleanup || true
-	db_go || true
+        db_text medium logcheck-database/conffile-cleanup || true
+        db_go || true
     fi
 fi
 

Modified: logcheck/trunk/debian/logcheck-database.templates
===================================================================
--- logcheck/trunk/debian/logcheck-database.templates	2006-07-08 12:16:38 UTC (rev 1140)
+++ logcheck/trunk/debian/logcheck-database.templates	2006-07-08 14:11:00 UTC (rev 1141)
@@ -1,29 +1,3 @@
-Template: logcheck-database/rules-directories-note
-Type: note
-_Description: Local modifications should be put into .d directories
- From version 1.1.1-8, logcheck supports run-parts controled rule
- directories:
- .
-  - /etc/logcheck/cracking.d
-  - /etc/logcheck/cracking.ignore.d [for local use only]
-  - /etc/logcheck/violations.d
-  - /etc/logcheck/violations.ignore.d
-  - /etc/logcheck/ignore.d.workstation
-  - /etc/logcheck/ignore.d.server
-  - /etc/logcheck/ignore.d.paranoid
- .
- The ignore.d.{workstation,server,paranoid} directory to be used is set by
- the REPORTLEVEL option in the file "/etc/logcheck/logcheck.conf".
- .
- These directories may contain files prefixed with "logcheck-" (containing
- generic alert/override patterns), named "(packagename)" (containing patterns
- specific to that one package), or named "local" respectively prefixed with
- "local-" (created by the local administrator to contain patterns tailored for
- a particular site).  Logcheck will then use rules collected from all the files
- found in the appropriate directories.
- .
- Please see /usr/share/doc/logcheck for more details.
-
 Template: logcheck-database/standard-rename-note
 Type: note
 _Description: Logcheck standard rulefiles renamed




More information about the Logcheck-commits mailing list