[Piuparts-commits] rev 848 - trunk

Wed Dec 29 19:39:39 UTC 2010

Author: holger
Date: 2010-12-29 19:39:38 +0000 (Wed, 29 Dec 2010)
New Revision: 848

Modified:
   trunk/TODO
Log:
update & shuffle around

Modified: trunk/TODO
===================================================================

--- trunk/TODO	2010-12-29 16:06:56 UTC (rev 847)
+++ trunk/TODO	2010-12-29 19:39:38 UTC (rev 848)
@@ -13,18 +13,30 @@
   Another approch is for each logfile to check if the package still exist 
   in $distro and if not, delete it.
 
+
+for 0.41:
+
 - provide mail templates for bugreports (which ideally only should need manual
   logfile trimming) at http://$piuparts/$distro/fail/$packages_$version.bug
   for usage by a then to be written tool.
 
-for 0.41:
+- write reportbug(-like) wrapper for mass bug filing (start simple, make it 
+  more sophisticated later). 
 
+
+for 0.42:
+
 - discard logs for packages which have been removed from distro.
 
 - svn mv piatti trunk/doc/examples  and include it into a new binary package. 
   when doing so keep in mind the two tango icons and credit those in 
   debian/copyright.
 
+- publish FAI classes to setup piuparts.$fqdn automatically 
+
+
+for 0.43:
+
 - PackagesDB: get rid of 50% of unique()
 
 - remove configfile option "mirror" and use the mirror from "packages-url".
@@ -36,42 +48,34 @@
 - master:
  - write stats about number of daily tests (-> report: create fancy graphs)
 
-for 0.45 and later:
 
+for 0.44:
+
 - untestable packages are not recognicable as such, see http://piuparts.debian.org/source/a/apache2.html 
   atm. (log is N/A, even though its there, even if empty) - http://piuparts.debian.org/sid/state-cannot-be-tested.html
   aint helpful neither.
 
+- slave_run: cleanup stale proc mountpoints
+
+- the templates used by update-reports.py should be taken from /etc/piuparts/templates/
+  and not be included in the python source
+
+- mounting /proc and perhaps others (usbfs, sysfs, /dev/pts, etc.) in
+  the chroot might be a good idea because some packages might need this.
+  Interestingly enough this currently seems to prevent start-stop-daemon
+  from starting any daemons ;)
+
+
+for 0.45 and later:
+
 - report:
  - write stats about the reasons for failures, as its done with shell scripts now
    (piuparts-analyze.py is an existing "fragment".)
  - RSS feeds of logs
- - maybe packages.txt for binary packages (like sources.txt)
  - do more fancy R graphs, eg. also per state
  - sort packages on maintainer pages alphabetically
  - link (and target) to piuparts.d.o configuration is static to piatti. should refer to the actual hosts configuration, eg goldwassers
 
-- create emacspeak-broken-dpkg-preconfigure package for broken repo. (then later
-  put more broken packages in there and use that for testing piuparts)
-
-- monitor:
- - write slave-watcher to monitor hanging processes, eg. looping dpkg-preconfigure
- - Check for and kill extraneous processes afterwards. Perhaps by checking
-   whether their working directory is in the chroot.
-   Introduce a whitelist of processes to wait for and assume it's an error 
-   if those haven't been killed after $time=10min. see #387428
- - master.log grows to fast and there is no mechanism to stop it
-
-- slave_run: cleanup stale proc mountpoints
-
-- the templates used by update-reports.py should be taken from /etc/piuparts/templates/
-  and not be included in the python source
-
-- write reportbug wrapper for mass bug filing (start simple, make it more sophisticated 
-  later)
-
-- publish FAI classes to setup piuparts.$fqdn automatically 
-
 - a redirect of http://piuparts.d.o/foo to http://p.d.o/source/f/foo.html would be nice
 
 
@@ -87,39 +91,44 @@
   cannot be removed, it assumes these are untestable, which is only true for
   removal tests...
 
+
+Low priority stuff (a.k.a. "nobody's said they must have it now")
+-----------------------------------------------------------------
+
+- create emacspeak-broken-dpkg-preconfigure package for broken repo. (then later
+  put more broken packages in there and use that for testing piuparts)
+
+- monitor:
+ - write slave-watcher to monitor hanging processes, eg. looping dpkg-preconfigure
+ - Check for and kill extraneous processes afterwards. Perhaps by checking
+   whether their working directory is in the chroot.
+   Introduce a whitelist of processes to wait for and assume it's an error 
+   if those haven't been killed after $time=10min. see #387428
+ - master.log grows to fast and there is no mechanism to stop it
+
 - find_default_debian_mirrors: if parts[2] contains a / (think
   stable/updates for security.d.o), you can't ignore this, it will break
   later...
 
-- support for extra-packages-url (for volatile, security, etc)
+- support for extra-packages-url (for backports, security, etc)
 
 - not sure if it's a sensible thing to to, but provide a way to turn off debugging
   output for piuparts.py - see http://docs.python.org/library/logging.html
 
 - commandline-switches for all programms 
 
-- mounting /proc and perhaps others (usbfs, sysfs, /dev/pts, etc.) in
-  the chroot might be a good idea because some packages might need this.
-  Interestingly enough this currently seems to prevent start-stop-daemon
-  from starting any daemons ;)
+- move shell cronjobs functionality into master, slave & report
 
-
-Low priority stuff (a.k.a. "nobody's said they must have it now")
------------------------------------------------------------------
-
-* move shell cronjobs functionality into master, slave & report
-
-* make it possible to call aptitude (or similar) instead of apt-get and 
+- make it possible to call aptitude (or similar) instead of apt-get and 
   allow to override the commandline arguments of the used program (to be 
   able to test with and without recommended packages or authentication).
 
-* Remove --minimize and related options/functionality? Since 0.38 --skip-minimize 
+- Remove --minimize and related options/functionality? Since 0.38 --skip-minimize 
   and --debfoster-options have become quite obsolete (--minimize has been added 
   in 0.38) since debootstrap now creates a minimal chroot.
 
-* Kill children after a timeout to make sure the test doesn't run forever.
+- Kill children after a timeout to make sure the test doesn't run forever.
 
-* piuparts-slave: keep track of reservations permanently
-* piuparts-master: keep track of whom a reservation is made
-* piuparts-slave: timestamps to log messages
-* piuparts: upgrade the chroot before taking a snapshot of its files
+- piuparts-master: keep track of whom a reservation is made
+
+- piuparts-slave: timestamps to log messages


