Source: case Version: 1.5.3+dfsg-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 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>>' > dh_auto_build > I: pybuild base:217: /usr/bin/python3 setup.py build > running build > running build_py > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/pytest.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/skip.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/case.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/mock.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > copying case/utils.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case/tests > copying case/tests/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_case/build/case/tests > PYTHONPATH=. python3 -m sphinx -N -bhtml docs/ build/html # HTML generator > Running Sphinx v2.4.3 > making output directory... done > loading intersphinx inventory from https://docs.python.org/dev/objects.inv... > loading intersphinx inventory from > https://www.sphinx-doc.org/en/stable/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory 'https://docs.python.org/dev/objects.inv' not fetchable > due to <class 'requests.exceptions.ProxyError'>: > HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded > with url: /dev/objects.inv (Caused by ProxyError('Cannot connect to proxy.', > NewConnectionError('<urllib3.connection.HTTPSConnection object at > 0x7fc021ef99d0>: Failed to establish a new connection: [Errno 111] Connection > refused'))) > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory 'https://www.sphinx-doc.org/en/stable/objects.inv' not > fetchable due to <class 'requests.exceptions.ProxyError'>: > HTTPSConnectionPool(host='www.sphinx-doc.org', port=443): Max retries > exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot > connect to proxy.', NewConnectionError('<urllib3.connection.HTTPSConnection > object at 0x7fc021ef9b80>: Failed to establish a new connection: [Errno 111] > Connection refused'))) > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 9 source files that are out of date > updating environment: [new config] 9 added, 0 changed, 0 removed > reading sources... [ 11%] changelog > reading sources... [ 22%] index > reading sources... [ 33%] reference/case > reading sources... [ 44%] reference/case.case > reading sources... [ 55%] reference/case.mock > Changelog:162: WARNING: Inline emphasis start-string without end-string. > WARNING: __all__ should be a list of strings, not [b'Case', b'ANY', > b'ContextMock', b'MagicMock', b'Mock', b'call', b'patch', b'sentinel', > b'mock', b'skip'] (in module case) -- ignoring __all__ > > Exception occurred: > File "/usr/lib/python3/dist-packages/sphinx/util/docstrings.py", line 28, > in prepare_docstring > content = len(line.lstrip()) > AttributeError: 'tuple' object has no attribute 'lstrip' > The full traceback has been saved in /tmp/sphinx-err-8x44ij56.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:13: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/05/01/case_1.5.3+dfsg-3_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! 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.