Source: gammu
Version: 1.41.0-1.1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx3.1

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> [100%] Generating Sphinx documentation (html)
> cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/manual && /usr/bin/sphinx-build 
> -c /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/manual/ -n -b html -D 
> latex_paper_size=a4 /<<PKGBUILDDIR>>/docs/manual/ 
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/manual/html
> Running Sphinx v3.1.1
> WARNING: Support for evaluating Python 2 syntax is deprecated and will be 
> removed in Sphinx 4.0. Convert 
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/docs/manual/conf.py to Python 3 syntax.
> 
> Extension error:
> Could not import extension configext (exception: cannot import name 'l_' from 
> 'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))
> make[5]: *** [docs/manual/CMakeFiles/manual-html.dir/build.make:61: 
> docs/manual/CMakeFiles/manual-html] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/23/gammu_1.41.0-1.1_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 sph...@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.

Reply via email to