Your message dated Fri, 10 Jun 2016 10:34:58 +0200
with message-id <[email protected]>
and subject line it's a feature of python3.5, not a bug (at least not in
dh-python)
has caused the Debian Bug report #803310,
regarding dh-python lets the python3.4 test in sphinx-patchqueue succeed
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 [email protected]
immediately.)
--
803310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803310
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-python
Severity: important
python-sphinxqueue has a bogus fix for #802141, just avoiding the build failure.
The underlying problem is that apparently the test step succeeds with
python3.4. But mercurial doesn't have *any* Python3 support. I fail to see why
this succeeds, assuming an issue with pybuild. So why is the missing import
detected with 3.5, but not with 3.4?
Severity important, because it may accept failing tests in other packages as
well.
I'll reopen #802141 for python-sphinxdoc and asking for removal of the python3
package, but please fix dh-python to fail the 0.5-1 package as uploaded.
--- End Message ---
--- Begin Message ---
Control: retitle 803310 python3.5 imports everything, is there a way in pybuild
to change that?
... the answer is: no. Reopen and reassign to python3.5 if you want
--- End Message ---
