[Piuparts-commits] [SCM] piuparts git repository branch, develop, updated. 0.44-662-gf196745
Holger Levsen
holger at layer-acht.org
Mon Jun 4 14:21:23 UTC 2012
The following commit has been merged in the develop branch:
commit f1967458b86e46177d12c274c1c3828874b3436e
Author: Holger Levsen <holger at layer-acht.org>
Date: Mon Jun 4 16:21:15 2012 +0200
more cleanup
diff --git a/TODO b/TODO
index be9f228..2575864 100644
--- a/TODO
+++ b/TODO
@@ -17,24 +17,19 @@ for 0.45:
for 0.46:
+- in maintainer view: sort buggy states up again
+
+- more stats and graphs:
+ - packages processed per day (in total and per slave)
+ - # of open bugs with tag piuparts
+ - generate http://piuparts.debian.org/stable/states.png + testing.png
+ from existing data
+
- piuparts-report.py: fix another FIXME in main()
- sometimes a chroot doesn't get removed on piatti - find out
why and fix it.
-- display biggest blockers, either using something like
- lynx --dump http://piuparts.debian.org/$1/state-dependency-failed-testing.html | \
- grep -E "dependency .* is failed-testing" | \
- sed 's#\(.*\)\(\[.*\]\)\(.*\)#\1\3#' | \
- sort|uniq -c| grep -v " 1 "|sort -n | tac
- or https://github.com/davesteele/piublocker
- - actually, don't merely display them on the website, better: use that
- to suggest packages to file bugs against, in the to be written
- bug-submitting-tool - start with the errors which are easy to detect
- reliably.
- The bug-submitting tool should get the bug categories from piupartslib
- and download it's data from a configurationable piuparts install.
-
- copy/move .kpr files to htdocs?
- piuparts-slave should do the rescheduling of old logs and do so with
@@ -47,16 +42,11 @@ for 0.46:
this blog post for a nice howto:
http://andialbrecht.wordpress.com/2009/03/17/creating-a-man-page-with-distutils-and-optparse/
-- publish FAI classes to setup piuparts.$fqdn automatically.
-
- remove the git repository piatti.git.
for 0.47:
-- remove configfile option "mirror" and use the mirror from
- "packages-url".
-
- 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...
@@ -70,9 +60,9 @@ for 0.47:
- piuparts-slave: timestamps to log messages
-- master:
- - write stats about number of daily tests (-> report: create
- fancy graphs)
+- the templates used by update-reports.py should be taken from
+ /etc/piuparts/templates/ and not be included in the python
+ source
for 0.48 and later:
@@ -83,10 +73,6 @@ for 0.48 and later:
etc.) in the chroot might be a good idea because some packages
might need this.
-- the templates used by update-reports.py should be taken from
- /etc/piuparts/templates/ and not be included in the python
- source
-
- report:
- write stats about the reasons for failures, as its done with
shell scripts now (piuparts-analyze.py is an existing
--
piuparts git repository
More information about the Piuparts-commits
mailing list