On Sat, Aug 12, 2006 at 12:17:21PM -0300, Margarita Manterola wrote:
> I can reproduce this in my machine. It's due to the fact that
> /usr/bin/python points to python2.3 in my box, and smart-notifier's python
> version is "current". Changing this in /var/lib/dpkg/status, "fixes" this
> bug.
>
> Therefore, as discussed with Pierre Habouzit, this is a bug in dh_python,
> which is not placing the correct version in the Python-Version field, and
It looks to me like this is what happens:
smart-notifier has XS-Python-Version set to 2.4 but the binary
package gets Python-Version "current" if built with python2.4 as the
default python.
In my tests with python2.3 as the default, Python-Version is set to 2.4.
In both cases there is no python dependency (only python2.4).
So anyone installing smart-notifier built with python2.4 as the defualt
on a machine with python2.3 as the default experiences breakage when
python-central tries to compile the bytecode for python2.3.
It seems to me that dh_python should set Python-Version to x.y if
XS-Python-Version is x.y regardless of what the current default python
is. At least that is what I would have expected.
> I'm reassigning to debhelper (I'm sorry :-/)
:) No worries. Just my luck to update this in the middle of a python
transition!
> --
> Love,
> Marga
>
>
--
Brian Sutherland
Metropolis - "it's the first movie with a robot. And she's a woman.
And she's EVIL!!"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
