Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Mon, 28 Apr 2003 21:01:00 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cannot checkout cygwin
Message-ID: <20030429010100.GA7710@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <34212183533 DOT 20030428233632 AT familiehaase DOT de> <013e01c30dda$507a2680$78d96f83 AT pomello>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <013e01c30dda$507a2680$78d96f83@pomello>
User-Agent: Mutt/1.4.1i

On Tue, Apr 29, 2003 at 12:02:59AM +0100, Max Bowsher wrote:
>Gerrit P. Haase wrote:
>> Hallo,
>>
>> Getting this error :
>>
>> cvs server: Updating winsup/cygwin
>> P winsup/cygwin/ChangeLog
>> cvs [server aborted]: could not find desired version 1.19 in
>> /cvs/src/src/winsup/cygwin/malloc.cc,v
>
>OK, you've managed to do something REALLY weird to your local copy.

No, that was me.  I moved the old malloc.cc to malloc_wrapper.cc a while ago
and made a new malloc.cc.  I shouldn't have done that but the damage is done
now.

>I suggest "cvs up -A", and if that doesn't work, either delete your working
>copy and check it out again, or try to manually repair your CVS/Entries.

Editing CVS/Entries and removing the malloc.cc entry should fix it.  I don't know
if "cvs up -A" or "cvs up -AC" would work or not.  I suspect not.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/