[Debian-med-packaging] Bug#759794: Bug#759794: insighttoolkit4: FTBFS on amd64 with ENOSPC

[Gert Wollny]

> insighttoolkit4 repeatedly FTBFS on amd64 [1] because of ENOSPC. A
> manual build on porterbox barriere.debian.org reported a need of ~44GB
> while it failed on buildd barber at approx 37GB of disk space.

There are two things that could probably help:

 - change the python-binding dimensions to use only 2 an 3. I enabled
   also 4 because in our lab we have to deal with 3D+t data, but in the
   end using 4D data with python is not such a good idea memory-wise. 
   (On Monday I will check how much this actually saves)
 - build with -g1 or even -g0 (have to look up if this is not against
   Debian Policy).  The python bindings creates a lots of debugging info
   that gets thrown away anyway. We would then also have to disable the
   lib*-dbg package.