[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#955117: extra-cmake-modules: FTBFS with Sphinx 2.4: Could not import extension ecm (exception: No module named 'sphinxcontrib')



Source: extra-cmake-modules
Version: 5.62.0-1
Severity: important
Tags: ftbfs
User: python-modules-team@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

extra-cmake-modules fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> [ 50%] sphinx-build html: see /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/build-html.log
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs && /usr/bin/sphinx-build -c /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs -d /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/doctrees -b html /<<PKGBUILDDIR>>/docs /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/html > build-html.log
> 
> Extension error:
> Could not import extension ecm (exception: No module named 'sphinxcontrib')
> make[3]: *** [docs/CMakeFiles/documentation.dir/build.make:65: docs/doc_format_html] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/03/26/extra-cmake-modules_5.62.0-1_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sphinx@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


Reply to: