Your message dated Thu, 26 Dec 2013 16:30:57 +0400
with message-id <20131226123057.7309.46292@mitya57.local>
and subject line Re: nipype: FTBFS with Sphinx 1.2: Could not import extension 
inheritance_diagram (exception: cannot import name xfileref_role)
has caused the Debian Bug report #711200,
regarding nipype: FTBFS with Sphinx 1.2: Could not import extension 
inheritance_diagram (exception: cannot import name xfileref_role)
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 ow...@bugs.debian.org
immediately.)


-- 
711200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nipype
Version: 0.8-1
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.2

When rebuilt against python-sphinx 1.2~b1+dfsg-2 (available in experimental), nipype failed to build from source:
| sphinx-build -b html -d _build/doctrees   . _build/html
| Making output directory...
| Running Sphinx v1.2b1
|
| Extension error:
| Could not import extension inheritance_diagram (exception: cannot import name 
xfileref_role)
| make[1]: *** [htmlonly] Error 1
| make[1]: Leaving directory `/build/nipype-LeEbqB/nipype-0.8/doc'
| make: *** [doc-stamp] Error 2

sphinx.roles.xfileref_role was deprecated since Sphinx 1.0 and finally removed in Sphinx 1.2.
sphinx.roles.XRefRole should be used instead.

Note however that Sphinx (>= 0.6) has its own inheritance_diagram extension, which of course works. :) It might be a good idea to use it instead of your own copy. (I didn't check if/how they differ, though.)

--
Jakub Wilk

--- End Message ---
--- Begin Message ---
Version: 0.9-1

This was fixed upstream in 0.9 release, which is now in unstable.

--
Dmitry Shachnev

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to