Hi Vagrant,

On Samstag, 14. Februar 2015, Vagrant Cascadian wrote:
> Prompted by the announcement of reproducible builds status, I took a
> look at a few of my packages and started testing with sbuild... which
> apparently needs a few patches to get reproducible builds working...
> I've got a couple brief proof-of-concept patches.
> One patch sets the build dir to a static location based on the package
> version, rather than a tempdir with a random string.
> The other patch ignores .buildinfo files in the .changes when displaying
> package contents. Without it, the build status gets set to "attempted"
> and is treated as a failed build:

cool! I think it would be good if you could file a wishlist bug against sbuild 
("please add support for reproducible building of packages with sbuild") and 
attach the patches there, so they do get lost.

the current setup on jenkins.d.n just uses pbuilder twice. Maybe we should use 
sbuild once and pbuilder once? Could you help us with patches for that too? I 
at least have no clue about sbuild whatsoever ;-) We'd need to use our custom 
repo anyway, so using an sbuild rebuild plus your two patches is rather 

git clone ssh://git.debian.org/git/qa/jenkins.debian.net.git and then check 
bin/reproducible_build.sh line 193 and 207 to see how pbuilder is used.

Using sbuild once instead should be trivial, no? ;-)

> Thanks for your work towards reproducibility!

Thanks for your contribution!


> p.s. not (yet) subscribed to list, so if you need me to respond, please
> CC me.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reproducible-builds mailing list

Reply via email to