When building a package with python-all-dbg, dh_auto_build does this: dh_auto_build python2.5-dbg setup.py build python-dbg setup.py build python2.5 setup.py build python setup.py build
This results in build/scripts-2.6/* having python-dbg in the shebang line. Because the default distutils behavior for a script is to not overwrite it if it's already been created in build/. [0] dh_auto_install runs setup.py install --force, so the last python to run wins, which ensures that the script installed has an unversioned python in the shebang. (Bugs #548392 and #547510 explain the whole nasty story behind needing to do that.) It *seems* that bug #589759 can be dealt with by also making dh_auto_build pass --force to setup.py. It certianly fixes it in the case in this bug[1]. It may cause unnecessary work, or who knows, may break something else. So I'm CCing debian-python for advice before doing that. [0| It's also possible for a setup.py to build a script by hand, and always overwrite it. So while running python first and python-dbg second would probably fix this bug in most cases, I am uncomfortable doing that. [1] Tested in the case of pyrit by adding the following to its debian/rules: override_dh_auto_build: dh_auto_build -- --force -- see shy jo
signature.asc
Description: Digital signature