Your message dated Tue, 23 Feb 2010 01:11:40 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-exppsy-maintainers] Bug#570842: Bug#570842: FTBFS: 
Format: "png" not recognized.
has caused the Debian Bug report #570842,
regarding FTBFS: Format: "png" not recognized.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
570842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570842
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nipy
Version: 0.1.2+1741-2.2
Severity: important
User: [email protected]
Usertags: kfreebsd

Hi,

your package FTBFS on kfreebsd-amd64:
| checking consistency... done
| preparing documents... done
| writing output... [  1%] api/generated/gen
| writing output... [  2%] api/generated/nipy.algorithms.fwhm
| Format: "png" not recognized. Use one of: dia hpgl mif mp pcl pic vtx
| 
| 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.
| Please also report this if it was a user error, so that a better error 
message can be provided next time.
| Either send bugs to the mailing list at 
<http://groups.google.com/group/sphinx-dev/>,
| or report them in the tracker at 
<http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
| make[1]: *** [htmlonly] Error 1

Full build logs:
  https://buildd.debian.org/status/package.php?suite=unstable&p=nipy

Mraw,
KiBi.



--- End Message ---
--- Begin Message ---
Yaroslav Halchenko <[email protected]> (22/02/2010):
> Would it be possible to get access to a clean chroot with ONLY nipy
> BD installed (well, optimal would be that precisely the same chroot
> where build failed ;)))

No, buildds are restricted. Anyway, we had several other issues with
bind mounts lately, we got rid of them a few minutes ago, I gave your
package back, and it built successfully. I'm closing this bugreport
accordingly.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to