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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=u864z0VhZNAVu6TBaWQs+xp+ucJlPFY1d1a+IMJVfcE
	Tmk3V8IJOQvvfIztlr6kzM1wBui/XyAjkDA8H9H5Lu+SB4Rgj5gRhL5g4ZcN5L7E
	fIFIrjpHTTWaRjJUIJ1gy46kVuEH6oy9h8Jrj6/gRZLF9BIlHExEoVg6xRdVwQfY
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=qwWzdWsrR+tNgDb6o++Cwxw+4z8=; b=c5gbeUCqwXTXRErk5
	f8ZxmyTkElTGDnt+JWW5Xx/9swcHVldTs4AwLoBCPAxFXDH11pPSThAGKQKq2JPb
	7ICdt4CkmHQAmydfusqxTWHFM8HTgGegC2D2M6iojuFqHbcG+Pah1G/c2++hKJoc
	FPfBNpK7IlkNAXbGgyiNuiQPIo=
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=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=ham version=3.3.2
X-HELO: bureau85.ns.utoronto.ca
Message-ID: <52556162.2080802@cs.utoronto.ca>
Date: Wed, 09 Oct 2013 10:00:02 -0400
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: checking in >= 256k file fatally corrupts rcs file
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> <20131009070534 DOT GA8855 AT plunk DOT org> <52555C16 DOT 5090505 AT etr-usa DOT com>
In-Reply-To: <52555C16.5090505@etr-usa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 09/10/2013 9:37 AM, Warren Young wrote:
> On 10/9/2013 01:05, Don Hatch wrote:
>> Would it be possible to simply declare 5.8 DOA
>
> The Cygwin package system allows one to mark 5.8-1 as obsolete, but I 
> don't know if it can be told "and downgrade to 5.7-11".
>
>> If not, can we make a 5.9 that's identical to 5.7,
>
> If a new Cygwin package had to come out based on 5.7, it would be 
> called 5.7-12, not 5.9.  GNU rcs 5.9 already exists.  (The current 
> upstream release is 5.9.1.)  Cygwin packages generally leave the 
> upstream revision numbers unmolested.
Or, just roll a 5.8-2 that happens to be compiled from 5.7 sources, or 
from 5.8 sources with the optimization disabled. I suspect it would be 
trivial to disable the optimization in the 5.8 code base. The old 
behavior was almost certainly disk-only, meaning that the bug lies in 
the transition from using the buffer to using disk. Disable buffer usage 
completely and the bug goes away.

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