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.
Glenn, I can tell you now that the problem doesn't seem to be tortoise. I've been able to reproduce the bug using the CVSNT command line in two different versions (2.0.34 and 2.0.38). I also uninstalled TCVS 1.6.10 and then installed TCVS 1.6.7 and the problem still appears. And now I realized that the problem is just with a specific module from a specific repository. Other modules from the same repository and from other repositories don't seem to have the problem (all the repositories are in the same server). I've already reported the bug in the CVSNT Bug Tracker. I also have tried changing the TEMP directory(and the TEMP Env variable) and it didn't work. The problem doesn't appear always,though. Sometimes (like 1 out of 10 times) UPDATE works OK. This is really the most weird bug I've ever seen. I'm starting to believe the problem is in the server(it runs CVSNT 2.0.12a) I really appreciate your help. Regards, Carlos -----Mensaje original----- De: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]En nombre de Glen Starrett Enviado el: martes, 04 de mayo de 2004 15:39 Para: Carlos Méndez CC: Tortoisecvs-Users at Lists. Sourceforge. Net; 'Cvsnt at Cvsnt. Org' Asunto: Re: [cvsnt] Help! Problem with update Carlos Méndez wrote: >Yeah, this seems to be the problem. The actual path (in my PC) is >C:\WINDOWS\TEMP\. Now I know that TortoiseCVS creates some directories with >the name "cvs-serv"+ SOME_NUMBER in the TEMP directory. > >You mention that the latest Tortoise fixed the bug. I use the latest STABLE >version (1.6.10) so maybe you wanted to say the opposite, that the bug was >introduced in the latest version? I didn't have that kind of problem in >previous versions of Tortoise. Do you know a way to solve this problem or >I'll have to wait until this bug is fixed? > > You misunderstood me--there was a problem that Tortoise wasn't passing the set temp path information to CVSNT before, so people weren't able to set their TEMP path to something that made sense to them. I believe that it was that fix from the previous version that may have broken your setup. If you didn't have appropriate permissions set up, or a bad temp path, then it would cause this to appear. Check those out if you can: Make sure the c:\windows\temp path exists and you have full permissions to it, change your TEMP environment variable if necessary, etc. -- Glen Starrett _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs