Certain files are checkouted as read-only. Don't know why?

[krevathi1912]

Hi,

We have a CVS where a large no of codes are checked in all the days.
Today files in the ceratain directory alone is checkout as readonly for all
the users.
I am sure no specific restriction is applied on these files.
We dont know what is the reason for it. WE are unable to rectify it also.
Any one help us to rectify this problem.
How to remove the read-only restriction on these files.



Regards
Revathi

[Todd Denniston]

Post by krevathi1912
Hi,
We have a CVS where a large no of codes are checked in all the days.
Today files in the ceratain directory alone is checkout as readonly for all
the users.
I am sure no specific restriction is applied on these files.
We dont know what is the reason for it. WE are unable to rectify it also.
Any one help us to rectify this problem.
How to remove the read-only restriction on these files.
Regards
Revathi

in the directory where these files are read only, try the following command:
cvs watchers -R

I expect you will find someone has used the `cvs watch` command, I did not
think it was supposed to make things RO but it has for me in the past. My
solution for folks who wanted to watch files was to make a script that always
applied watches as `cvs watch add -a commit filename`, and have them use that.

or someone may have used `cvs edit` unnecessarily.

[krevathi1912]

But it doesn't help me. Still the files are checkout as read-only mode

Post by Todd Denniston

Post by krevathi1912
Hi,
We have a CVS where a large no of codes are checked in all the days.
Today files in the ceratain directory alone is checkout as readonly for all
the users.
I am sure no specific restriction is applied on these files.
We dont know what is the reason for it. WE are unable to rectify it also.
Any one help us to rectify this problem.
How to remove the read-only restriction on these files.
Regards
Revathi

cvs watchers -R
I expect you will find someone has used the `cvs watch` command, I did not
think it was supposed to make things RO but it has for me in the past. My
solution for folks who wanted to watch files was to make a script that always
applied watches as `cvs watch add -a commit filename`, and have them use that.
or someone may have used `cvs edit` unnecessarily.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

[Todd Denniston]

Post by krevathi1912
But it doesn't help me. Still the files are checkout as read-only mode

I did not mean that the commands below would fix the issue, only that they
might help you and us be sure of what the issue is.

if it is watchers, then you need to first have anyone who _IS_ currently
"watching" a file to run `cvs watch remove` then you can start again, IIRC.

Post by krevathi1912

Post by Todd Denniston

Post by krevathi1912
Hi,
We have a CVS where a large no of codes are checked in all the days.
Today files in the ceratain directory alone is checkout as readonly for all
the users.
I am sure no specific restriction is applied on these files.
We dont know what is the reason for it. WE are unable to rectify it also.
Any one help us to rectify this problem.
How to remove the read-only restriction on these files.
Regards
Revathi

cvs watchers -R
I expect you will find someone has used the `cvs watch` command, I did not
think it was supposed to make things RO but it has for me in the past. My
solution for folks who wanted to watch files was to make a script that always
applied watches as `cvs watch add -a commit filename`, and have them use that.
or someone may have used `cvs edit` unnecessarily.

[tedtoal]

I've just spent an entire day trying to get my files so they won't check out
as read-only, and FINALLY fixed it. There seem to be many different paths
that could cause problems. There is the Edit Policy in TortoiseCVS
preferences; there is the WATCH setting in the repository (turn it off using
"cvs watch off"); there are the registered watchers (remove yourself using
"cvs watch remove"); there seems to be a bug in (my version of) CVSNT that
causes it to not change the contents of the fileattr.xml file even though
"cvs watch off" and "cvs watch remove" were done (but manually editing the
fileattr.xml file and removing the watch statements also does not fix the
problem); and then...

The final cause in my own case was that project files were individually
marked to "enforce reserved edit" within their ,v archive files, in the form
of the "x" option in the ,v file statement "kopt xkv". I was able to remove
the "x" from ALL the 'v files in the project with this command:

cvs update -k-x

Then, updating the project with new copies of files eliminated the
read-only.

[krevathi1912]

Hi,

We have a CVS where a large no of codes are checked in all the days.
Today files in the ceratain directory alone is checkout as readonly for all
the users.
I am sure no specific restriction is applied on these files.
We dont know what is the reason for it. WE are unable to rectify it also.
Any one help us to rectify this problem.
How to remove the read-only restriction on these files.



Regards
Revathi

[Arthur Barrett]

Please contact the TortoiseCVS team for questions/advice about
TortoiseCVS:
http://www.tortoisecvs.org/support.shtml

The mailing list is linked on the page above to:
http://sourceforge.net/mail/?group_id=48103

The info-cvs newsgroup is not really the place to discuss TortoiseCVS or
even to look for answers. In fact CVSNT is NoT CVS.

If you get involved in the correct group then you'll find that questions
you have are far more common and likely already answered in the FAQ or
in the mailing list archive and you wont feel so frustrated and on your
own:
http://www.tortoisecvs.org/faq.shtml#exclusive

Alternatively if you got TortoiseCVS installed via the CVS Suite 2009
(the new name for CVSNT) then it included comprehensive documentation on
Configuration Management theory and how to configure your server for
various models including reserved centralised, unreserved distributed
etc. If you are running the server on windows then the server
configuration wizard that runs after the install would lead you through
making the correct choices.

People who invest enormous time and money in creating these products
like TortoiseCVS, CVSNT and CVS Suite do not want to see people
struggling with getting SCCM running which is why they've made so many
facilities available to people like you. Please use them.

There is the Edit Policy in TortoiseCVS preferences; there
is the WATCH setting in the repository (turn it off using
"cvs watch off"); there are the registered watchers (remove
yourself using "cvs watch remove"); there seems to be a bug
in (my version of) CVSNT that causes it to not change the
contents of the fileattr.xml file even though "cvs watch
off" and "cvs watch remove" were done (but manually editing
the fileattr.xml file and removing the watch statements also
does not fix the problem); and then...

If there is a bug, please report it to the TortoiseCVS team.

Regards,



Arthur Barrett