Your message dated Thu, 30 Oct 2014 23:36:02 +0800
with message-id 
<CAKcpw6Wi=p_2SW0E=7SAyezv7=am-7ttzzbhyopkglskeea...@mail.gmail.com>
and subject line Re: nipy: FTBFS with Sphinx 1.2: Could not import extension 
inheritance_diagram (exception: cannot import name xfileref_role)
has caused the Debian Bug report #706532,
regarding nipy: 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.)


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

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

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

--
Jakub Wilk

--- End Message ---
--- Begin Message ---
On Mon, 16 Sep 2013 18:10:00 +0400 Dmitry Shachnev <mity...@gmail.com> wrote:
>
> Control: tags -1 + patch fixed-upstream
>
> This was fixed upstream in this commit:
>
> https://github.com/nipy/nipy/commit/3f961418f96c666f
>

I noticed this bug has been fixed in version: 0.3.0+git262-gbb838d7-1
So I close this bug

> --
> Dmitry Shachnev

--- End Message ---

Reply via email to