[Qa-jenkins-scm] [jenkins.debian.net] 02/02: reproducible: explain why there are suite specific debbindiff schroots

[Holger Levsen]

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 2e1a80590b58c61895ade3e9698647180fd6a2b2
Author: Holger Levsen <holger at layer-acht.org>
Date:   Thu May 14 14:55:27 2015 +0200

    reproducible: explain why there are suite specific debbindiff schroots
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index a9296ad..5ebc6e8 100644
--- a/README
+++ b/README
@@ -148,7 +148,7 @@ Installation tests inside chroot environments.
 
 * There are suite specific jobs to create the pbuilder base.tgz's per suite, which have the reproducible apt repo added. Similarily there's another job per suite to create the schroots used by the builder jobs to download the packages sources to build.
 
-* Then there is another job to create a sid schroot to run debbindiff on the the two results. (FIXME: explain why here)
+* Then there are two more jobs to create sid and testing schroots to run debbindiff on the the two results. This is neccessary since two investiage haskell binaries, debbindiff needs access to the same haskell compiler version as the investigated packages have been built with.
 
 * Finally, there is a maintenance job running every 4h, making sure things are considerably under control.
 

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