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 righ
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.
Nor
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.
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
> >yo
* Joey Hess , 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 package.
I’m not sure
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
6 matches
Mail list logo
