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
I did, see #548392.
The order is partially based on timestamps, and for a package like
winpdb where setup.py build takes less than 1 second to run on
This craziness (w.r.t. the winpdb install) is fixed with the following
patch to debhelper, but maybe the default should be changed upstream in
Python.
In a nutshell, there's a timestamp comparison going on (in the absence
of a contents comparison). If the dest is newer than the source, no copy
Am Sonntag, den 20.09.2009, 16:25 +0200 schrieb arne anka:
Package: zhone
Version: 0-git20090610-4
Severity: important
When trying to start zhone on a new install created with install.sh
where python-cairo 1.8.6-1+b2 is installed:
# zhone
Traceback (most recent call last):
Joachim Breitner wrote:
it seems that this is actually a bug in dh: It seems to call setup.py
twice, once for each version of python, including adjusting the shebang
line. Then, as the the python version tried last ist 2.4, this modified
script is shipped with the package.
I’m not sure what
hi,
Am Mittwoch, den 23.09.2009, 21:27 +0200 schrieb Jakub Wilk:
We discussed possible breakage in #520834 but missed the case that python
script shebang lines would be modified like this. This seems to be done
by python2.4 setup.py, but not by python2.5 setup.py. In the latter case
you get
* Joey Hess jo...@debian.org, 2009-09-23, 14:49:
it seems that this is actually a bug in dh: It seems to call setup.py
twice, once for each version of python, including adjusting the shebang
line. Then, as the the python version tried last ist 2.4, this modified
script is shipped with the
Joachim Breitner wrote:
hi,
Am Mittwoch, den 23.09.2009, 21:27 +0200 schrieb Jakub Wilk:
We discussed possible breakage in #520834 but missed the case that python
script shebang lines would be modified like this. This seems to be done
by python2.4 setup.py, but not by python2.5 setup.py.
Joey Hess wrote:
Bernd, did you get it backwards when writing the above code?
Build order does not actually matter, but installation order does.
At least in this case, the last python version to run the install
overwrites the script from the other version, so default should be last.
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
Package: zhone
Version: 0-git20090610-4
Severity: important
When trying to start zhone on a new install created with install.sh
where python-cairo 1.8.6-1+b2 is installed:
# zhone
Traceback (most recent call last):
File /usr/bin/zhone, line 74, in ?
import cairo
ImportError: No module
10 matches
Mail list logo
