Hi Stefano!
On 02/09/2015 08:07 PM, Stefano Rivera wrote:
Hi John (2015.02.09_00:36:31_+0200)
Please let the decision whether a certain package should be built on
a certain architecture up to the porters.
OK, you make persuasive arguments. I'll remove it.
Thank you very much! I appreciate that.
At the time this check was implemented, many of Debian's architectures
had a wide range of RAM in buildds. There are far fewer "small" buildds
in the supported architectures these days. I think by now, most
architecture that do have some small buildds have blacklisted pypy on
them, so I am not too worried about blocking up the build queue.
Well, it isn't really an issue either way. The m68k buildds have 768 MiB
RAM at most, for example. However, we can use very fast swap areas
(RAM disk boards etc) such that the amount of RAM isn't much of an
issue.
I was more concerned about wasting time architectures with varying RAM
in buildds than archs that only have small buildds, where it'd be
unlikely to build anyway. But I can see why this would be an issue on
those archs.
Yeah, I understand. But normally we will just blacklist the package per
arch or build it manually so that isn't really an issue.
Thanks a lot for your help!
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
