Re: Problem with unlocking files.

[Noel Yap]

--- "Schoep, Grant @ STORM" <address@hidden>
wrote:
> We have a CVS repository here that for some reason
> we can't unlock files
> that have been locked by other users.
> 
> Example:
> user1 goes in a does a "cvs admin -l thisfile".
> user2 now goes in a does a "cvs admin -u thisfile"
> 
> CVS echos "done" for user2. However, it doesn't
> unlock the file. Its like it
> didn't do anything.
> 
> Any clues as to whats wrong? Is there someway that
> the repository is
> configured to disallow this action? If so, how to I
> reenable it.

I can't help you with the problem you're currently
experiencing but I may be able to help you by possibly
eliminating the need for "cvs admin" in your
development process.

Have you taken a look at the "advisory locks" patch
available at SourceForge under project RCVS?  It
enables developers to do "cvs edit -c" and "cvs ci -c"
thereby simulating locks.  Moreover, doing a "cvs edit
-f" will allow multiple developers to "lock" the file
so that they wouldn't have to unlock someone else's
lock.

HTH,
Noel

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/