Hi Santiago, Quoting Santiago Vila (2016-05-26 13:19:10) > I used sbuild to build gcc-6-cross-ports. > > The build log had this as the last line: > > Build needed 15:13:17, 2194502040k disc space > > That would be more than 2000 GB, but there is simply no way this may > be possible, because the build was made on a virtual machine and > the virtual disk had a size of 24 GB.
the effect you original saw and which made you submit this bug can be explained by the issue Helge found. If the package you are building produces many build artifacts, then the size of the unpacked source will repeatedly be added, possibly resulting in very large sizes. I think the patch I propose should fix your problem. You are of course welcome to make this change to your local sbuild installation to verify that it really does. The reason I never saw this issue myself is also easily explained. I never built packages with more than one binary as a test case. Thus, the loop only doubled the size of the unpacked source which sounds plausible. Thanks! cheers, josch
signature.asc
Description: signature
