gzip 1.4-1 creates corrupt archive

Warren Young warren@etr-usa.com
Tue Aug 28 02:43:00 GMT 2012

On 8/25/2012 12:11 AM, Peter wrote:
> cat "$LOG" | gzip > "$LOG.old.gz"

Generally speaking, cat with a single file is a sign you're not using 
redirection to its fullest.  In this case, you get the same effect with 
much less overhead with:

     gzip < "$LOG" > "$LOG.old.gz"

> The resulting archive was corrupt.

Evidenced by...?

I don't disbelieve you, but can't you at least produce a "hello world" 
example file that shows the problem and send it to the list, or put it 
on a public web server somewhere?

>>From my investigation I suspect there is something with textmode and binmode
> but I do not fully understand how to deal with it.

Why do you need the textmode hack?

That is to say, what non-Cygwin tools are you using that truly cannot 
cope with Unix LF line endings, thereby requiring Cygwin to do strange 
things in order to appease the native tools?

(Oh, and in case anyone reading this things I'm being a hypocrite after 
my arguments in the SQLite/svn thread, I'll reiterate that I don't like 
interop hacks and would like to avoid them wherever possible.  I'm 
hoping to find out that it is actually possible here.)

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

More information about the Cygwin mailing list