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.
Hello Tobias, Thursday, September 8, 2005, 2:38:01 PM, you wrote: TR> Hello, TR> in the last days we quite often encounter the problem that the HEAD TR> version of the file and the version that was checked in last is not TR> the same. I.e. each of the following TR> - cvs update -A TR> - cvs update -r HEAD TR> - just cvs update on a checked out copy without sticky tag TR> does not deliver the latest version of the file but the version before TR> that, even when the local copy of the file was identical to the latest TR> version before hand. TR> Example (the most extreme case): TR> 1) I have a copy of version 1.26 (which is the latest version) in my TR> working directory. TR> 2) I modify the file. TR> 3) I commit the file. TR> 4) I do "cvs update" TR> 5) My file is reverted to version 1.26, although "cvs log" shows me TR> that my commit was successfull and version 1.27 exists. TR> I can get version 1.27 with "cvs update -r 1.27" or, if i placed a tag TR> "TAG" as step 4.5, by "cvs update -r TAG", but update to HEAD always TR> reverts it to 1.26. in rare cases I observed the same on my Solaris server with 2.0.58d. Switching to a newer version solved the problem (2.5.01 Build 1990). There are also some issues in enumerating the sandbox directory structure when this version of client is used against a 2.5.01 Server. So I had to upgrade the client side also. -- Best regards, Richard mailto:richard at wirthware.de