On 07/20/2010 09:40 PM, Joey Hess wrote: > Christian Kastner wrote: >> When building Python debug extensions, dh_auto_install calls the regular >> interpreters first and the debug interpreters last. > > Sorry, could you please be more clear? dh_auto_install does not build > anything.
Sorry about that. I was referring to the package build in general. > And it runs python interpreters in the same order as > dh_auto_build, with "python" hardcoded to run last. > > You didn't provide any log of a problem, or even the name of a package > exhibiting a problem. I've only been experimenting with building Python extensions for the debug interpreter so far, so all I can offer is a sample package in my personal repo: http://www.kvr.at/debian/pool/main/p/pyrit/pyrit_0.3.0-1.dsc While looking for the smallest possible test case, it appears I was also wrong: the issue seems to originate from dh_auto_build, not dh_auto_install: $ dh build $ head -n 1 build/scripts-2.?/pyrit ==> build/scripts-2.5/pyrit <== #!/usr/bin/python2.5-dbg ==> build/scripts-2.6/pyrit <== #!/usr/bin/python-dbg These merely get copied to debian/tmp during install, apologies for that mixup. I also failed to report that lintian prints a warning in this case: W: pyrit: unusual-interpreter ./usr/bin/pyrit #!/usr/bin/python-dbg I have attached a full build log. Christian
pyrit_0.3.0-1_amd64.build.gz
Description: application/gzip
