[buildd-tools-devel] Bug#778571: Bug#778571: [Reproducible-builds] Bug#790868: sbuild: Please allow sbuild to use a deterministic build path to build packages

[Johannes Schauer]

Hi,

Quoting Benjamin Drung (2015-07-14 21:19:51)
> The idea to bind mount the directory is to avoid build conflicts. When you
> build the same package twice in parallel, one chroot would bind mount
> /build/$package-XXXXXX/$package-$version to
> /usr/src/debian/$package/$full-version and the other
> /build/$package-YYYYYY/$package-$version to
> /usr/src/debian/$package/$full-version. Does this make sense or do I have a
> flaw in my logic?

maybe I have a flaw in mine :) So let me inquire about this last thing you
wrote.

Do you mean to bind mount /build/$package-XXXXXX/$package-$version from the
host running sbuild to /usr/src/debian/$package/$full-version in the schroot
where the build is done? If yes, then why would I want the /build directory on
my host system? That would violate the FHS. Secondly, who would be responsible
to set up /build/$package-XXXXXX and /build/$package-YYYYYY on my host system?
Which permissions would that require?

So maybe you mean it the other way round, to bind mount
/usr/src/debian/$package/$full-version from the host running sbuild to
/build/$package-XXXXXX/$package-$version in the schroot where the build is
done? If yes, then what is XXXXXX? If it is random, then how would it make the
build path reproducible? If it is not random, why does the XXXXXX part exist?

Thanks for bearing with me :)

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20150714/2b356ee1/attachment.sig>