[pkg-gnupg-maint] Bug#852106: Bug#852106: gpgme1.0: Build allocates 200 GB as a normal thing

[Santiago Vila]

On Mon, Jan 23, 2017 at 05:41:29PM -0500, Daniel Kahn Gillmor wrote:

> I'm open for suggestions for how to address this.  We could just drop
> THREAD_COUNT from 100 to 10 to reduce the RAM consumption, but that
> would mean minimizing some of the concurrency that the test suite is
> (rightly) trying to judge itself against.  I'd rather not remove those
> kinds of checks if we don't need to.
> 
> Any suggestions about what the right thing to do is?  

Just try to be more "normal", i.e. try reducing the memory
requirements to, say, 4 GB, or 8 GB if you really need it.
I would consider 16 GB to be already too much by today's standards,
considering the memory requirements of all the other packages.

I have put the current memory requirements for the packages
that may be built with "dpkg-buildpackage -A" here:

https://people.debian.org/~sanvila/A.memory.txt

Try "sort -k2 -n" on that file and you will see not only that gpgme1.0
is at the end but also how far this package is from the average, the
median, or any other significant statistic measure that you can
imagine.

Of course, there is not a policy anywhere saying "packages must not
use more than X GB of memory", so just apply common sense.

Thanks.