Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 14 Apr 2004 10:36:00 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem with gzip
Message-ID:	<20040414143600.GB5982@coe.bosbc.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<c5ipbn$fsf$1 AT sea DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<c5ipbn$fsf$1@sea.gmane.org>
User-Agent:	Mutt/1.4.1i

On Wed, Apr 14, 2004 at 10:29:54AM +0300, Alex Vinokur wrote:
>Hi,
>
>I have a problem with gzip.
>
>====================
>Windows 2000 Professional
>Cygwin 1.5.5(0.94/3/2)
>gzip 1.3.5 (2002-09-30)
>guzip 1.3.5 (2002-09-30)
>====================
>
>-------------------------
>$ gunzip logs.tar.gz
>
>gunzip: logs.tar.gz: invalid compressed data--crc error
>
>gunzip: logs.tar.gz: invalid compressed data--length error
>-------------------------
>
>See attachment.
>
>P.S. The bug report has been sent to bug-gzip AT gnu DOT org too (2004-04-06).

How about some *details* about how you made the suspect logs.tar.gz
file.  The above errors seem to indicate that gzip is correctly
detecting a damaged .gz file.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -