[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem finding lock

From: Todd Denniston
Subject: Re: Problem finding lock
Date: Tue, 17 Jul 2007 14:09:56 -0500
User-agent: Thunderbird (X11/20070509)

Simon Renshaw wrote:

One of the dev told me that he got the following error while trying to
commit after he deleted a file: mismatch in rcs file.

So I did a checkout then I went in the directory where the file is, I
removed it then ran cvs remove and cvs commit. Commit failed because
version 1.1 is locked.

the ,v file may have come from an RCS repo, and the locking is still per user.

I asked the dev and he did not lock it. I looked around in the repo but
I cannot find a lock file for it.

A related question: that file is in a directory that I'd like to
completely remove from CVS. I don't need to keep it as an empty
directory. I know that if I use cvs remove to remove everything under
it, CVS won<t checkout the empty directory. If I want to really remove
it, can I just delete the directory from the repo?

You understand the long term risk, that if there was anything in it that was used in an old build, you will no longer be able to construct the old build.

the short term risk/problem is that for each developer sand box that is currently checked out, you need to make a good backup and do one of the following: * before making the change have everyone do a cvs commit of everything they currently have, then cvs release. after making the change (rm) everyone needs to do a new checkout.

* after making the change (rm) you have to have all the developers rm that directory out of their sandboxes.

These directions may have problems, you are using rm in a version control repository which may destroy everything. USE AT YOUR OWN RISK.
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]