Bernd Zeimetz wrote: > Normally the scripts are not copied a second time, if they exist at the > destination (have a look at winpdb, for example - if you want to build it in a > chroot, don't forget to s/python/python-all/ in the build-deps. So usually - and > in my experience - dh does the right thing as it is now. > The last time we had such an issue it was due to the setup.py doing weird things > (like creating the to-be-installed script on the fly). I didn't have the time to > investigate in zhone, but I'm kinda sure its an issue with its setup.py. I can reproduce the same problem with winpdb if I comment out the rules file's inclusion of dpatch. The patching changes the mtime of winpdb.py, and that *somehow* causes setup.py to behave differently and in a way that dh_auto_install must accidentially depend on. -- see shy jo
Attachment:
signature.asc
Description: Digital signature