reproducible: updates

1 files changed, 18 insertions, 18 deletions

diff --git a/TODO b/TODO
index 449634d6..efaf4fc1 100644
--- a/TODO
+++ b/TODO
@@ -170,40 +170,41 @@ properties:
 === reproducible builds
 
 * higher prio:
-** cleanup old testing + diffscope schroots on armhf nodes, diffoscope schroots on pb-amd64 nodes and old schroot+pbuilder setups on jenkins
+** notes related:
+*** #786396: classify issue by "toolchain" or "package" fix needed: show bugs which block a bug
+*** new page with annoted packages without categorized issues
+*** new page with packages that have notes with comments (which are often useful / contain solutions / low-hanging fruits for newcomers)
+*** new page with notes that doesnt make sense: a.) packages which are reproducible but should not, packages that build but shouldn't, etc.
+*** new page with packages which are reproducible on one arch and unreproducible on another arch (in the same suite, so unstable only atm)
+*** new page with packages which ftbfs on one arch and build fine on another arch (in the same suite, so unstable only atm)
+*** send notifications to maintainers when a note to their packages changes?
+** new page: packages which are orphaned but have a reproducible usertagged patch
+** cleanup old testing + diffscope schroots on armhf nodes, diffoscope schroots on pb-amd64 nodes and old pbuilder setups on jenkins
 ** reproducible_build.sh changes needed:
 *** fix: "DIFFOSCOPE='E: Failed to change to directory ‘/tmp’: Permission denied" - maybe by making sure the cause is gone…
+*** race condition with itself? https://jenkins.debian.net/job/reproducible_builder_armhf_6/716/console says Warning, package php5 in unstable on armhf is probably already building elsewhere, exiting. Please check https://jenkins.debian.net/job/reproducible_builder_armhf_6/716/ which does not compute.
 *** diffoscope needs to be run on the target arch...
 **** should probably be doable with qemu-static on the host
-*** race condition with itself? https://jenkins.debian.net/job/reproducible_builder_armhf_6/716/console says Warning, package php5 in unstable on armhf is probably already building elsewhere, exiting. Please check https://jenkins.debian.net/job/reproducible_builder_armhf_6/716/ which does not compute.
 *** once all non remote build jobs are removed, remove the legacy code from _build.sh
-** setup builder3, distribute more ressources
+** setup builder3, to distribute more ressources away from jenkins itself
+** test coreboot/openwrt/netbsd/freebsd on a node
 ** explain status in plain english on each coreboot/openwrt/netbsd/freebsd page, also on the Debian dashboard plus add an "executive summary about reproducible builds in the free software world"
 *** get the content for "<h2>status of $1</h2>" from notes.git/friends.yaml or such
-** .py scripts: UDD or any db connection errors should either be retried or cause an abort (not failure!) of the job
+** mattia: .py scripts: UDD or any db connection errors should either be retried or cause an abort (not failure!) of the job
 ** repo-comparison: check for binaries without source
 ** link source-data-epoch spec from rb.d.n
 ** link howto on each coreboot/openwrt/netbsd/freebsd page
 ** pkg sets are still amd64 only atm…
-** use disorderfs (atm its disabled)
-*** current scripts are only in hosts/jenkins/ but need to be copied to hosts/*/
+** use disorderfs:
+*** code is there but disabled, but scripts are only in hosts/jenkins/ and need to be copied to hosts/*/
 *** document usage in diff table...
-** notes related
-*** #786396: classify issue by "toolchain" or "package" fix needed: show bugs which block a bug
-*** new page with annoted packages without categorized issues
-*** new page with packages that have notes with comments (which are often useful / contain solutions / low-hanging fruits for newcomers)
-*** new page with notes that doesnt make sense: a.) packages which are reproducible but should not, packages that build but shouldn't, etc.
-**** aint that covered by reproducible_breakages.py already? no.
-*** send notifications to maintainers when a note to their packages changes?
 
 * lesser prio
-** scheduler: do not try to schedule other suites than unstable on armhf
-** use build3 as (sudo) test system to develop a dsa approvable sudoers.d
+** use build3 (or 5) as (sudo) test system to develop a dsa approvable sudoers.d
 ** do final s#debbindiff#diffoscope#g and s#dbd#ds#g and rename .debbindiff.html+txt files as well as the dbd directories...
-** run amd64 builder 400 days in the past… (that way we will notice problems soon)
+** run pb2-amd64 builder 400 days in the past… (that way we will notice problems soon)
 *** Acquire::Check-Valid-Until "false" should help, when setting the time to the future
 ** document (in README) the multihost setup
-** the setup pbuilder+schroot setup scripts should detect network problems such as "Bad gateway" and sleep 5m and retry once
 ** more graphs:
 *** graph average build duration by day
 *** graph packages in testing+unstable which need to be fixed
@@ -213,7 +214,6 @@ properties:
 *** reproducible_create_meta_pkg_sets uses schroot created by dpkg_setup_schroot_jessie job (outside of reproducible job space...)
 ** "fork" etc/schroot/default into etc/schroot/reproducible
 ** move "untested" field in stats table too? (as in csv output...)
-** new page: packages which are orphaned but have a reproducible usertagged patch
 ** a reproducible_log_grep_by_sql.(py|sh) would be nice, to only grep in packages with a certain status (build in the last X days)
 ** adopt usertag script from pkg-apparmor to notify us about new usertagged bugs automatically
 ** use reprepro and snapshot (reprepro gen-snapshot) on alioth to speed up our repo, maybe. maybe we'll just be in sid soon :-)