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 firstname.lastname@example.org.
Bo Berglund wrote: > On Sat, 3 May 2008 10:50:49 -0400, "Gordon Boast" > <gordon.boast at ieee.org> wrote: >>I am using cvsnt version 2.5.03 (Scorpio) Build 2382 with TortoiseCVS >>version 1.10.6. In February I switched from the :local: protocol to the >>:sspi: protocol. This was done on recommendation on this mail list to solve >>a problem I was having at the time.... >> >>Since making this change, I have noticed that when I check out a sandbox >>(not done too often) some files in each directory are checked out as >>read-only (shown with a locked icon). Such files cannot be changed and >>committed unless I first clear the read-only property with windows explorer >>)icon changes to normal check-mark). I have been working this way, >>successfully, since February. >> >>Today I have a situation were after making the above change to a file, I am >>still unable to complete the commit. The following error message is posted: >> >> In C:\Documents and >>Settings\TSi\Desktop\TradeStationIndicators\PackageELDs: "C:\Program >> Files\CVSNT\cvs.exe" commit -m "copy out from EXPORT folder" >>TurnSignal_Complete(7.0).ELD >> CVSROOT=:sspi:gordodesk1:C:/CVSRepositories >> >> cvs server: user 'TSi' is not a valid editor of the file >>'TurnSignal_Complete(7.0).ELD' >> cvs [server aborted]: correct above errors first! >> >> Error, CVS operation failed >> >>Does anyone know how to correct this error? > > It is *not* an error..... > Someone has changed te readonly property of the file in his sandbox by > issuing the cvs edit command. THis makes the file read/write in his > sandbox. But it also tells CVSNT that this user is the owner of the > edit token on the file and that noone else may commit any changes to > the file until he is done and has committed his own changes. > > So you need to find out who has done this and tell him to commit or > unedit the file. I think this, while it does happen, is not what happened here. It seems that .ELD are binary and this file has been added with -kbx options. It therefore requires a valid editor before committing. You edited it by clearing the read-only flag, not by issuing the command "cvs edit". Now CVSNT requests that you be an "editor" of the file; that is, that you have issued a "cvs edit" command before committing. The purpose of this is to prevent two people working at the same time on a not mergeable file. To fix your problem, just issue a "cvs edit" command on the file, and you can commit it. And then, either start using "cvs edit" for binary files (if more than one person are using the repo), or don't add binary files with the -kx option (-kb or -kB is enough). Gerhard