[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Strange FTBFS of ppl



On Sat, Jul 05, 2008 at 08:26:46AM +0200, Michael Tautschnig wrote:
> > On Sat, Jul 05, 2008 at 07:11:17AM +0200, Michael Tautschnig wrote:
> > > Hi admins,
> > > 
> > > I'm totally puzzled by the FTBFS of my package ppl on amd64 (well, actually it
> > > also fails on 2 more archs, but that seems to be a different story).
> > > 
> > > Could you please take a short look at
> > > http://buildd.debian.org/fetch.cgi?&pkg=ppl&ver=0.9-4&arch=amd64&stamp=1215163252&file=log
> > > 
> > > and possibly try to re-schedule ppl for another attempt?
> > 
> > It seems to contain:
> > /home/buildd/.dvipsrc: Permission denied
> > 
> > 
> > While /home doesn't exist on the buildds.  Please avoid writing anything
> > there.
> > 
> 
> Sure, I guess I need to forward this one to the TeX maintainers (CC'ed), because
> this is just an artifact of building the PDF documentation.
> 
> But anyway, IMHO this is not the cause of the FTBFS, rather that one seems to be
> odd:
> 
> shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
> Error: dot: can't open Constraint__System_8types_8hh__dep__incl.dot
> Problems running dot: exit code=1, command='dot', arguments='"Constraint__System_8types_8hh__dep__incl.dot" -Tcmap -o "Constraint__System_8types_8hh__dep__incl.map"'
> Could not open file /build/buildd/ppl-0.9/doc/devref.html-dir/conversion_8cc.html for writing

I see:
/home/buildd/.dvipsrc: Permission denied
rm -rf devref.html-dir
TEXINPUTS=/build/buildd/ppl-0.9/doc: doxygen devref.doxyconf-html && rm -rf ppl-devref-0.9-html && mv -f devref.html-dir ppl-devref-0.9-html
[...]
Could not open file /build/buildd/ppl-0.9/doc/devref.html-dir/conversion_8cc.html for writing

And since it all seems to be related to the documentation, I assumed
that's why it failed.  But other buildds seem to have the same messages,
upto the shell-init message.

I'm now assuming that for some reason it failed to start the last
command, because of lack of some resource or something.  I've started it
on the other buildd, and that seems to have worked.


Kurt




Reply to: