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.
On Tue, 01 Feb 2005 11:53:46 -0700, Dick Jackson <dick at d-jackson.com> wrote: >cvs login >Logging in to :pserver:djackson@<myCVSserver>:2401:/jnj > >***** CVS exited normally with code 0 ***** This means that you have given the local workstation enough info to log on automatically whenever needed to djackson@<myCVSserver>:/jnj But whenever needed is the key here.... > >Looks good, but when I do anything else with my files... > >===== >cvs -n update -P add_colorbar.pro (in directory C:\JJ\toolkit\) >cvs server: connect to 127.0.0.1(127.0.0.1):2402 failed: No connection could be >made because the target machine actively refused it. > >***** CVS exited normally with code 1 ***** The cvs update command does not use anything else but what was stored in the CVS metadata folders upon checkout! Your problem is that you have an erroneous root stored in the CVS metadata. In WinCvs do as follows: 1) Select the top folderin your sandbox in the left pane 2) Go to Macros/CVS/CHANGEROOT 3) Click OK on the first dialogue 4) Enter the root changes you want to apply 5) OK Now the update will use the root you entered and if that is a correct working repository with the modules you have then all will be OK. > >Even if I do this, the same thing happens: > >===== >cvs -n -d :pserver:djackson:<password>@<myCVSserver>:2401:/jnj update -P >add_colorbar.pro cvs update has *never* used the -d parameter, it *always* uses what is stored in the CVS folder. >As I mentioned, I've tried uninstalling and throwing away all settings files in >C:\Program Files\GNU\WinCVS 1.3. I've even fumbled around with regedt32, but >found nothing that looked right. Messing with the client program will not help in fixing a problem in the sandbox. The setup does not touch data at all.... /Bo (Bo Berglund, developer in Sweden)