On Tue, Jan 29, 2008 at 08:54:41PM +0100, Michael Schmitz wrote:
> > Another proposed solution would be the use of lvm snapshots to build the
> > packages in. Just lvremoving the snapshot would give you a clean chroot
> > again.
> Could be worth a try - no idea how much overhead lvm incurs and whether
> it's noticeable on m68k.
I'll setup the next buildd to use LVM on the chroot partition so we can try
it out...
I suppose the machine to arrive end of this or beginning of next week. DHL
is already instructed to pick up the machine in Nuernberg, so it should be
ready for final setup and such by the end of next week. This will hopefully
bring the backlog down as well.
> > IMHO it is possible to check the build dependency and if it's installable
> > not by the buildd itself, but with a different approach, say on another host
> > with some scripts. This should be doable on a centralized host or database.
> That approach is quite likely to fail - whether a package is installable
> or not solely depends on the particular set of package installed at that
> time. All you can hope for is to figure out if the installation problem is
> supposed to happen with an up to date chroot.
> There may be reasons for not updating the chroot at times :-)
Well, I was aiming at those situation where sbuild starts a build, installs
packages and discovers at that situation that one build-dep is not already
build. ;)
--
Ciao... // Fon: 0381-2744150
Ingo \X/ SIP: [EMAIL PROTECTED]
gpg pubkey: http://www.juergensmann.de/ij/public_key.asc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
