[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg issue with lzma



Hi All,

> On May 14, 2017, at 11:02 PM, Guillem Jover <guillem@debian.org> wrote:
> 
> Hi!
> 
> On Sun, 2017-05-14 at 18:50:16 +0300, Igor Kozhukhov wrote:
>> i have often issue with my builds on SPARC similar to:
>> 
>> 02:53:00.547 dpkg-deb: building package 'gcc-6-libgcj-tools' in '../gcc-6-libgcj-tools_6.3.0-2-15_solaris-sparc.deb'.
>> 02:53:00.547 	dpkg-deb --build debian/gcc-6-libgo ..
>> 02:53:00.555 dpkg-deb: building package 'gcc-6-libgcj' in '../gcc-6-libgcj_6.3.0-2-15_solaris-sparc.deb'.
>> 02:53:00.555 	dpkg-deb --build debian/gcc-6 ..
>> 02:53:00.555 dpkg-deb: building package 'gcc-6-libgij' in '../gcc-6-libgij_6.3.0-2-15_solaris-sparc.deb'.
>> 02:53:00.555 dpkg-deb: building package 'gcc-6-libgo' in '../gcc-6-libgo_6.3.0-2-15_solaris-sparc.deb'.
>> 02:53:00.556 dpkg-deb: building package 'gcc-6' in '../gcc-6_6.3.0-2-15_solaris-sparc.deb'.
>> 02:53:04.537 dpkg-deb (subprocess): compressing tar member: lzma error: Not enough space
>> 02:53:04.541 dpkg-deb: error: subprocess <compress> from tar -cf returned error exit status 2
>> 02:53:04.547 dh_builddeb: dpkg-deb --build debian/gcc-6-libgij .. returned exit code 2
>> 02:53:04.547 dpkg-deb (subprocess): compressing tar member: lzma error: Not enough space
>> 02:53:04.551 dpkg-deb: error: subprocess <compress> from tar -cf returned error exit status 2
>> 02:53:04.557 dh_builddeb: dpkg-deb --build debian/gcc-6-libgo .. returned exit code 2
>> 02:58:00.412 debian/rules:139: recipe for target 'binary-arch' failed
>> 
>> issue is:
>> dpkg-deb (subprocess): compressing tar member: lzma error: Not enough space
>> 
>> I have SPARC 64bit sun4v T5220 with 32GB RAM & 64 threads.
>> i have a lot of RAM + swap available.
> 
> This looks like you've run out of space on whatever is your TMPDIR
> (or P_tmpdir macro). At least going by the error message, although of
> course the strings for errno values change from system to system, so
> this might be something else, but then getting the actual errno value
> matching that error string, would be helpful.

it is not issue with out of space - because i have a lot of space on SPARC, but i’m using ZFS and /tmp = tmpfs mounted
i can see this issue only on SPARC native hw - sun4v T5220 - where i have 32GB ram, 64 threads, more free space on zfs tdatase and more free space on swap - what is using with tmofs.

> Thanks,
> Guillem


Reply to: