[Piuparts-commits] rev 728 - piatti/home/piupartsm/bin/known_problems trunk trunk/debian

Holger Levsen holger at alioth.debian.org
Wed Nov 10 23:37:22 UTC 2010


Author: holger
Date: 2010-11-10 23:37:13 +0000 (Wed, 10 Nov 2010)
New Revision: 728

Added:
   piatti/home/piupartsm/bin/known_problems/error_configuring_db_error.conf
Modified:
   trunk/debian/changelog
   trunk/piuparts-report.py
Log:
 - report packages which failed
       - due to problems configuring a database.



Copied: piatti/home/piupartsm/bin/known_problems/error_configuring_db_error.conf (from rev 708, piatti/home/piupartsm/bin/known_problems/logrotate_error_after_removal_error.conf)
===================================================================
--- piatti/home/piupartsm/bin/known_problems/error_configuring_db_error.conf	                        (rev 0)
+++ piatti/home/piupartsm/bin/known_problems/error_configuring_db_error.conf	2010-11-10 23:37:13 UTC (rev 728)
@@ -0,0 +1,11 @@
+#
+# 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`
+ISSUE=0
+HEADER='Packages with failed logs because installation failed because no database could be conected.'
+HELPTEXT='
+<p>
+Just how buggy these packages really are is discussed in <a href="http://bugs.debian.org/595652" target=_blank>#595652</a> at the moment.
+</p>
+'

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog	2010-11-10 23:26:58 UTC (rev 727)
+++ trunk/debian/changelog	2010-11-10 23:37:13 UTC (rev 728)
@@ -4,11 +4,12 @@
   * piuparts-report.py: 
      - report packages which failed
        - due to broken maintainer scripts, 
-       - due to output from cron after removal
-       - due to not enough force being 
-       - due to a problem with pre-depends.
-       - due to files having been modified after purge.
-       - due to files having disappeared after purge.
+       - due to output from cron after removal,
+       - due to not enough force being,
+       - due to a problem with pre-depends,
+       - due to files having been modified after purge,
+       - due to files having disappeared after purge and
+       - due to problems configuring a database.
      - only report about (un)owned files and directories and symlink issues in
        sid
      - visual improvements in the output.

Modified: trunk/piuparts-report.py
===================================================================
--- trunk/piuparts-report.py	2010-11-10 23:26:58 UTC (rev 727)
+++ trunk/piuparts-report.py	2010-11-10 23:37:13 UTC (rev 728)
@@ -389,6 +389,7 @@
     "pre_depends_error.tpl": "due to a problem with pre-depends",
     "modified_files_after_purge_error.tpl": "due to files having been modified after purge",
     "disappeared_files_after_purge_error.tpl": "due to files having disappeared after purge",
+    "error_configuring_db_error.tpl": "due to problems configuring a database",
 }
 
 




More information about the Piuparts-commits mailing list