Hi again,
Quoting Johannes Schauer (2015-07-31 11:47:01)
> 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
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/buil
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/buil
Am Dienstag, den 14.07.2015, 21:28 +0200 schrieb 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-XXX
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-XX/$package-$version to
> /usr/src/debian/$package/$full-version and the other
Am Samstag, den 11.07.2015, 11:35 +0200 schrieb Johannes Schauer:
> Also, when you talk about the build path being
> /usr/src/debian/$package/$version, then do you mean that the source is
> unpacked
> in that directory directly, so that you get:
>
> /usr/src/debian/$package/$version/debian/rules
6 matches
Mail list logo
