From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: gzip 1.4-1 creates corrupt archive
Date: Mon, 27 Aug 2012 14:08:00 -0000 [thread overview]
Message-ID: <503B619C.7000700@cs.utoronto.ca> (raw)
In-Reply-To: <CA+sc5m=a0oS0UHCyjAWgDJTaZEgnURdg7qcVYjwfnTp8p1N8Kw@mail.gmail.com>
On 27/08/2012 7:29 AM, Earnie Boyd wrote:
> On Sun, Aug 26, 2012 at 12:38 AM, K Stahl wrote:
>> Missed that section, was reading from my phone. Anyway, how about
>> instead of chastising someone for trying to help, you come up with an
>> alternative solution?
> Stating that you missed something in a post isn't really chastising as
> much as it is criticism that you need to pay attention more. Reading
> from a phone isn't an excuse for miscommunication.
>
*sigh*
It was actually neither. Somebody who seemed to have a clue how to
diagnose this weirdness happened to miss a relevant detail. Happens to
all of us, but I figured if I pointed it out early on it would save the
OP a round trip latency in getting to the next phase of diagnosis, since
the advice given had already been tried.
Unfortunately, it backfired and introduced 2+ rounds of latency instead.
Back on topic, I can't repro using text or binary (executable) files,
which makes me wonder whether the issue is the constant appending the OP
mentioned. Perhaps gzip reads twice from the growing log file in a way
that confuses it, and bzip2 doesn't? Perhaps there's some weirdness with
atimes that makes gzip think the file is unchanged when it actually has
grown?
Ryan
--
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
next prev parent reply other threads:[~2012-08-27 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 11:18 Peter
2012-08-26 3:49 ` K Stahl
2012-08-26 4:39 ` Ryan Johnson
2012-08-26 6:25 ` K Stahl
2012-08-27 13:06 ` Earnie Boyd
2012-08-27 14:08 ` Ryan Johnson [this message]
2012-08-28 0:09 ` KHMan
2012-08-28 2:43 ` Warren Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=503B619C.7000700@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).