> Am 13.07.2017 um 22:50 schrieb Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx>: > > Em Mon, 6 Mar 2017 14:09:27 +0100 > Markus Heiser <markus.heiser@xxxxxxxxxxx> escreveu: > >> This patch brings scalable figure, image handling and a concept to >> embed *render* markups: >> >> * DOT (http://www.graphviz.org) >> * SVG > > Not sure what's happening here, but, after I upgraded to Fedora 26, > with comes with python 3.6, instead of 3.5, this patch is now > causing build problems (with Sphinx 1.4.9, running on a virtual > environment): Are you sure (only) this patch causes the problem? I remember this was a more general problem which unfortunately pops up in the context of this patch .. > $ make SPHINXDIRS=doc-guide htmldocs > SPHINX htmldocs --> file:///devel/v4l/docs/Documentation/output/doc-guide ... > File "/devel/v4l/docs/sphinx_1.4/lib/python3.6/site-packages/docutils/writers/_html_base.py", line 671, in depart_document > assert not self.context, 'len(context) = %s' % len(self.context) > AssertionError: len(context) = 4 SHORT: If one of you see a "AssertionError: len(context) = 4", then update your Sphinx Version LONG: we had already a long ML thread in March about this. Ok, to summarize. The problem here is a chain of problems .. First: there has been a not backward compatible change in the (undocumented?) API in one of Sphinx-doc's dependencies (in docutils 0.13.1). Second: The Sphinx team does not maintain patch levels, see my (return42) request at the Sphinx project: https://github.com/sphinx-doc/sphinx/issues/3212#issuecomment-283756374 Third: distros don't care about such details .. Jon pointed us the LWN article "Package managers all the way down" .. https://lwn.net/Articles/712318/ Back to sphinx .. This error is typical for environments (distros) where a Sphinx 1.4.x is paired with docutils >= 0.13.1 So far I can see, we can only restart the "docutils borkage" thread from Jon & you: https://www.mail-archive.com/linux-doc@xxxxxxxxxxxxxxx/msg09874.html -- Markus -- -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
