[Pkg-exppsy-maintainers] Bug#570842: Bug#570842: FTBFS: Format: "png" not recognized.

[Cyril Brulebois]

Yaroslav Halchenko <debian at onerussian.com> (22/02/2010):
> This one probably is ok -- there is plenty of those (for some
> reason) before that point as well -- none lead to a failure.  and
> the same happened on kfreebsd-i386 without total failure... it seems
> that there is an issue with graphviz and kfreebsd -- all other archs
> seems had no problem... right?

I didn't check everyone of them. But arch-specific failures are always
possible.

> > | Exception occurred:
> > |   File "/build/buildd-nipy_0.1.2+1741-2.2-kfreebsd-amd64-zNQuQI/nipy-0.1.2+1741/doc/sphinxext/inheritance_diagram.py", line 225, in generate_dot
> > |     fd.write('digraph %s {\n' % name)
> > | IOError: [Errno 32] Broken pipe
> > | The full traceback has been saved in /tmp/sphinx-err-M876vx.log, if you want to report the issue to the developers.
> this is the actual cause... I guess /tmp/sphinx-err-M876vx.log isn't
> available any longer for retrospection (could it simply run out of space
> or smth like that)?

It's lost indeed. Not sure about ENOSPC. There are like 20+ GB
available in that partition if I read “df -h”'s output right.

> would it be possible obtain access to chroot on freebsd64 box with
> all required dependencies? (dchroot on asdfasdf lacks them).

Yes, nipy's BD installed on asdfasdf.

Mraw,
KiBi.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-exppsy-maintainers/attachments/20100222/d9ecfd93/attachment.pgp>