X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:in-reply-to
	:references:content-type:content-transfer-encoding:mime-version;
	q=dns; s=default; b=MFwyoEWRtaiKYRgFHLRrhMuaOuHmniRSbyK571FlvOr
	Ya6sNgYg+Prfj7bngY5L98xvGxmQ4Y6mEYdxudCVJP7v33iD52hakxrL4MN6ojVf
	JdRejDe5YKzAr0eeRL9FxOjAuwSTVkXgMOzHUgS9uvgZQRuQiTPdV31e/mAK+J1s
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:in-reply-to
	:references:content-type:content-transfer-encoding:mime-version;
	s=default; bh=nkefK+EM0wuiAhYSOB56DqYYisY=; b=O/YhhZ2ayotgOEVzH
	VqRZLpOtMv1XhhrPcADDrlcec9pGml+CNafJw8wKLoOQbq99Bqixw2NdouNsjhHM
	rlqHjDpYjV/SEtSzLDykglQ1Nqpq48M2wE7eYJTLGxeYcimYQwlt2uPCXywWSeZR
	wl6o8vGo2LhQVE12pU8wpQMvcM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=2.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KAM_ASCII_DIVIDERS,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO:	COL004-OMC3S9.hotmail.com
X-TMN:	[oYHdNuEee5CcTJb4LLPYNYFhnG33k2W8]
Message-ID:	<COL130-W103DBAFD945896AC6F7E51C2E00@phx.gbl>
From:	Murthy Gandikota <murthy64 AT hotmail DOT com>
To:	Eric Blake <eblake AT redhat DOT com>, "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: tar zxvf won't work with Redhat generated compressed tar file
Date:	Mon, 20 Apr 2015 23:06:59 +0000
In-Reply-To:	<COL130-W530B6F57CC449D3CD22F44C2E00@phx.gbl>
References:	<COL130-W80F61D41DBC766A5C40206C2E00 AT phx DOT gbl>,<969800560 DOT 20150420222609 AT yandex DOT ru> <COL130-W78804B6BA04135A92CC2FAC2E00 AT phx DOT gbl>,<509379965 DOT 20150420235036 AT yandex DOT ru> <COL130-W65B445CB84F1010DEEDA6EC2E00 AT phx DOT gbl>,<55356CBB DOT 9030601 AT redhat DOT com>,<COL130-W530B6F57CC449D3CD22F44C2E00 AT phx DOT gbl>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t3KN7GLB028319

----------------------------------------
> From: murthy64 AT hotmail DOT com
> To: eblake AT redhat DOT com; cygwin AT cygwin DOT com
> Subject: RE: tar zxvf won't work with Redhat generated compressed tar file
> Date: Mon, 20 Apr 2015 22:00:10 +0000
>
>
>
> ----------------------------------------
>> Date: Mon, 20 Apr 2015 15:16:43 -0600
>> From: eblake AT redhat DOT com
>> To: cygwin AT cygwin DOT com
>> Subject: Re: tar zxvf won't work with Redhat generated compressed tar file
>>
>> On 04/20/2015 03:08 PM, Murthy Gandikota wrote:
>>
>>>>
>>>>> $ tar xvf mytar.gz
>>>>> tar: This does not look like a tar archive
>>>>> tar: Skipping to next header
>>>>> tar: Exiting with failure status due to previous errors
>>>>
>>>> Then what makes you think it is actually a tar archive?
>>>> What
>>>>
>>>> gunzip> mytar < mytar.gz; file mytar
>>>>
>>>> says?
>>>>
>>
>>> Sorry, didn't notice the top-posting.... here is the output to the command
>>>
>>> mytar: gzip compressed data, last modified: Tue Mar 24 03:50:58 2015, from Unix
>>
>> Then it looks like you have a DOUBLE-compressed file. That is, someone
>> took a .tar.gz file, and ran THAT through gzip again (which seldom does
>> anything except make a LARGER file - because the first round of
>> compression removed any redundancy). Tar cannot read a
>> double-compressed stream, but breaking things into two steps lets you
>> get back to a single compressed stream, where the tar call then
>> auto-decompresses because you weren't supplying an explicit 'z' the
>> second time around. To prove it, try:
>>
>> gunzip <mytar.gz>mytar
>> tar zxvf mytar
>>
>> and if it still untars with an explicit decompression, then you have
>> proven that your original file was double-compressed. Also, if I'm
>> right about double compression, then mytar.gz would likely be slightly
>> larger than mytar (rather than the usual case of the .gz being
>> noticeably smaller).
>>
>> --
>> Eric Blake eblake redhat com +1-919-301-3266
>> Libvirt virtualization library http://libvirt.org
>>
>
> Yes, Sir. It did untar properly. So the problem is with the server compressing during the download (I get the file from a http server)?
> Thanks a lot for your help
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

It would be doubly nice if cygwin handled it ;-) It seems gunzip had no problem recognizing the file as double compressed.
Thanks all for the help.
>
 		 	   		  
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -