[Piuparts-commits] rev 543 - piatti/home/piupartsm/bin/known_problems trunk
Holger Levsen
holger at alioth.debian.org
Sat Dec 5 19:16:20 UTC 2009
Author: holger
Date: 2009-12-05 19:16:19 +0000 (Sat, 05 Dec 2009)
New Revision: 543
Added:
piatti/home/piupartsm/bin/known_problems/broken_symlinks_error.conf
Modified:
piatti/home/piupartsm/bin/known_problems/broken_symlinks_issue.conf
trunk/piuparts-report.py
Log:
split view
Copied: piatti/home/piupartsm/bin/known_problems/broken_symlinks_error.conf (from rev 542, piatti/home/piupartsm/bin/known_problems/broken_symlinks_issue.conf)
===================================================================
--- piatti/home/piupartsm/bin/known_problems/broken_symlinks_error.conf (rev 0)
+++ piatti/home/piupartsm/bin/known_problems/broken_symlinks_error.conf 2009-12-05 19:16:19 UTC (rev 543)
@@ -0,0 +1,9 @@
+#
+# detect packages which have the string "Broken symlinks" in their logs
+#
+COMMAND=`rgrep "Broken symlinks" fail bugged |cut -d " " -f1|sed -e "s#\.log:#.log#"|sort -u 2>/dev/null`
+ISSUE=1
+HEADER='Packages which have logs with the string "Broken symlinks"'
+HELPTEXT='
+<p>This is clearly an error, but as there are too many of this kind, piuparts can be configured to not fail if it detects broken symlinks. Another option is not to test for broken symlinks. See the <a href="http://piuparts.debian.org/doc/piuparts.1.html" target="_blank">piuparts manpage</p> for details.</p>
+'
Modified: piatti/home/piupartsm/bin/known_problems/broken_symlinks_issue.conf
===================================================================
--- piatti/home/piupartsm/bin/known_problems/broken_symlinks_issue.conf 2009-12-05 18:55:40 UTC (rev 542)
+++ piatti/home/piupartsm/bin/known_problems/broken_symlinks_issue.conf 2009-12-05 19:16:19 UTC (rev 543)
@@ -1,9 +1,9 @@
#
-# detect packages which have the string "WARN: Broken symlinks" in their logs
+# detect packages which have the string "Broken symlinks" in their logs
#
-COMMAND=`rgrep "Broken symlinks" pass fail bugged |cut -d " " -f1|sed -e "s#\.log:#.log#"|sort -u 2>/dev/null`
+COMMAND=`rgrep "Broken symlinks" pass |cut -d " " -f1|sed -e "s#\.log:#.log#"|sort -u 2>/dev/null`
ISSUE=1
-HEADER='Packages which have logs with the string "WARN: Broken symlinks"'
+HEADER='Packages which have logs with the string "Broken symlinks"'
HELPTEXT='
<p>This is clearly an error, but as there are too many of this kind, piuparts can be configured to not fail if it detects broken symlinks. Another option is not to test for broken symlinks. See the <a href="http://piuparts.debian.org/doc/piuparts.1.html" target="_blank">piuparts manpage</p> for details.</p>
'
Modified: trunk/piuparts-report.py
===================================================================
--- trunk/piuparts-report.py 2009-12-05 18:55:40 UTC (rev 542)
+++ trunk/piuparts-report.py 2009-12-05 19:16:19 UTC (rev 543)
@@ -350,7 +350,8 @@
"unknown_failures.tpl": "unclassified failures",
"initdscript_lsb_header_issue.tpl": "update-rc.d issues",
"command_not_found_issue.tpl": "but logfile contains 'command not found'",
- "broken_symlinks_issue.tpl": "logfile contains 'broken symlinks'",
+ "broken_symlinks_issue.tpl": "but logfile contains 'broken symlinks'",
+ "broken_symlinks_error.tpl": "also logfile contains 'broken symlinks'",
}
More information about the Piuparts-commits
mailing list