increase the build size limit

Asked by Simon Guinot on 2010-06-03

Hi,

Here is the ppa: https://launchpad.net/~sguinot/+archive/net5big-xp
And here is the build failure log message: http://launchpadlibrarian.net/49573645/buildlog_ubuntu-lucid-amd64.linux_2.6.32-21.32%2Bnet5bigxp.1_FAILEDTOBUILD.txt.gz

The interesting part is:

dpkg-deb: building package `linux-image-2.6.32-21-preempt-dbgsym' in `../linux-image-2.6.32-21-preempt-dbgsym_2.6.32-21.32+net5bigxp.1_amd64.deb'.
dpkg-deb (subprocess): data: internal gzip error: read(4096) != write(0): No space left on device
dpkg-deb: subprocess <compress> from tar -cf returned error exit status 2
dh_builddeb: dpkg-deb --build debian/linux-image-2.6.32-21-preempt-dbgsym .. returned exit code 2
make: *** [binary-preempt] Error 9
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2

Apparently, the build fail because there is no space left on the device.
So, could you please increase the build size limit ? 10G _should_ be ok :)

On the other hand, I am not interested in building _all_ the kernel package targets. So I have an extra question. How to set/restrict the ppa build targets ? and how to configure the buildbot behaviour ?

Thanks in advance.

Simon

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
LaMont Jones
Solved:
2010-06-07
Last query:
2010-06-07
Last reply:
2010-06-04
Best LaMont Jones (lamont) said : #1

The builder in question (osmium) as 30GB of space, of which 773MB are used prior to build-dependencies being installed.
If we ran out of disk space, then your build is apparently using far more than 10GB.

As for restricting the flavours built, I know that's simple to do, but do not remember how it is done. That probably wants a second question, against the kernel package.

lamont

Simon Guinot (sguinot) said : #2

Hi Lamont,

30GB of space ? shared with other ppa build ?
Actually the net5bigxp ppa build succeed for the x86 architecture but not for the amd64. So I guess that increase the build size limit could solve this issue.
Could you please try this and trigger a new amd64 build ?

Thanks in advance.

Simon Guinot (sguinot) said : #3

Thanks LaMont Jones, that solved my question.