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. 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. > They (we) are in a much better decision to decide that and if we > actually don't want a package to be built at all on a certain > architecture, we just set it to "Not-For-Us" in the wanna-build > database on the buildd master. There is no need for a package > maintainer to influence that. 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. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
