Wouter Verhelst wrote: > On Sat, Jul 17, 2004 at 10:58:57AM +0200, Goswin von Brederlow wrote: > > Wouter Verhelst <wouter@grep.be> writes: > > > In any case, buildd doesn't write to disk what it's doing (the > > > build-progress file is written by sbuild), so if it's aborted > > > incorrectly (i.e., it doesn't have time to write a REDO file), that > > > information goes lost. > > > > > > That's probably a bug, but once you know about it, it's easy to work > > > around (it just means you have to clean up after a crash, but you have > > > to do that anyway, so...) > > > > Which is one of the things realy screwed up on the buildd/sbuild > > combination. > > What's your alternative? Obviously to clean the chroot automatically unless a clean-buildd-shutdown flag was written. Shouldn't be hard to implement. Thiemo
Attachment:
signature.asc
Description: Digital signature