From 4c53f625b65425d9ad4d9e27addf8e79e0090716 Mon Sep 17 00:00:00 2001 From: Holger Levsen Date: Wed, 9 Sep 2015 14:58:21 +0200 Subject: document more breakage due to remote builds --- TODO | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/TODO b/TODO index c6c4c3f7..257b1c4d 100644 --- a/TODO +++ b/TODO @@ -170,14 +170,19 @@ properties: === reproducible builds * higher prio: +** reproducible_build.sh changes needed: +*** handle_unhandled() needs to unregister the build from the db too +*** rbuild.log isnt show when a package ftbfs +*** main host should not need to download sources +*** diffoscope needs to be run on the target arch... +**** should probably be doable with qemu-static on the host ** setup builder3, distribute more ressources -** build.sh: handle_unhandled() needs to unregister the build from the db too ** dashboard: include host infos from info.sh in variation table +** dashboard: document usage of -j 24/8/3 in write_explaination_table() ** 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 "

status of $1

" from notes.git/friends.yaml or such ** repo-comparison: check for binaries without source ** link source-data-epoch spec from rb.d.n -** do final s#debbindiff#diffoscope#g and s#dbd#ds#g and rename .debbindiff.html+txt files as well as the dbd directories... ** link howto on each coreboot/openwrt/netbsd/freebsd page ** pkg sets are still amd64 only atm… ** use disorderfs (atm its disabled) @@ -193,6 +198,7 @@ properties: * lesser prio ** reproducible_scheduler.py: why do we have ARCH_SHARE when LIMITS is different for each arch anyway...? legacy? if so -> cleanup... +** 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) *** Acquire::Check-Valid-Until "false" should help, when setting the time to the future ** document (in README) the multihost setup @@ -237,14 +243,6 @@ properties: ** maintenance is general, cleanup of started but interrupted builds... * grep for "locales-all" in build logs… (to confirm that its really used on the new build nodes) -* reproducible_build.sh changes needed: -** diffoscope needs to be run on the target arch... -*** can't this be run via qemu on the host? - -* then we have a new script, reproducible_info.sh which just outputs key-value pairs, like "ARCH=armhf", DATETIME="Mo 10. Aug 11:56:22 CEST 2015" and "TZ=UTC" and whatever. -** this script is run on all nodes, via a for loop on the main node (jenkins atm), as part of dashboard.sh, and the results will be captured in /srv/reproducible-results/node-information/$NODE and then used by reproducible_html_dashboard.sh to create the table with the differences between 1st and 2nd build... -*** document usage of -j 24/8/3 in write_explaination_table() - ==== reproducible Debian armhf * make systems send mail, use port 465 -- cgit v1.2.3-70-g09d2