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.
In the following scenario 'cvs update' (with cvsnt) won't create a file although it should: Create a file "a.txt" and import it into a new module. Checkout the module into a new working copy. Tag the repository as "RevA". Create an additional file "b.txt" and add it to the module. Now checkout the module, Revision "RevA" into another working copy. Finally do "cvs update -d -r 1.1 b.txt" within the working copy. cvsnt with a local repository or with a cvsnt server (with pserver authentication) won't create the file "b.txt", although it should (IMHO). cvsnt client with a cvs (1.11.6) server over extssh creates the file "b.txt" Tested configurations: cvsnt client only (local repository): 2.5.03.2151 cvsnt client/server: client 2.5.03.2151, server 2.5.01.1976 cvsnt client, cvs server: client 2.5.03.2151, server 1.11.6 (works) Some background information: I'm using tailor (http://www.darcs.net/DarcsWiki/Tailor) to read out every single version of the files within a cvs repository. To achieve this tailor checks out the first revision from the repository and afterwards updates the files one by one to the next revision. This process works fine if the repository is on some Linux-machine with cvs 1.11.xx, but it fails with cvsnt. Regards, Thomas Klaeger