Julian Opificius wrote: > <SNIP> > Larry got me on track by saying the file itself is being used as the > lock file, which explains the lock directory problem. > > However I still have problem that I can't check in a modified file. > Larry suggested that there is a permissions problem on the directory, > but I checked and found that permissions are OK on the project directory > tree - in so far as they're the same as any other directory in the repo. > > Is it fundamentally not possible to check in a modified (head) file that > was originally checked out against a tag, even if sticky tags are cleared? > > Another question: What is the ".recordref,v" file for ? I have one in > the directory in question on the server. > > julian.
A possibility from FAR left field, which user owns ,arinc_interface.vhd and .recordref,v ? perhaps there was a `kill -9` done on a commit and the offending user needs to finish the commit? I would think CVS would clean this up for any user who later did a commit, but they might have to do it a second time (the first time should do the clean up). -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
