Your message dated Tue, 21 Apr 2009 14:59:23 +0200
with message-id <20090421125923.ga17...@rivendell>
and subject line Re: Bug#523329: Bug still there
has caused the Debian Bug report #523329,
regarding tar: causes dpkg-source extract failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
523329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tar
Version: 1.22-1
Severity: important
Since installing the latest version of tar, I'm getting failures in
attempting to extract certain deb packages. For example, with
telepathy-glib:
....
frobozz:/tmp$ dpkg-source -x telepathy-glib_0.7.29-1.dsc
dpkg-source: extracting telepathy-glib in telepathy-glib-0.7.29
dpkg-source: info: unpacking telepathy-glib_0.7.29.orig.tar.gz
dpkg-source: failure: gunzip died from signal 13
frobozz:/tmp$ ls telepathy-glib-0.7.29.orig/
frobozz:/tmp$
When I try the same thing with the previous version of tar installed,
the package unpacks just fine.
(Never mind the local "+pb1" versions below, I've also reproduced the
same problem in a vanilla pbuilder chroot.)
--
Daniel Schepler
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages tar depends on:
ii libc6 2.9-6+pb1 GNU C Library: Shared libraries
tar recommends no packages.
Versions of packages tar suggests:
ii bzip2 1.0.5-1+pb1 high-quality block-sorting file co
ii ncompress 4.2.4.2-2+pb1 Original Lempel-Ziv compress/uncom
-- no debconf information
--- End Message ---
--- Begin Message ---
found 523329 1.14.25
fixed 523329 1.14.26
thanks
On Tue, 21 Apr 2009, Michael Meskes wrote:
> reopen 523329
Don't do that. You just lost any versioning information associated to the
bug report. You should have used "found 523329 1.14.26" to reopen it
instead.
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building virtualbox-ose using existing
> virtualbox-ose_2.2.0-dfsg.orig.tar.gz
>
> gzip: stdout: Broken pipe
> dpkg-source: failure: gave error exit status 1
> dpkg-buildpackage: failure: dpkg-source -i.git/ -I.git -b virtualbox-ose gave
> error exit status 29
> debuild: fatal error at line 1324:
> dpkg-buildpackage -rfakeroot -D -us -uc -i.git/ -I.git failed
> ...
>
> Downgrading tar to 1.20-1 fixed the problem.
I can't reproduce it. The initial bug report failed at dpkg-source -x
and you're seeing a problem at build time. The initial error message
was "dpkg-source: failure: gunzip died from signal 13" and you get
another error message.
So it's not the same problem. In fact the error message is not normal, it
should have told exactly what command failed and it doesn't (" gave error
exit status 1" instead of "<something> gave error exit status 1").
Can you maybe strace to check what process failed ? It might be tar
itself (in that case, dpkg-source is not to blame).
Anyway, please open a new bugreport about it (not grave, probably
important if it's not a problem like ENOSPC) and give us a way to
reproduce it more reliably. Are you on i386 ? What version of gzip and tar
and dpkg-dev ?
The error message is weird too. It shows gzip but if it fails apparently
during the tar extraction, it should have been gunzip. But if gzip or
gunzip failed, we should have had their name in the error message.
Cheers,
--
Raphaël Hertzog
Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/
--- End Message ---
