The repository currently has the 1.3 version with read only permissions. The attic has the version 1.2 version with also read only permissions. I am not sure how your solution is fixing this!
Main Topics
Browse All TopicsHi,
User A removed a file from CVS repository. A copy of it with ver 1.2 ended up at the attic with dead state. It has read only permissions.
User B added the file back in the project and checked it in. when he tries to commit it he gets error permission denied. This file has a 1.3 version.
What is the best way of putting this file back? shoult I use
cvs up -j<dead revision> -j<revision just before dead> <filename>
or can I manually remove 1.3 version from the repository, move 1.2 version there and check out?
thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: mzalfresPosted on 2007-06-25 at 11:24:08ID: 19357872
In general, removing file from repository and adding it back is not good idea... Some CVS version could have troubles.
I'd make cvs 'forget' anything regarding this file completely, and put just 1.3 version as new to avoid any problems.
Go to repository folders, rename 'your_filename,v' file to some other name and add version 1.3 as a new one. This will result with history loss, but give you clean situation.
I tried to reproduce your problem on my CVS, but my installation just worked.
I did following:
cvs remove <some_file>
cvs ci .
later:
cvs add <the_same_file>
cvs ci .
both went OK without errors, but from the same user. So maybe the problem is not CVS itself, but rather file access rights?