From owner-freebsd-current Wed Jul 12 13: 4:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B68F937BDDE for ; Wed, 12 Jul 2000 13:04:47 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA20683; Wed, 12 Jul 2000 13:04:45 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA56370; Wed, 12 Jul 2000 13:04:44 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 12 Jul 2000 13:04:44 -0700 (PDT) Message-Id: <200007122004.NAA56370@vashon.polstra.com> To: brian@Awfulhak.org Subject: Re: **HEADS UP** if you used to cvsup the crypto repo from internat ! In-Reply-To: <200007121405.PAA11870@hak.lan.Awfulhak.org> References: <200007121405.PAA11870@hak.lan.Awfulhak.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200007121405.PAA11870@hak.lan.Awfulhak.org>, Brian Somers wrote: > I haven't looked into it too deeply yet because of other source tree > problems, but if you used to get your crypto ,v files from internat, > you will suffer some funny problems unless you nuke the old checked-out > files. [...] > The problem occurs when you cvsup the new crypto-in-src-all sources > and replace RCS files with different contents and the same version > number. cvs update/checkout compares the repo version number against > the checked out version number and considers the file an ``M'' > (modified source). The file isn't updated and your world gets > corrupted. One thing I'd like to stress is that this only affects you if you're getting the CVS files (*,v) and then using the cvs command to check them out and/or update them. If you are using CVSup in checkout mode (*default tag=something) then you don't need to do anything special. > This is probably a candidate for UPDATING. That wouldn't hurt. But it actually affects _all_ branches, I believe. So in a way, UPDATING doesn't cover enough ground. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message