[Qa-jenkins-scm] [jenkins.debian.net] 01/01: reproducible: add note about DSA packages

Holger Levsen holger at moszumanska.debian.org
Mon May 11 12:56:04 UTC 2015


This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 3034e97f9733404465fb034aeeafcc57593a7371
Author: Holger Levsen <holger at layer-acht.org>
Date:   Mon May 11 14:55:49 2015 +0200

    reproducible: add note about DSA packages
---
 TODO | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/TODO b/TODO
index 6b98ff3..8de1ffc 100644
--- a/TODO
+++ b/TODO
@@ -209,7 +209,7 @@ grep '(=.*).,.$' rygel_0.24.2-1.debbindiff.html | uniq -c | sort | grep -c '^\s*
 
 * pkg sets related:
 ** for all pkg sets: only display FTBR+FTBFS and reproducible packages with notes by default, provide a way to show them all...
-** replace bin/reproducible_installed_on_debian.org with a proper data provider from DSA
+** replace bin/reproducible_installed_on_debian.org with a proper data provider from DSA, eg https://anonscm.debian.org/cgit/mirror/debian.org.git/plain/debian/control
 
 * db schema 2.0
 ** move "untested" field in stats table too? (as in csv output...)
@@ -220,13 +220,13 @@ grep '(=.*).,.$' rygel_0.24.2-1.debbindiff.html | uniq -c | sort | grep -c '^\s*
 ** different cpu type: Opteron_G3  AMD Opteron 23xx (Gen 3 Class Opteron) is the most powerful one that's different to current Opteron_G4
 *** that 2nd slave can also run with a different date (or year, so probably 1984)
 
-* build-slave design:
+* a test VM using this build-slave design has been setup:
 ** 9 cores, 36gb ram, 80gb disk, 50gb /, 30gb /srv/kvm
 ** runs squid3 + kvm
+*** though squid is not configured yet
 ** kvm guest with different cpu, 32gb ram, 8 cores, 30gb /
 ** date changed in /etc/rc.local to 1984
 ** runs pbuilder inside the kmv guest
-** ssh is forwarded to the host
 
 * enable people to upload test packages, to be built in jenkins:
 	<mapreri> h01ger: another wild future request by me: allowing us to upload something and let jenkins test it. rationale: I sent (another) patch for debian-keyring, to fix a timestamp issue in debian control files (due to not_using_dh-builddeb), but there is also a umask issue. I don't want to bother me to setup the very same things jenkins tests locally (I already did too much in this regards, imho), but really people can't tests everything 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git



More information about the Qa-jenkins-scm mailing list