-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Banck <[EMAIL PROTECTED]> writes:
> tags 270357 271031 -moreinfo
> tags 270357 271031 -unreproducible
> merge 270357 271031 310863
> thanks
>
> (I guess they are the same, unmerge if not)
>
> On Thu, May 26, 2005 at 02:53:50PM +0100, Roger Leigh wrote:
>> sbuild uses the non-chrooted install of apt, rather than the copy
>> installed inside the chroot. I've not investigated why yet.
>
> 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.
Rather than copying stuff over into the chroot, I used bind mounts:
$ 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.
The sbuild docs don't mention it, but I had to mount /dev/pts, since
the gcc testsuite runs expect, which needs ptys. I notice "official"
chroots e.g. on bruckner don't do this. Do these use old-style BSD
ptys?
>> If apt-listbugs is installed, and requires human interaction before
>> unpacking, sbuild freezes. Removing apt-listbugs from the non-chroot
>> environment allows sbuild to work again. Therefore, I suggest making
>> sbuild conflict with apt-listbugs.
>
> 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.
Regards,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFClg7iVcFcaSW/uEgRAgE6AKDTVT39Tg2EWmnURoOhjDG8KlaB2QCfXM4Z
xT2mqeI8tlfZlP18thrqsKU=
=zxTP
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
