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

Bug#402482: marked as done (busybox gunzip / zcat fail to decompress validly gzipped files)

Your message dated Mon, 24 Mar 2008 12:59:50 +0100
with message-id <200803241259.52630.thijs@debian.org>
and subject line fixed in 1:1.9.2-1
has caused the Debian Bug report #402482,
regarding busybox gunzip / zcat fail to decompress validly gzipped files
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 owner@bugs.debian.org

402482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402482
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: busybox-udeb
Version: 1:1.1.3-3
Severity: serious

Busybox's gunzip/zcat code does not correctly compress a validly
compressed file (in this case amd64.gz):

# gzip -t (test) says it's ok:
tack:~$ gzip -t -v amd64.gz 
amd64.gz:        OK

# and the normal system versions of gunzip and zcat cope:
tack:~$ gunzip -cd < amd64.gz | wc -l
tack:~$ zcat amd64.gz | wc -l

# But the busybox versions don't:
tack:~$ ./debian/d-i/busybox/bin/gunzip -cd < amd64.gz | wc -l
tack:~$ ./debian/d-i/busybox/bin/zcat amd64.gz | wc -l

The file is created by concatenating several gzipped chunks of data
together, which documentation says is a valid thing to do. The busybox
tools are being confused by this, and only decompressing the first
such block in the file. This just caused a set of daily builds of d-i
CDs to break, hence I'm marking this serious.

Steve McIntyre, Cambridge, UK.                                steve@einval.com
"C++ ate my sanity" -- Jon Rabone

Attachment: signature.asc
Description: Digital signature

--- End Message ---
--- Begin Message ---
Version: 1:1.9.2-1


I've confirmed this bug was indeed fixed in the recent upload of th 1.9.x 


Attachment: pgpMz3WknFW7Q.pgp
Description: PGP signature

--- End Message ---

Reply to: