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

[Steve M. Robbins]

Hello Gert,

I ran into this issue again today which prompted me to re-read this bug log.

On Sat, 30 Aug 2014 16:15:19 +0200 Gert Wollny <gw.fossdev at gmail.com> wrote:
> > 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)

I can definitely make this change for the next upload.  
Did you ever quantify whether this saves on disk space?

>  - 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.

I think in the coming months there will be an archive-wide automatic debug 
package generation [1] .  We can then drop the -dbg package.  I haven't 
checked, but I suspect it will still require building with -g.

[1]  https://lists.debian.org/debian-devel/2015/08/msg00443.html

Thanks,
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20151004/8746decf/attachment.sig>