some more TODO. add job-type prefix to chroot-path

1 files changed, 2 insertions, 2 deletions

diff --git a/TODO b/TODO
index f9630dfa..26899a78 100644
--- a/TODO
+++ b/TODO
@@ -24,7 +24,6 @@ About jenkins.debian.net
 ** svn:scm
 * mail notifications (to where?)
 * proper backup (=daily), see bottom of this document for what to backup
-* more tests (see below)
 
 === More minor stuff
 
@@ -65,13 +64,14 @@ About jenkins.debian.net
 * build the manual on every svn commit
 ** later: notify debian-boot@l.d.o and #debian-boot
 * run scripts/digress/
-* bubulle wrote: "Another interesting target would be d-i builds *including non uploaded > packages* (something like "d-i from git repositories" images). That would in some way require to create a quite specific image, with all udebs (while netboot only has udebs needed before one gets a working network setup).
+* bubulle wrote: "Another interesting target would be d-i builds *including non uploaded packages* (something like "d-i from git repositories" images). That would in some way require to create a quite specific image, with all udebs (while netboot only has udebs needed before one gets a working network setup).
 
 === Tests using autopkgtest
 
 * I aware but also lost, after looking at /usr/share/doc/autopkgtest/ - wanna help?
 * https://wiki.ubuntu.com/AutomatedTesting has more information, but help is still welcome to implement this.
 * finding packages with autopkgtests: http://lists.debian.org/debian-qa/2012/11/msg00012.html
+** this only lists a few packages, so a very first test could be to compare this list against this: `wget -q http://http.debian.net/debian/dists/unstable/main/Contents-source.gz -O- | zgrep -m1 -E '^debian/tests/control\s'`, make a job out of it and make it UNSTABLE if the diff is non-zero. And as a second step, run those tests...
 * also see http://dep.debian.net/deps/dep8/
 
 == Installed software that makes jenkins.debian.net run