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 email@example.com.
Siegfried Heintze wrote: > I'm sure I'm using the recent cvsnt client. I tried it again, this time > (using cmd.exe instead of bash) I'm trying to save my changes in the > repository. What does this error mean: "Up-to-date check failed"? That means that the server thinks there is a more recent version of the file available, as if someone else had committed that file after you had checked it out. > > This is in reponse to creating a new sandbox, modifying a file with the > editor and commiting it. That is an appropriate sequence, is it not? Yes, that's appropriate. Normally, when you get the up-to-date check error, you have to do an update to merge in the latest changes to that file. However, with the sequence you describe, that shouldn't happen (unless there is someone else with very good timing updating that file). What version of server are you using? You can check with "cvs version" in a sandbox (not the lack of a -). What happens when you do a "cvs up" just before the commit? > Thanks,\ > Siegfried > > C:\Program Files\Apache Group\Apache2\htdocs\CaseAssessment>"c:\Program > Files\cv > snt\cvs.exe" commit Assertion.f > cvs server: Up-to-date check failed for `Assertion.f' > cvs [server aborted]: correct above errors first! > cvs commit: saving log message in > C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cvs25.tmp > > C:\Program Files\Apache Group\Apache2\htdocs\CaseAssessment> > -- Glen Starrett