Re: python-wheel backport to Wheezy
On 07/13/2014 07:08 PM, Scott Kitterman wrote:
> On July 13, 2014 6:00:58 AM EDT, Thomas Goirand <zigo@debian.org> wrote:
>> Hi,
>>
>> There's more and more packages in Sid which requires python-wheel. I
>> was
>> wondering if it was possible to do a backport of it. It seems very
>> likely, because the setup.py is handling old stuff like Python prior
>> 2.7. Many backports which used to be trivial aren't anymore because of
>> this.
>>
>> Currently, backporting python-wheel seems to work, except that it does,
>> in Wheezy:
>>
>> dh_python3 --shebang=/usr/bin/python3
>> mkdir -p debian/python-wheel-common/usr
>> mv debian/python3-wheel/usr/bin debian/python-wheel-common/usr
>> mv: cannot stat `debian/python3-wheel/usr/bin': No such file or
>> directory
>> make[1]: *** [override_dh_python3] Error 1
>>
>> It's looking like to me that it's trying to move
>> /usr/bin/{wheel,wininst2wheel,egg2wheel} inside python-wheel-common,
>> however, they aren't present in debian/python3-wheel/usr/bin when I
>> rebuild in Wheezy. What's the way to fix this correctly? (I could hack
>> something, but I would much prefer to understand)
>>
>> Barry, what do you think? Your thoughts?
>>
>> Cheers,
>>
>> Thomas Goirand (zigo)
>>
>> P.S: Note that even if we decide that an official backport isn't
>> appropriate, I'd like to fix the issue for myself in the best possible
>> way.
>
> What packages are there that need it?
The last 2 examples I have in mind: python-six, python-requests. But
there's more. I probably will have multiple iterations in the future
needing new versions (OpenStack always upgrade its six requirements.txt
at least).
On 07/14/2014 12:20 AM, Barry Warsaw wrote:
> Still, this isn't a use case where *distro*
> packages requires them, so it shouldn't be a pressing need for
> backporting. I.e. on wheezy you could just install wheel locally from
> PyPI (in a virtualenv if necessary) and that would support this use
> case.
The thing is, I don't need the -whl packages in Wheezy, but I would like
backporting to be easy (eg: the less modification possible to the
packages from Sid/Testing). Having python-wheel would help a lot in this
regard.
By the way, is there anyone to tell me what's happening when building
wheel in Wheezy as per above? As I wrote, I don't mind to keep my
python-wheel backport in the non-official OpenStack repository, if you
guys think it's not worth having wheel in official Wheezy backports.
Cheers,
Thomas Goirand (zigo)
Reply to: