[Openstack-devel] PyPy out of date on many arch

[Thomas Goirand]

On 11/22/2013 06:02 PM, YunQiang Su wrote:
> On Fri, Nov 22, 2013 at 5:27 PM, Thomas Goirand <zigo at debian.org> wrote:
>> On 11/22/2013 05:12 PM, Thomas Goirand wrote:
>>> Hi Stefano,
>>>
>>> First, thanks for working on the PyPy package.
>>>
>>> PyPy is a dependency for many packages in Debian. On my side, I need
>>> python-simplejson which depends on pypy, then python-wsme depends on
>>> python-simplejson, and last, most of my OpenStack packages depend on
>>> python-wsme. So indirectly, I need PyPy to be working, and migrated to
>>> testing. Though it has been stuck in Sid for 70 days. As a consequence,
>>> python-simplejson, python-wsme & many OpenStack packages can't migrate
>>> to testing as well.
>>>
>>> I had a try with porter boxes, indeed, on armhf and mipsel, PyPy is not
>>> available.
>>>
>>> Do you know what's going on? Do you think a fix could be done anytime
>>> soon? If it can't be fixed for armhf and mipsel, could you declare this
>>> in the debian/control, so that the packages can migrate to testing?
>>>
>>> Last, do you need help?
>>>
>>> Cheers,
>>>
>>> Thomas Goirand (zigo)
>>
>> As sgran pointed out on IRC, there's no mipsel machine with 4GB of RAM,
>> so there's no chance that PyPy will build there. So I would suggest that
>> you just declare PyPy not working on this arch.
> We have a mips(64)el porterbox with 18GB RAM.
> Maybe I can build pypy for mipsel manually by pbuilder.
> Will it a good idea?

Well, if we don't have a buildd with enough RAM, then it's useless, no?
What's the name of the machine? Do you think a buildd could be added
using this kind of configuration/hardware, for the 32 bits port?

Cheers,

Thomas