Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <004201c30e3c$c9d964c0$78d96f83@pomello> From: "Max Bowsher" To: References: <34212183533 DOT 20030428233632 AT familiehaase DOT de> <013e01c30dda$507a2680$78d96f83 AT pomello> <20030429010100 DOT GA7710 AT redhat DOT com> Subject: Re: cannot checkout cygwin Date: Tue, 29 Apr 2003 11:47:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Christopher Faylor wrote: > 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. But I can repair it if you like. What needs to be done is: In malloc.cc,v: Increase the revision numbers of all existing revisions in this file, and then graft in the revisions from malloc_wrapper.cc,v which actually existed under the name malloc.cc. In malloc_wrapper.cc,v: Set state = dead on those revisions that were grafted into malloc.cc,v . If you would like me to do this, I'd first need you to do: cvs ci -f -r1.27 malloc.cc The log message could be: 'Bump revision number to allow for broken metadata from a bad rename to be fixed' Max. -- 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/