[Piuparts-commits] rev 835 - piatti/home/piupartsm/bin/known_problems

Holger Levsen holger at alioth.debian.org
Sun Dec 19 13:50:25 UTC 2010


Author: holger
Date: 2010-12-19 13:50:23 +0000 (Sun, 19 Dec 2010)
New Revision: 835

Modified:
   piatti/home/piupartsm/bin/known_problems/db_setup_error.conf
Log:
ignore warning which doesnt cause error

Modified: piatti/home/piupartsm/bin/known_problems/db_setup_error.conf
===================================================================
--- piatti/home/piupartsm/bin/known_problems/db_setup_error.conf	2010-11-30 13:32:20 UTC (rev 834)
+++ piatti/home/piupartsm/bin/known_problems/db_setup_error.conf	2010-12-19 13:50:23 UTC (rev 835)
@@ -1,7 +1,7 @@
 #
 # detect packages with failed to install due to problems configuring the db - see #595652
 #
-COMMAND=`rgrep -E "(dbconfig-common: .* configure: aborted.|updating database schema for .*...command failed with code 0|warning: database package not installed?|psql: could not connect to server: No such file or directory|DBI connect.* failed: could not connect to server)"  fail bugged | cut -d " " -f1 | sed -e "s#\.log:.*#.log#"|sort -u 2>/dev/null`
+COMMAND=`rgrep -E "(dbconfig-common: .* configure: aborted.|updating database schema for .*...command failed with code 0|psql: could not connect to server: No such file or directory|DBI connect.* failed: could not connect to server)"  fail bugged | cut -d " " -f1 | sed -e "s#\.log:.*#.log#"|sort -u 2>/dev/null`
 ISSUE=0
 HEADER='Packages with failed logs because installation failed because no database could be conected.'
 HELPTEXT='




More information about the Piuparts-commits mailing list