Bug#963659: pybind11: FTBFS with Sphinx 3.1: File "/usr/lib/python3/dist-packages/sphinx/domains/c.py", line 3093, in object_type / raise NotImplementedError()

[Lucas Nussbaum]

Source: pybind11
Version: 2.5.0-4
Severity: important
Tags: ftbfs
User: python-modules-team at lists.alioth.debian.org
Usertags: sphinx3.1

Hi,

pybind11 fails to build with Sphinx 3.1, currently available in
experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>/docs'
> sphinx-build -b html -d .build/doctrees   . .build/html
> Running Sphinx v3.1.1
> making output directory... done
> 1.8.17
> /<<PKGBUILDDIR>>/include/pybind11/operators.h:162: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
> /<<PKGBUILDDIR>>/include/pybind11/pytypes.h:518: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
> /<<PKGBUILDDIR>>/include/pybind11/detail/common.h:472: warning: Detected potential recursive class relation between class make_index_sequence_impl and base class make_index_sequence_impl< N - 1, N - 1, S... >!
> 
> /<<PKGBUILDDIR>>/include/pybind11/detail/common.h:472: warning: Detected potential recursive class relation between class make_index_sequence_impl and base class make_index_sequence_impl< N - 1, N - 1, S... >!
> 
> /<<PKGBUILDDIR>>/include/pybind11/detail/descr.h:57: warning: Detected potential recursive class relation between class int_to_str and base class int_to_str< Rem/10, Rem%10, Digits... >!
> 
> /<<PKGBUILDDIR>>/include/pybind11/detail/descr.h:57: warning: Detected potential recursive class relation between class int_to_str and base class int_to_str< Rem/10, Rem%10, Digits... >!
> 
> /<<PKGBUILDDIR>>/include/pybind11/cast.h:2164: warning: no uniquely matching class member found for 
>   template < Derived >
>   template < policy, Args >
>   object object_api< Derived >::call(Args &&... args) const
> 
> /<<PKGBUILDDIR>>/include/pybind11/detail/common.h:588: warning: explicit link request to 'value' could not be resolved
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 29 source files that are out of date
> updating environment: [new config] 29 added, 0 changed, 0 removed
> reading sources... [  3%] advanced/cast/chrono
> reading sources... [  6%] advanced/cast/custom
> reading sources... [ 10%] advanced/cast/eigen
> reading sources... [ 13%] advanced/cast/functional
> reading sources... [ 17%] advanced/cast/index
> reading sources... [ 20%] advanced/cast/overview
> reading sources... [ 24%] advanced/cast/stl
> reading sources... [ 27%] advanced/cast/strings
> reading sources... [ 31%] advanced/classes
> reading sources... [ 34%] advanced/embedding
> reading sources... [ 37%] advanced/exceptions
> reading sources... [ 41%] advanced/functions
> reading sources... [ 44%] advanced/misc
> reading sources... [ 48%] advanced/pycpp/index
> reading sources... [ 51%] advanced/pycpp/numpy
> reading sources... [ 55%] advanced/pycpp/object
> reading sources... [ 58%] advanced/pycpp/utilities
> reading sources... [ 62%] advanced/smart_ptrs
> reading sources... [ 65%] basics
> reading sources... [ 68%] benchmark
> reading sources... [ 72%] changelog
> reading sources... [ 75%] classes
> reading sources... [ 79%] compiling
> reading sources... [ 82%] faq
> reading sources... [ 86%] index
> reading sources... [ 89%] intro
> reading sources... [ 93%] limitations
> reading sources... [ 96%] reference
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/domains/c.py", line 3093, in object_type
>     raise NotImplementedError()
> NotImplementedError
> The full traceback has been saved in /tmp/sphinx-err-kvkkptxm.log, if you want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error message can be provided next time.
> A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> make[2]: *** [Makefile:55: html] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/23/pybind11_2.5.0-4_unstable_sphinx-exp.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 3.1 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 at packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/3.x/changes.html
[2]: https://www.sphinx-doc.org/en/3.x/extdev/deprecated.html

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.