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

[Holger Levsen]

Author: holger
Date: 2009-12-26 10:21:16 +0000 (Sat, 26 Dec 2009)
New Revision: 587

Added:
   piatti/home/piupartsm/bin/known_problems/output_from_cron_error.conf
   piatti/home/piupartsm/bin/known_problems/problems_and_no_force_error.conf
Modified:
   trunk/debian/changelog
   trunk/piuparts-report.py
Log:
- report packages which failed due to output from cron after removal and due to not enough force being used.



Copied: piatti/home/piupartsm/bin/known_problems/output_from_cron_error.conf (from rev 575, piatti/home/piupartsm/bin/known_problems/command_not_found_error.conf)
===================================================================
--- piatti/home/piupartsm/bin/known_problems/output_from_cron_error.conf	                        (rev 0)
+++ piatti/home/piupartsm/bin/known_problems/output_from_cron_error.conf	2009-12-26 10:21:16 UTC (rev 587)
@@ -0,0 +1,19 @@
+#
+# detect packages with cron file has output with package removed
+#
+COMMAND=`rgrep -E "FAIL: Cron file .* has output with package removed" fail bugged | cut -d " " -f1 | sed -e "s#\.log:.*#.log#" | sort -u 2>/dev/null`
+ISSUE=0
+HEADER='Packages with failed logs because a cron file has output with package removed'
+HELPTEXT='
+<p>
+From <a href="http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.5">http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.5</a>
+</p>
+
+<pre>
+The scripts or crontab entries in these directories should check if all
+necessary programs are installed before they try to execute them. Otherwise,
+problems will arise when a package was removed but not purged since 
+configuration files are kept on the system in this situation.
+</pre>
+
+'

Copied: piatti/home/piupartsm/bin/known_problems/problems_and_no_force_error.conf (from rev 575, piatti/home/piupartsm/bin/known_problems/overwrite_other_packages_files_error.conf)
===================================================================
--- piatti/home/piupartsm/bin/known_problems/problems_and_no_force_error.conf	                        (rev 0)
+++ piatti/home/piupartsm/bin/known_problems/problems_and_no_force_error.conf	2009-12-26 10:21:16 UTC (rev 587)
@@ -0,0 +1,15 @@
+#
+# detect packages with problems because of not enough force
+#
+COMMAND=`rgrep "E: There are problems and -y was used without --force-yes" fail bugged | cut -d " " -f1 | sed -e "s#\.log:.*#.log#" | sort -u 2>/dev/null`
+ISSUE=0
+HEADER='Packages with failed logs because of not enough force'
+HELPTEXT='
+<p>
+The piuparts logfile for these packages contains the string <pre>E: There are problems and -y was used without --force-yes</pre>, which is usually an indication, that an essential package needs to be removed to install this package. As piuparts does not use that much force, the piuparts test fails.
+</p>
+<p>
+This is usually not an error in the package and it needs to be seen how piuparts should deal with it.
+</p>
+
+'

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog	2009-12-25 20:36:46 UTC (rev 586)
+++ trunk/debian/changelog	2009-12-26 10:21:16 UTC (rev 587)
@@ -1,7 +1,9 @@
 piuparts (0.39) UNRELEASED; urgency=low
 
   * piuparts-report.py: 
-     - report packages which failed due to broken maintainer scripts.
+     - report packages which failed due to broken maintainer scripts, 
+       due to output from cron after removal and due to not enough force being 
+       used.
      - visual improvements in the output.
      - ignore udebs and binaries from other archs too.
   * piupartsib/packagesdb.py: automatically break circular dependencies when

Modified: trunk/piuparts-report.py
===================================================================
--- trunk/piuparts-report.py	2009-12-25 20:36:46 UTC (rev 586)
+++ trunk/piuparts-report.py	2009-12-26 10:21:16 UTC (rev 587)
@@ -361,6 +361,8 @@
     "post_installation_script_error.tpl": "due to post-installation maintainer script failed",
     "pre_removal_script_error.tpl": "due to pre-removal maintainer script failed",
     "post_removal_script_error.tpl": "due to post-removal maintainer script failed",
+    "output_from_cron_error.tpl": "due to output from cron after removal",
+    "problems_and_no_force_error.tpl": "due to not enough force being used"
 }