Hi peter (2013.11.22_20:36:12_+0200) I assume this was bug was triggered by the thread on pkg-openstack-devel. My reply there hasn't appeared in the archives yet - so I'll repeat the relevant bits here.
> I appreciate that grinding swap on buildds is less than ideal but I > still think it is preferable to not having the package on those > architectures at all. Especially as slow architectures are where > having optimised implementations of stuff is most important. Is that not a decision for those porters to make? What's the disadvantage of letting it continue to try to build there? It seems fairly harmless, to me. After installing the build-deps the package realises there isn't enough RAM, and aborts, wasting only a few minutes of buildd time. Ubuntu has armhf buildds that are capable of building PyPy. I personally have a machine that's capable, and if the Debian armhf porters would like me to, I'd be quite happy to do binary uploads for it, when necessary. There is a JIT implementation for ARM, which makes PyPy builds on that platform a useful thing to have (I think). There also seems to be interest in porting the JIT to MIPS. Someone occasionally posts on the list and IRC channel about it - I doubt we'll see anything any time soon, though. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 461 1230 C: +27 72 419 8559 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
