On Wed, Oct 04, 2006 at 09:42:14AM +0200, Raphael Hertzog wrote:
> On Wed, 16 Aug 2006, Brian Sutherland wrote:
> > 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.
>
> Can you really reproduce that with the dh_python of debhelper 5.0.37.3 ?
I reproduced the installation problem, but didn't try the build leading
up to it with the latest debhelper.
> I wanted to prepare a patch for this, but I really get 2.4 and not current
> when building smart-notifier with python 2.4...
Yeah, I get the same.
But I will note that the smart-notifier binary in the archive has
Python-Version set to current and build depends on >=5.0.37.2.
So looks like it was only a problem in 5.0.37.2, or something else
changed in between then and now.
Thanks for looking into it.
I guess now the bug should be sent back to smart-notifier to be fixed
with an updated build dependency.
--
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]
