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:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Rl7oRK5RI3YL/a+ZO0HIwLbQY1lCPllJfntrKLHWTCn
	tjFwCf1tdkGQczOHZYB3Rad751OZnqaCnIfQ3uoBNtDv7iSQpSkNjl5CuAfPvnKU
	RL1WsdzSFuGww13w/eYnm4Ualq1Rly+wV4jaN0e+cGUo8gu0Bkf3gEknSVauQCZc
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5535B855.50707@redhat.com>
Date: Mon, 20 Apr 2015 20:39:17 -0600
From: Eric Blake <eblake@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Murthy Gandikota <murthy64@hotmail.com>,
        "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: tar zxvf won't  work with Redhat generated compressed tar file
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>
In-Reply-To: <COL130-W103DBAFD945896AC6F7E51C2E00@phx.gbl>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 04/20/2015 05:06 PM, Murthy Gandikota wrote:
> 
> 
> ----------------------------------------
>> From: murthy64 AT hotmail.com
>> To: eblake AT redhat.com; cygwin AT cygwin.com

No need to CC me - I read the list.  Also, no need to include raw emails
in your reply (we not only ask that you avoid top-posts, but also that
you trim to relevent content).

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

You may want to report that to the owner of the website you were
downloading from.

> 
> It would be doubly nice if cygwin handled it ;-)

I'm not going to add a cygwin-specific patch; you'd get the same
behavior on Linux.  If you want to convince upstream to do double
uncompression in a single process, then it will eventually percolate
downstream; but I don't think anyone will want to take on a patch like that.

> It seems gunzip had no problem recognizing the file as double compressed.

No. Your manual gunzip removed one layer of compression, then your tar
command (with or without the 'z') ran a second gunzip to remove the
second layer of compression.  There was no single process doing double
uncompression.


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

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