[buildd-tools-devel] Bug#795466: Option to add bind-mounts to sbuild

[Johannes Schauer]

Hi,

Quoting Joachim Breitner (2015-12-24 09:34:50)
> Am Donnerstag, den 24.12.2015, 01:08 +0100 schrieb Johannes Schauer:
> > On Fri, 14 Aug 2015 10:46:56 +0200 Joachim Breitner  wrote:
> > > it would be really useful to be able to sepecify additional bind-mounts
> > > to sbuild.
> > 
> > this is not an sbuild thing but a schroot thing. You'd specify additional
> > bind-mounts in your schroot config in /etc/schroot/chroot.d
> 
> that doesn’t help with one-shot bind-mounts that I need to set up when
> using sbuild as part of a some infrastructure. But you are right: The
> feature request should be to schroot to have a flag to specify
> additional bind-mounts.

which will probably not happen because schroot is supposed to be run as a user
but the decision about which mounts are allowed should be left to the
superuser. This is currently enforced by only root having the privileges to
edit /etc/schroot/chroot.d/*. If a normal user could bind mount whatever they
want on demand that would be a security issue.

> > > My use case is that I want to make a local repository (file:///)
> > > available as an extra repository. I used --extra-package, but passing
> > > that 2000 times made the builds too slow...
> > 
> > Does --extra-repository not work for you?
> 
> From the explanation it seems that this just adds a line to the
> sources, but how would that help me (without a bind-mount) when the
> repository is local?
> 
> 
> Stepping back from concrete feature request, here is my usecase:
> 
> I have a local directory with many packages that I want to use in my
> sbuild. The directory is temporary, so that rules out static settings
> in /etc/schroot/chroot.d (and also, I’d like to to be able to do this
> with a vanilla schroot configuration). You may assume that the
> directory is usable as an apt source, i.e. a Packages file exists. How can I
> make sbuild use this repository.

What I'm usually doing is to setup a local http server like this:

$ cd /my/pkg/root
$ python3 -m http.server 8000 --bind 127.0.0.1

With this I can then run sbuild with:

--extra-repository="deb http://127.0.0.1:8000/ ./"

Alternatively you could use some of the directories that are already shared
with the sbuild chroot by default like /home and /tmp

Hope this helps!

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/20151224/4cd322c6/attachment.sig>