Bug#617299: dpkg-deb: should give a hint when it fails due to filling /tmp

[Martin-Éric Racine]

Package: dpkg
Version: 1.16.4.3
Followup-For: Bug #617299

I also encounter the same bug when trying to build kernel 3.2.21 from upstream tarball:

$ LOCALVERSION=-git-686-pae make deb-pkg
[...]
dpkg-deb: building package `firmware-linux' in `../firmware-linux_3.2.21-git-686-pae-1_i386.deb'.
dpkg-deb: building package `linux-headers-3.2.21-git-686-pae' in `../linux-headers-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'.
dpkg-deb: building package `linux-libc-dev' in `../linux-libc-dev_3.2.21-git-686-pae-1_i386.deb'.
dpkg-deb: building package `linux-image-3.2.21-git-686-pae' in `../linux-image-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'.
dpkg-deb (subprocess): data member: internal gzip write error: 'File not found'
dpkg-deb: error: subprocess <compress> from tar -cf returned error exit status 2
make[1]: *** [deb-pkg] Error 2
make: *** [deb-pkg] Error 2

-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (1001, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.5.0-rc6-686-pae (SMP w/2 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-3
ii libc6 2.13-33
ii liblzma5 5.1.1alpha+20120614-1
ii libselinux1 2.1.9-5
ii tar 1.26-4
ii zlib1g 1:1.2.7.dfsg-13

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii apt 0.9.7.1

-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Goswin von Brederlow]

On Fri, Jul 13, 2012 at 08:46:51PM +0300, Martin-�ric Racine wrote:
> 2012/7/13 Martin-�ric Racine <martin-er...@iki.fi>:

> > Package: dpkg
> > Version: 1.16.4.3
> > Followup-For: Bug #617299
> >
> > I also encounter the same bug when trying to build kernel 3.2.21 from upstream tarball:
> >
> > $ LOCALVERSION=-git-686-pae make deb-pkg
> > [...]
> > dpkg-deb: building package `firmware-linux' in `../firmware-linux_3.2.21-git-686-pae-1_i386.deb'.
> > dpkg-deb: building package `linux-headers-3.2.21-git-686-pae' in `../linux-headers-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'.
> > dpkg-deb: building package `linux-libc-dev' in `../linux-libc-dev_3.2.21-git-686-pae-1_i386.deb'.
> > dpkg-deb: building package `linux-image-3.2.21-git-686-pae' in `../linux-image-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'.
> > dpkg-deb (subprocess): data member: internal gzip write error: 'File not found'
> > dpkg-deb: error: subprocess <compress> from tar -cf returned error exit status 2
> > make[1]: *** [deb-pkg] Error 2
> > make: *** [deb-pkg] Error 2
>

> This seems to be caused by either 'tar' or 'gzip' using /tmp to build
> the package. Since recent Debian systems default to using tmpfs for
> /tmp, systems with insufficient memory or with another process using
> all available memory resources will make the build fail. Would there
> perhaps be a way to make this process use /var/tmp or some other
> normal storage space to avoid these nonsensical failures?

No, switching to /var/tmp would make no sense and would in no way fix
the bug. Nothing garanties that /tmp has enough space or that /var/tmp
would have enough space or the build directory. Applications have to
deal with ENOSPC properly.

The bug here is that the error message makes little sense. It should
properly respond with "No space left on device" and hopefully give
a hint that the device in question is /tmp.

And the trigger seems to be the excess size of the build, see other
mails. But fixing that is just doctoring the symptoms.

MfG
Goswin