At Fri, 08 May 2009 21:33:44 +0200, Benjamin Mesing wrote: > > On Fri, 2009-05-08 at 23:47 +0900, Junichi Uekawa wrote: > > At Thu, 07 May 2009 19:08:24 +0200, > > Benjamin Mesing wrote: > > > > > > On Wed, 2009-05-06 at 12:34 +0900, Junichi Uekawa wrote: > > > > Hi, > > > > > > > > At Tue, 05 May 2009 21:20:05 +0200, > > > > Benjamin Mesing wrote: > > > > > > > > > > On Mon, 2009-05-04 at 10:15 +0900, Junichi Uekawa wrote: > > > > > > Hi, > > > > > > > > > > > > It sounds like cdebootstrap or debootstrap is failing. You may want > > > > > > to > > > > > > add some --debug to see who's complaining what, or try reproducing > > > > > > with bare debootstrap command-line. > > > > > > > > > > Weird, enabling --debug makes the problem dissapear (i.e. --create > > > > > finishes successfully). It passes the line where the error occured > > > > > without any problems. > > > > > > > > > > > > > By the way, do you guys have enough free disk space available? > > > > > > > > Most probably cause of this message is package installation failure > > > > inside chroot, and it's either caused by occasional breakage in sid, > > > > or some out-of-diskspace error. > > > > > > Definitely sufficient disk-space available. > > > > Can you actually reproduce the message? > > rerun with a clean /var/cache/pbuilder/base.cow directory, run: > > > > pbuilder create --buildplace /var/cache/pbuilder/base.cow --mirror > > ftp://ftp.fu-berlin.de/pub/unix/linux/mirrors/debian --distribution sid > > --no-targz --extrapackages cowdancer > > > > Which would leave the debug logs somewhere, and look for a debug log > > inside somewhere in /var/cache/pbuilder/base.cow/var/log/bootstrap.log > > which gives more verbose information. (if you aren't able to reproduce with > > any debug options). > > I am able to reproduce the bug with the command line you have given. > However, I didn't find any debug information. Running with --debug makes > everything work again. I've attached the file bootstrap.log for a bad > run, but it seems to contain only the regular output.
I'm unable to reproduce your problem now, so I'm relying on you to debug it. 0. What is the architecture and kernel version? 1. Please paste the log from 'good debug run' you cited as well. 2. Can you use the debootstrap or cdebootstrap command-line displayed from the pbuilder create debug output and see if that will reproduce the problem ? BTW, the log says it stopped in a different place (before you said it was libblkid1, but now it's got further). 'E: Got signal: Broken pipe, cleaning up' is probably just a symptom, I'd like to know what's happening when that's being output. P: Extracting grep P: Extracting gzip P: Extracting hostname P: Extracting mount P: Extracting libsepol1 P: Extracting sysvinit-utils E: Got signal: Broken pipe, cleaning up -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
