Date: Wed, 6 Dec 1995 18:47:15 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: davidg@root.com Cc: terry@lambert.org, gibbs@freefall.freebsd.org, phk@critter.tfs.com, imb@scgt.oz.au, julian@ref.tfs.com, current@FreeBSD.org Subject: Re: changes in -current..TEST please Message-ID: <199512070147.SAA02995@phaeton.artisoft.com> In-Reply-To: <199512070054.QAA19195@corbin.Root.COM> from "David Greenman" at Dec 6, 95 04:54:12 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> >I am *NOT* deleting files! > > > >I am: > >1) SUP the CVS > >2) cd /sys > >3) cvs update . > > You should be using "cvs update -Pd". su cd /sys cvs update -Pd <<I *really* think I *don't* want 'P'>> [ ... ] cvs [update aborted]: cannot open file .#vfs_init.c.1.13 for comparing: No such file or directory Same problem. I have *ONLY* *EVER* used "cvs co", "vi", and "cvs diff" on the sources in this tree. If I manually add the entries to the history file for the files that get the error, or if I mv file file.bak/cvs co file/mv file.bak file, then the problem goes away. BTW: I have been using CVS for over 2 years now. I am not a newby. This is the first time I'm using an updated copy of a SUP tree locally rather than just NFS mounting the original (even read-only would be sufficient for what I'm doing: checking out, editing, and diffing). > Wrong. It is checking for them in the current directory. If you check out > another copy someplace, I think you'll find that the cvs update *does* work as > expected and that the real problem is your checked out copy has some .# state > that is missing. How it got rm'd I can only guess. When is it created? I am not doing any commands that should cause the thing to be created: I am only ever checking out or diffing using the SUP'ped tree. Where is the state information that a .# file is expected to exist stored? Or in plainer English: why is CVS expecting one to be there when I have done nothing that would require it, and where is this flag so I can hack the thing? That's the incorrect information, so that's where I need to look. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512070147.SAA02995>