On 05-Nov-2013, Dmitry Shachnev wrote: > When I tried to build the current Bzr snapshot of python-coverage, I > noticed that in the build log gcc is invoked three times for Python 2 > stuff and one time for Python 3 stuff.
Thanks for noticing this, I hadn't seen that problem. > I used a checkout of that branch, and it has this bug closed in the > changelog. As Barry points out, that's not a signal to anyone but developers using that VCS. The bug report isn't affected until the package is released, regardless of anything it says in the VCS. > That happens because: > > - dh_auto_build builds for python2.7 and python2.7-dbg; > - Your override_dh_auto_build builds for python2.7 and python3.3. I'm trialling the solution for debug builds described at <URL:https://wiki.debian.org/Python/DbgBuilds>, which doesn't consider Python 3 at all. So you're right, and thank you for describing a better solution. > So we can’t consider this bug fixed yet. We don't :-) > My advice will be: > > - Let dh_auto_build cover the python2.7 stuff itself, no need to touch that. > - Make sure your overrides build and install python3 versions of libraries > with both debug and non-debug interpreters. Can you please update <URL:https://wiki.debian.org/Python/DbgBuilds> to incorporate that advice? > You can also consider switching to pybuild, which does all this stuff > automatically. I'm looking into that, but it has more impact on the package that I'd like to be cautious. I'd like to wait until after this bug is fixed. -- \ “Friendship is born at that moment when one person says to | `\ another, ‘What! You too? I thought I was the only one!’” —C.S. | _o__) Lewis | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
