Locking files with cvs

If you find a file name with different case, bingo. To resolve this either you have to manually change the case in the CVS server, or else keep the original name someFile.

You have similarly named but differently cased files in your repository and CVS doesn't know which one to pick. This is due to a fix I recently checked in for a problem where a recase from a case-insensitive system such as Windows would cause an assertion failure and archive corruption.

Now when a CVS server finds two files that would be identical for the case-insensitive system, it refuses to go any further. Windows does not recognize a difference in case of a file, so I think you are out of luck here if you want to use C style case sensitivity in file names If you really want this to be changed for cosmetic reasons then I suggest the following if you have access to the repository directly :.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. CVS cannot lock file? Ask Question. Tag Cloud abbie appfuse birthday denver grails gwt jack java javascript jsf linkedin maven rails roller skiing softwaresummit spring springmvc struts2 tapestry travel trish vacation webframeworks wicket. Is it possible to lock files with CVS? That manual is from subversion, an alternative to CVS.

It's sooo much easier than cvs! Uh, try again Jano. The manual link I gave is from cvshome. For a more direct link to the details on CVS lock try this. An excerpt: Currently the usual way to get reserved checkouts with CVS is the cvs admin -l command see section A.

If no newer revision exists, running update has no effect. If you have edited the file, and a newer revision is available, CVS will merge all changes into your working copy. For instance, imagine that you checked out revision 1.

In the meantime someone else committed revision 1. If you run update on the file now, CVS will incorporate all changes between revision 1.

If any of the changes between 1. In such cases a warning is printed, and the resulting file includes both versions of the lines that overlap, delimited by special markers. See section update--Bring work tree in sync with repository , for a complete description of the update command.

CVS tells you that there were some conflicts. You resolve the conflict by editing the file, removing the markers and the erroneous line.

For your protection, CVS will refuse to check in a file if a conflict occurred and you have not resolved the conflict. Currently to resolve a conflict, you must change the timestamp on the file. In previous versions of CVS, you also needed to insure that the file contains no conflict markers.

If you use release 1. See the documentation for pcl-cvs. It is often useful to inform others when you commit a new revision of a file. See section The modules file. See section Loginfo. You can use these features of CVS to, for instance, instruct CVS to mail a message to all developers, or post a message to a local newsgroup. If several developers try to run CVS at the same time, one may get the following message:. CVS will try again every 30 seconds, and either continue with the operation or print the message again, if it still needs to wait.

If a lock seems to stick around for an undue amount of time, find the person holding the lock and ask them about the cvs command they are running. Note that these locks are to protect CVS's internal data structures and have no relationship to the word lock in the sense used by RCSwhich refers to reserved checkouts see section Multiple developers. Any number of people can be reading from a given repository at a time; only when someone is writing do the locks prevent other people from reading or writing.

For many groups, use of CVS in its default mode is perfectly satisfactory. Users may sometimes go to check in a modification only to find that another modification has intervened, but they deal with it and proceed with their check in.

Other groups prefer to be able to know who is editing what files, so that if two people try to edit the same file they can choose to talk about who is doing what when rather than be surprised at check in time.

The features in this section allow such coordination, while retaining the ability of two developers to edit the same file at the same time. For maximum benefit developers should use cvs edit not chmod to make files read-write to edit them, and cvs release not rm to discard a working directory which is no longer in use, but CVS is not able to enforce this behavior. Command: cvs watch on [ -lR ] files The directory cvs. That is, one must obtain this lock first before creating any of the other locks.

To obtain a read lock, first create the cvs. This operation must be atomic which should be true for creating a directory under most operating systems. If it fails because the directory already existed, wait for a while and try again. After obtaining the cvs.