[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:54:33)
> Time to check the current behaviour and to rethink. :) Let's take the sl
> package as example. When I build sl, /var/lib/sbuild/build/sl-bRYRkz/ is
> created and the source package is placed there. bRYRkz is the random part.
> /var/lib/sbuild/build is mounted to /var/lib/schroot/mount/$session/build
> (done in /etc/schroot/sbuild/fstab) so that /var/lib/sbuild/build/sl-bRYRkz/
> is accessible as /build/sl-bRYRkz/ inside the chroot.

I think I now further understood what caused my initial confusion. When setting
up sbuild as it is described here https://wiki.debian.org/sbuild and then
building any package, then I don't see any directory being created in my hosts
/var/lib/sbuild/build directory. Funnily, my /etc/schroot/sbuild/fstab *does*
contain the line to mount /var/lib/sbuild/build from the outside to /build
inside the chroot. But somehow this does not seem to happen? Over here, when
running sbuild and investigating `mount` while it is running, I do not see my
/build being bind-mounted or otherwise.

This also explains why during the testing of akira's patch which allows setting
a custom build directory (bug #790868), we were able to use /build/foobar in
concurrent sbuild runs without any build failures because *somehow* /build was
not bind mounted from the outside.

Maybe this is a bug in schroot or sbuild?

Do you also see this behaviour with current sbuild from sid when being set up
like explained in the wiki?

Thanks!

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/20150731/c300705a/attachment.sig>