Control: tags -1 + moreinfo On 19-Jan-2018, Jeff Cliff wrote: > from debuild -us -uc -b : > > x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -g -O2 > -fdebug-prefix-map=/home/themusicgod1/python/python-coverage-4.2+dfsg.1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-3.5/coverage/ctracer/datastack.o > build/temp.linux-amd64-3.5/coverage/ctracer/filedisp.o > build/temp.linux-amd64-3.5/coverage/ctracer/module.o > build/temp.linux-amd64-3.5/coverage/ctracer/tracer.o -o > /home/themusicgod1/python/python-coverage-4.2+dfsg.1/.pybuild/pythonX.Y_3.5/build/coverage/tracer.cpython-35m-x86_64-linux-gnu.so > sphinx-build -N -bhtml doc/ \ > doc/_build/html/ > Running Sphinx v1.4.9 > making output directory...
Thanks for this report. The report does not specify what version of the ‘python-coverage’ source package you are using. Can you set that with a “found” command to the bug tracking system? I see that the example session refers to ‘python-coverage-4.2+dfsg.1’, which implies version “4.2+dfsg.1-2” the version in Debian Stretch. None of the build servers report any such failure for this version <URL:https://buildd.debian.org/status/package.php?p=python-coverage&suite=stretch> so we should first find out what is different about the environment you are using to get this behaviour. -- \ “An eye for an eye would make the whole world blind.” —Mohandas | `\ K. Gandhi | _o__) | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
