Closed jorti closed 1 year ago
Hi Jorti. That's inconvenient.
There's a really long existing bug in sphinx that causes it to generate cross references in places where it really should not. https://github.com/sphinx-doc/sphinx/issues/2549
In docs/source/conf.py there's a monkey patch for this, from line 363 and further.
It looks like a fix for this was implemented in v4 https://github.com/sphinx-doc/sphinx/pull/8638/commits
-$ git tag --contains 918086b5590763663c1627578085e528f1358384
v4.0.0
[...]
The function that is replaced while applying the workaround has been changed recently, causing the errors you see.
-$ git tag --contains 4534d2d1a5755c8cbc9ef4327eab7e34a85a7de8
v4.1.0
[...]
So, combining this information, it seems that when the major version number of the sphinx lib being used is >= 4, the monkey patch part should be skipped.
I just pushed a change to the develop branch with a little dirty extra amount of duct tape to do this.
Can you test it?
Hi, I can confirm that the commit 99fe101 fixes the issue. I've applied it on top of the v13 tag and the documentation is built successfully with sphinx 4.1.2
Ok, closing now, since it's fixed. Thanks.
The builds of the python-btrfs v13 package have begun to fail in Fedora rawhide with Python 3.10 with this error:
This is the full sphinx backtrace in the file
/tmp/sphinx-err-dfd4p4s4.log
: