Source: python-m2r Version: 0.2.1-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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:232: /usr/bin/python3 setup.py build > running build > running build_py > copying m2r.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build > running egg_info > creating m2r.egg-info > writing m2r.egg-info/PKG-INFO > writing dependency_links to m2r.egg-info/dependency_links.txt > writing entry points to m2r.egg-info/entry_points.txt > writing requirements to m2r.egg-info/requires.txt > writing top-level names to m2r.egg-info/top_level.txt > writing manifest file 'm2r.egg-info/SOURCES.txt' > reading manifest file 'm2r.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > writing manifest file 'm2r.egg-info/SOURCES.txt' > sphinx-build -b html docs debian/doc/html > Running Sphinx v3.3.1 > > Exception occurred: > File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 266, in > add_source_parser > for filetype in parser.supported: > AttributeError: 'str' object has no attribute 'supported' > The full traceback has been saved in /tmp/sphinx-err-32it295p.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:23: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/11/25/python-m2r_0.2.1-4_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.
