Your message dated Tue, 29 Apr 2025 11:25:50 +0000 with message-id <caldq5nxqest7bphqbnjo39-p4caopzahtcnegyytoxxr8gt...@mail.gmail.com> and subject line Re: python-vispy-doc: unhandled failures to build documentation can occur has caused the Debian Bug report #1064607, regarding python-vispy-doc: unhandled failures to build documentation can occur to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: python-vispy Version: 0.14.1-2 Severity: important Dear Maintainer, In the debian/rules build instructions for python-vispy-doc, the make step[1] that builds the package documentation (by using a Makefile in the 'doc' dir) is followed by another command, separated by a semicolon: HOME=$$(mktemp -d);PYTHONPATH=`pybuild --print {build_dir} -p$$(py3versions -dv)` HOME=$$HOME xvfb-run make -C doc html;rm -r $$HOME This means if the (middle) documentation build step fails -- a situation that would usually and correctly result in a FTBFS -- then the subsequent (rm) command is evaluated next, and it is the exit code from _that_ latter command that will determine the success/failure of the make target, and the overall doc package build. It may be possible to separate the commands onto separate lines (with care to make sure that variables are created and access correctly), or less invasively to use boolean AND (&&) separators instead of semi-colons. Regards, James [1] - https://sources.debian.org/src/python-vispy/0.14.1-2/debian/rules/#L18
--- End Message ---
--- Begin Message ---Thanks, Colin!
--- End Message ---
