Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45288 - [python-sphinx] sphinx 1.3 important regression

Attached to Project: Community Packages
Opened by Michel (xantares) - Wednesday, 10 June 2015, 11:48 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 05 July 2015, 09:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

hello,

there's this huge regression in current sphinx:
https://github.com/sphinx-doc/sphinx/pull/1828

could that patch be applied here, while a bugfix version is cooked upstream ?
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 05 July 2015, 09:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-sphinx 1.3.1-8
Comment by Doug Newgard (Scimmia) - Wednesday, 10 June 2015, 15:19 GMT
You could try describing the regression.

The patch hasn't been accepted upstream. It would have to be extremely severe for Arch to apply a patch that hasn't been accepted.
Comment by Michel (xantares) - Sunday, 14 June 2015, 11:15 GMT
the regression is that no content is produced
it affects several major python packages (sklearn, pandas ...)
is it possible to go back to 1.2.3 until a fix is released ?
Comment by Michel (xantares) - Sunday, 05 July 2015, 08:55 GMT
hello,
it has finally been accepted, could this commit be included:
https://github.com/sphinx-doc/sphinx/commit/4c2f693cbf7ec40448e7237383880d701ede6c88

Loading...