OK, I've found the problem thanks to a mini debconf debug session: cowbuilder seems to require that ones umask is at least 003, i.e. files are created *world-readable*.
So I can reliably trigger the problem with umask 0077 wereas umask 0002 umask 0003 (anything that does not have the 4 included) On Fri, 2010-05-14 at 08:28 +0900, Junichi Uekawa wrote: > Hi, > > At Fri, 7 May 2010 20:34:37 +0200, > Raphael Hertzog wrote: > > > > severity 575103 important > > thanks > > > > On Tue, 23 Mar 2010, Soeren Sonnenburg wrote: > > > Package: cowdancer > > > Version: 0.61 > > > Severity: grave > > > > > > in a freshly created cowbuilder environment svn-buildpackage failed > > > with > > > > > > I: Extracting source > > > cowdancer: cannot open ilistfile /.ilist > > > cowdancer: Fatal, initialize_functions failed > > > cowdancer: cannot open ilistfile /.ilist > > > cowdancer: cannot open ilistfile /.ilist > > > cowdancer: Fatal, initialize_functions failed > > > cowdancer: cannot open ilistfile /.ilist > > > cowdancer: cannot open ilistfile /.ilist > > > Can't open perl script "/usr/bin/dpkg-source": Cannot allocate memory > > > E: pbuilder: Failed extracting the source > > Have you verified that /.ilist file exists and readable ? > > ENOMEM is an error message that cowdancer uses to signify something is > wrong, and the log message preceding it is usually the problem. > > > regards, > junichi Soeren -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962
signature.asc
Description: This is a digitally signed message part
