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.
On Mon, 19 Mar 2007 09:57:36 +0100, "Aleksander Pahor" <Aleksander.Pahor at hermes-softlab.com> wrote: > >Hi Bo! > >Yes. It's CVSNT. I use TortoiseCVS as client. Version 1.8.25. Tortoise, yes, but what about the client version of cvsnt that tortoise uses???? > >CVSROOT=:sspi:srvcvs01:/cvs_root > >cvsdiag output: >CVSNT Diagnostic output >----------------------- >Server version: 2.5.03 (Scorpio) Build 2151 ... snip ... > >Before I had 184.108.40.2067. Could well be one of the versions that sometimes corrupted binary files. >Those files are newer than then the old server (added under the new 220.127.116.111 ). What exactly do you mean here? Which files are "newer" than which? >I tested - and those files get corrupted everytime I add them to the repo. They get corrupted if you cvs add them to your repository using the server build 2151???? What version do you use on the client side? Corruption may also be caused by an erroneous varsion on the client because client and server do co-operate in mysterious ways, I found. And don't give the Tortoise version, it does not say anything. What you should do is check the version of cvsnt that tortoise is using. >Actually the repo (,v) file looks OK. But checkout/update produces empty file with exact size. Looks like all the files that get corrupted have some kind of "right content" which bollocks cvsnt. >Do I need to upgrade the server to 18.104.22.1682? I didn't see any topic around about 22.214.171.1241 corrupting binary files... I have run 2151 for quite some time without problems like this. But I am now using 2382 and 2260 on two servers that definitely work OK. HTH /Bo (Bo Berglund, developer in Sweden)