Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
We recently setup CVSNT version 2.5.02.2064on a Windows 2003 server here...though we've gone one troublesome issue. First, I must admit that I'm not very familiar with CVS so I apologize if I've missed something terribly obvious...I have searched the archives and googled for a solution, but haven't found what I need yet. Basic problem: once in a while, when commiting to the server, files will be written with either "permission 51;" or "permission 55;" in the .v file. When this happens, others can checkout the module but get a message during the process: "cvs checkout: cannot set time on xxxxxxxxxxxx.xxx: Permission denied". The files which generate the error are also checked out as read-only (whereas everything else is writable) and clicking on "edit" does not remove the read-only attribute. As a result, they need to go into the filesystem and unmark read-only before they can change and commit the files. It doesn't happen every time, I've modified a file myself a few times to test and it usually commits with "permission 666;". As a test, I modified the permission line for some of the .v files and changed "permission 55;" to "permission 666;" on the last commit and the file worked as we would like when checked out. Clients are using WinCVS 2.0.2.4, global option to commit as writeable is set. I don't believe that any watchers are set. Would really like it if everything was commited as "permission 666;" or that entry was ignored entirely... Any ideas would be appreciated...thanks for the help... Anil