From owner-freebsd-current Sun Jun 25 13:53:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BEEF537B5BE; Sun, 25 Jun 2000 13:53:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA02677; Sun, 25 Jun 2000 13:53:41 -0700 Date: Sun, 25 Jun 2000 13:53:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: cvsup/cvs oddities? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 25 Jun 2000, Matthew Jacob wrote: > > > > > Can anyone shed light on why a CVSUP'd dirtree I have now always > > falls down with the following error?... Because it's CVSUP'd, the > > local repository is just /home/ncvs (NFS mounted). I cannot figure out why it > > all of a sudden wants to run off the Freefall ..... > > Check CVS/Root in that directory. If you do a remote cvs operation it > sometimes likes to update the repository to point to freefall, which then > screws up cvs update unless you specify "-d /home/ncvs". I have aliases > lcvs and rcvs which explicitly state the -d to use (I think this advice > came from the committer's guide) Oops. Somehow I had a couple of bad CVS/Root files creep in. The odd thing is that they weren't anywhere &near& where things died. I had to use find/grep to hunt 'em down. Thanks.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message