Source: requests Version: 2.25.0+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > PYTHONPATH=. python3 -m sphinx -D html_last_updated_fmt="December 08, 2020" > -N -bhtml docs/ \ > debian/python-requests-doc/usr/share/doc/python-requests-doc/html/ > Running Sphinx v3.4.1 > making output directory... done > loading intersphinx inventory from https://docs.python.org/3/objects.inv... > loading intersphinx inventory from > https://urllib3.readthedocs.io/en/latest/objects.inv... > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 15 source files that are out of date > updating environment: [new config] 15 added, 0 changed, 0 removed > reading sources... [ 6%] api > > Exception occurred: > File "/usr/lib/python3/dist-packages/sphinx/util/typing.py", line 160, in > _restify_py37 > return ':obj:`%s.%s`' % (cls.__module__, cls.__name__) > AttributeError: 'LookupDict' object has no attribute '__name__' > The full traceback has been saved in /tmp/sphinx-err-itgtnj9a.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[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/12/26/requests_2.25.0+dfsg-1_unstable.log 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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. 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.
