Hi Benjamin! On Fri, Mar 27, 2020 at 06:01:36PM +0100, Benjamin Drung wrote: > Thanks for reporting this failure. To troubleshoot, I need the full > stack trace that sphinx just saved in /tmp/sphinx-err-r3r4hnih.log. > > Is there an easy way to let sphinx print the stack trace instead of > storing it? Do you have snippets for the Debian packaging?
Call sphinx-build with -T option which makes in print the whole traceback.
In your package, you can change these lines in debian/rules
HTML_THEME=saltstack make -C doc html
SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
HTML_THEME=saltstack make -C doc man
SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
to
HTML_THEME=saltstack make -C doc html
SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build SPHINXOPTS=-T
HTML_THEME=saltstack make -C doc man
SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build SPHINXOPTS=-T
Alternatively, you can use -v which implies -T and makes the output more
verbose (which is in line with Policy ยง 4.9).
--
Dmitry Shachnev
signature.asc
Description: PGP signature
