DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=ZqFLZOnJjWAuA9id
	QfEVdlW3wik5IqtJ6+qJFpfRcmtbPk1Byo2+ebFUvcRO94K4GLCi22piwpE1cx9A
	46WcXrREakj7kimyvXbjWtrrXfyIOsjZCV+cB/u6BpougBTSCI28ELWW1gDLSEMG
	KtVlHeyJmbnOyTdSLjqiiTrVRYM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 21 Apr 2015 02:33:55 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1033870684.20150421023355@yandex.ru>
To: Murthy Gandikota <murthy64@hotmail.com>, cygwin@cygwin.com
Subject: Re: tar zxvf won't  work with Redhat generated compressed tar file
In-Reply-To: <COL130-W103DBAFD945896AC6F7E51C2E00@phx.gbl>
References: <COL130-W80F61D41DBC766A5C40206C2E00@phx.gbl>,<969800560.20150420222609@yandex.ru>      <COL130-W78804B6BA04135A92CC2FAC2E00@phx.gbl>,<509379965.20150420235036@yandex.ru>  <COL130-W65B445CB84F1010DEEDA6EC2E00@phx.gbl>,<55356CBB.9030601@redhat.com>,<COL130-W530B6F57CC449D3CD22F44C2E00@phx.gbl>  <COL130-W103DBAFD945896AC6F7E51C2E00@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Murthy Gandikota!

>>> 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).
>>
>> 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

> 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.

This is not expected, nor supported. And is unlikely to ever be supported.
Adding "support" for such cases would easily create a shell bomb, if you nest
packers enough times.


-- 
With best regards,
Andrey Repin
Tuesday, April 21, 2015 02:31:44

Sorry for my terrible english...


--
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