From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 3 09:52:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6476737B401 for ; Sun, 3 Aug 2003 09:52:49 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 433A743F75 for ; Sun, 3 Aug 2003 09:52:48 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.12.3p2/8.12.3) with ESMTP id h73GqlY3004026 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 3 Aug 2003 09:52:47 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.6/8.12.6/Submit) id h73Gqko0001449; Sun, 3 Aug 2003 09:52:46 -0700 (PDT) (envelope-from jdp) Date: Sun, 3 Aug 2003 09:52:46 -0700 (PDT) Message-Id: <200308031652.h73Gqko0001449@strings.polstra.com> To: hackers@freebsd.org From: John Polstra In-Reply-To: <20030803072341.GC298@numachi.com> References: <20030802193548.GH969@numachi.com> <200308022222.h72MM6Jl077237@strings.polstra.com> <20030803072341.GC298@numachi.com> Organization: Polstra & Co., Seattle, WA X-Bogosity: No, tests=bogofilter, spamicity=0.499924, version=0.11.2 Subject: Re: messing with CVS_LOCAL_BRANCH_NUM X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2003 16:52:49 -0000 In article <20030803072341.GC298@numachi.com>, Brian Reichert wrote: > On Sat, Aug 02, 2003 at 03:22:06PM -0700, John Polstra wrote: > > Yes: look for a different approach, or at least backup your local > > repository frequently. There are known bugs in CVSup which can cause > > it to throw away your local branch under certain circumstances. I > > won't have time to fix those issues any time soon. So my advice is, > > don't use the CVS_LOCAL_BRANCH_NUM feature. > > Darn. :/ [...] > So, can the 'certain circumstances' be described, so that I might > avoid them? Or is that just due to inherent wierdness in the whole > CVSup process? The main situation in which it will occur is when somebody has directly manipulated or replaced an RCS file in the master CVS repository. CVSup notices that the client and server have entirely different RCS files, so it does a full replace instead of trying to send just deltas. Ideally this situation should never arise, but in the real world it happens all the time. That's actually the only scenario I know of where the problem should crop up. But on the other hand, I've had some suspicious-sounding reports of CVS_LOCAL_BRANCH_NUM lossage that can't be explained by this alone. Bottom line is, if you value your local branch then you should back it up before every update. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Two buttocks cannot avoid friction." -- Malawi saying