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 Tony, There are some ugly messages from the server (cvsnt.org): Actually I have tag CVSNT_2_0_x in my sandbox and I want to get the .58a >>>> cvs -z9 -q update -P -d -r CVSNT_2_0_58sp (in directory K:\cvs\cvs_nt\cvsnt\) ? cryptlib ..... ? zlib/win32/Release cvs update: Read data failed (5): error:00000000:lib(0):func(0):reason(0) cvs [update aborted]: reading from server: error -1 <<<< Next time I try the same line all works well! (only a rename conflict with "test_new.txt", looks like cross branch rename doesn't work) Afterwards I switched back to CVSNT_2_0_x. That works like expected. When I now do a simple update I sometimes get another warning message: >>>> cvs -z9 -q update -P -d (in directory K:\cvs\cvs_nt\cvsnt\) cvs server: warning: is not (any longer) pertinent M cvsnt.vcproj <<<< So what is any longer perinent??? Both messages can sometimes be reprotuced and sometimes not (I se a 50:50 chance). cvs version Client: Concurrent Versions System (CVSNT) 2.0.58a (client/server) Server: Concurrent Versions System (CVSNT) 2.0.58a (client/server) Client build from the latest sources (just a few minits ago). Both can be reproduced on win32 and solaris. And another thing: When I do an explicite update to a branch already present in my sandbox I get also the rename/conflict error: >>>> cvs -z9 -q update -P -d -r CVSNT_2_0_x (in directory /export/home/rich/osdev/cvsnt_2/cvsnt/) ? autom4te.cache ? solaris_patches.txt ? contrib/xxyyzz ? cvsagent/win32/ChangeLog ? doc/cvs.tar.gz ? doc/version.inc ? src/server.c.mod ? src/xx_hardlink.h cvs server: test_new.txt has been renamed to cvs update: unable to rename ./test_new.txt: No such file or directory cvs update: move away ./test_new.txt; it is in the way C test_new.txt .... <<<< But the version of test_new.txt is already sticky tag CVSNT_2_0_x. -- Best regards, Richard mailto:r.wirth at wirthware.de