On Thu, May 26, 2005 at 07:01:07PM +0100, Roger Leigh wrote:
> > It is such that you do not need to have working apt-get/networking
> > inside the chroot. (the chroot typically only has Essential and
> > Build-Essential packages installed, which does not include apt-get
> > AFAIK)
>
> This may or may not be relevant, but I didn't use the packaged sbuild
> scripts to create the chroot. I ran cdebootstrap to create testing
> and unstable chroots ("build" buildd flavour). This came with apt-get
> installed as standard, so it runs in the chroot with no problems.
Indeed, it appears debootstrap's sid.buildd script installs apt as well.
> $ mount | grep chroot/sid
> /dev/mapper/hda_vg-sid_chroot on /srv/chroot/sid type ext3 (rw)
> /dev/pts on /srv/chroot/sid/dev/pts type none (rw,bind)
> tmpfs on /srv/chroot/sid/dev/shm type tmpfs (rw)
> proc on /srv/chroot/sid/proc type proc (rw)
> /dev/mapper/hda_vg-home on /srv/chroot/sid/home type ext3
> (rw,quota,user_xattr)
> /tmp on /srv/chroot/sid/tmp type none (rw,bind)
> /etc/passwd on /srv/chroot/sid/etc/passwd type none (ro,bind)
> /etc/shadow on /srv/chroot/sid/etc/shadow type none (ro,bind)
> /etc/group on /srv/chroot/sid/etc/group type none (ro,bind)
> /etc/resolv.conf on /srv/chroot/sid/etc/resolv.conf type none
> (ro,bind)
>
> This gives me networking and up-to-date config files, at the expense
> of several mount entries.
>
> > Hmm, might be worth a thought, but I think this might be too hard a
> > penalty. It would be better if we manage to get sbuild use the apt
> > configuration from the chroot instead the main root. However, we were
> > unsuccessful thus far with that.
>
> I agree that a conflict is far from ideal. If there's a way around
> that, I'd much prefer it.
>
> Why is networking not normally set up in the chroot? With my setup,
> it's perfectly possible to run apt in the chroot.
The question rather is: Why does sbuild not run apt in the chroot? I
guess the answer is: "Because upstream's (i.e. the one used on the
official buildds) does not either, and there was no convincing argument
to change it".
(Perhaps an answer to your above question is: "So that maintainers don't
get silly ideas like apt-getting/wgetting something during the build",
btw)
Now, if you (or somebody else) comes up with a patch, we might consider
including it.
However, I am a bit worried that this might break sbuild on hurd-i386,
as networking inside the chroot is AFAIK not known to work reliably on
the Hurd, and users of sbuild have reported trouble with it (though
perhaps they were unrelated).
Michael
--
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
