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:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=tJ8t
	45ytexVFqDAt1B6fAYMUbh2yZ7mmyOZSC7J2KbjapSSa6QJQumrQcPPLRfCwd1QR
	gwFdYXoPcNvt43E6d+g9CGljAYQYS7oIRnccvXZO1YqW46dOpErCTgonQT6Nl0DN
	CPXNAKptBg2PXOl4HZSsGo0yMx+OQQZgeZdHxpE=
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:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=iI51pQUeYS
	qbyhqcU59K6/gZjTg=; b=Ya82zTq/974KMtV0l+b4nKdT1ex4zgV3DNRGZlBST/
	Wy2GjUX/SH/zZKuJeIzvwVdbVtBYBv42xtqWvRSw74TMtEcY9ohAYsUslRWKwMNx
	5wDvXdITjN1DcCi40v4lzPiK4aVI7X0/YLVwfF7eDm6vD0AImbSFUSj/gaWKDxWu
	Y=
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-Spam-SWARE-Status:	No, score=-0.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	plunk.org
Date:	Wed, 9 Oct 2013 03:05:34 -0400
From:	Don Hatch <hatch AT plunk DOT org>
To:	cygwin AT cygwin DOT com
Cc:	Don Hatch <hatch AT plunk DOT org>
Subject:	Re: checking in >= 256k file fatally corrupts rcs file
Message-ID:	<20131009070534.GA8855@plunk.org>
References:	<20131008102204 DOT GB9241 AT plunk DOT org> <525499E5 DOT 4090608 AT etr-usa DOT com> <20131009003055 DOT GA30082 AT plunk DOT org> <5254B1C0 DOT 9020004 AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<5254B1C0.9020004@etr-usa.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-IsSubscribed:	yes

On Tue, Oct 08, 2013 at 07:30:40PM -0600, Warren Young wrote:
> On 10/8/2013 18:30, Don Hatch wrote:
> >On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote:
> >>On 10/8/2013 04:22, Don Hatch wrote:
> >>>
> >>>Checking in a text file of size >= 256k
> >>>corrupts the rcs file, irretrievably losing most of the contents
> >>
> >>It's documented in the rcs NEWS file:
> >
> >That quote certainly doesn't describe or justify the very serious
> >corruption bug I'm seeing in any way;
> 
> I'm not trying to justify it.  I'm just pointing out that you have
> an expedient workaround for the bug which lets you run on current
> versions of Cygwin rcs.

Ah I see, I misinterpreted the point of your message.

Your workaround feels much too dangerous to me...
if I forget to set the variable, or set it wrong,
or someone else doesn't know about the variable and runs into the bug,
then corruption happens and work is irretrievably lost.
I'll be continuing to use 5.7 instead
(even though I have to go through increasing contortions
to even get 5.7, since it's no longer the current or previous version).

> 
> >it would be really good if the feature
> >could be backed out, and possibly re-introduced at a later time
> >after it has been re-worked so that doesn't break the product.
> 
> If the bug affects GNU rcs on all platforms, it needs to be fixed
> upstream.  Then Cygwin rcs will get the fix when the Cygwin rcs
> package maintainer updates the packages.
> 
> If the bug is in the Cygwin rcs port or in Cygwin itself, the actual
> bug needs to be fixed, rather than hack out the feature that tickles
> the bug.

I certainly agree with you as a long-term plan;
however at this moment, it seems to me,
we have a dangerously broken current version in place
that is causing people to lose data and work
(I lost a significant amount when I hit the bug).

Would it be possible to simply declare 5.8 DOA
and revert the "considered most stable" version to be 5.7?
If not, can we make a 5.9 that's identical to 5.7,
ship that immediately as the "considered most stable" version,
and then we can more leisurely and properly work on figuring out
what went wrong and where?

Don

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