[Piuparts-commits] rev 364 - piatti/home/piupartss/bin trunk

[Holger Levsen]

Author: holger
Date: 2009-04-19 23:10:21 +0000 (Sun, 19 Apr 2009)
New Revision: 364

Modified:
   piatti/home/piupartss/bin/slave_join
   trunk/TODO
   trunk/piuparts-report.py
Log:
document the broken packages issue in the news section

Modified: piatti/home/piupartss/bin/slave_join
===================================================================
--- piatti/home/piupartss/bin/slave_join	2009-04-19 23:01:15 UTC (rev 363)
+++ piatti/home/piupartss/bin/slave_join	2009-04-19 23:10:21 UTC (rev 364)
@@ -1,4 +1,21 @@
 #!/bin/sh 
+
+# Copyright 2009 Holger Levsen (holger at layer-acht.org)
+# 
+# This program is free software; you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by the
+# Free Software Foundation; either version 2 of the License, or (at your
+# option) any later version.
+# 
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
+# Public License for more details.
+# 
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
 #
 # reattach to an existing slave session
 #

Modified: trunk/TODO
===================================================================
--- trunk/TODO	2009-04-19 23:01:15 UTC (rev 363)
+++ trunk/TODO	2009-04-19 23:10:21 UTC (rev 364)
@@ -39,6 +39,7 @@
   - owned and unowned files after purge (policy 6.8 + 10.7.3)
   - prompts without using debconf (#206684 is pending, will be in policy 3.8.2)
   - left-over processes (10.7.3)
+  - "E: Broken packages" - often indicates a problem with the archive at the time of testing, not with the package being tested
   - unclassified
  - write stats for total number of logs (when a package has more than a log in fail/ or bugged/)
  - include links to http://qa.debian.org/developer.php?login=$maintainer_email or probably

Modified: trunk/piuparts-report.py
===================================================================
--- trunk/piuparts-report.py	2009-04-19 23:01:15 UTC (rev 363)
+++ trunk/piuparts-report.py	2009-04-19 23:10:21 UTC (rev 364)
@@ -342,11 +342,16 @@
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-      <b>2009-04-18</b>: Deleted all failed logfiles which complained about <code>/var/games</code> being present after purge, as this ain't an issue, see #524461.
+      <b>2009-04-20</b>: Deleted 86 more failed logfiles (out of 692 failures in total atm) which were due to broken packages, which most likely are temporarily uninstallable issues - a good indicator for this is that all of those failures happened in sid and none in squeeze. For the future there is a cronjob now, to notify the admins daily of such problems. In more distant future those issues should be detected and avoided.
      </td>
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
+      <b>2009-04-18</b>: Deleted all 14 failed logfiles which complained about <code>/var/games</code> being present after purge, as this ain't an issue, see #524461.
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
       <b>2009-04-04</b>: Deleted all failed logfiles so far for two reasons: until now, only three out of ten failure types where logged with a pattern to search for in the logfiles, now this is done for all ten types of failures. And second, the way of breaking circular dependencies was not bulletproof, thus there were false positives in the failures. Now it should be fine, though maybe this will lead to lots of untestable packages... we'll see.
      </td>
     </tr>