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.
Hi Everybody,
I was trying to use import with multiple vendor tags as described in CVS
Cederqvist manual (13.6) and I encountered a strange bug that assigns the
release tags incorrectly to a (wrong) branch instead of a revision. My "cvs
version" returns
Client: Concurrent Versions System (CVSNT) 2.0.4 (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.4 (client/server)
Both server and client installed on Win2K.
To reproduce the bug:
1) create an empty folder with one non-empty text file test.txt
2) execute "cvs -d:sspi:cvshost:\cvs import modulename branch1 initial1"
3) execute "cvs -d:sspi:cvshost:\cvs import -b 1.1.3 modulename branch2
initial2"
4) execute "cvs -d:sspi:cvshost:\cvs checkout modulename"
5) move to the modulename folder and execute "cvs status -v". The output is:
File: test.txt Status: Up-to-date
Working revision: 1.1.1.1
Repository revision: 1.1.1.1 /cvs/modulename/test.txt,v
Expansion option: (default)
Commit Identifier: (node)
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
Merge From: (none)
Existing Tags:
initial2 (branch: 1.1.1) <<<< BUG HERE!
branch2 (branch: 1.1.3)
initial1 (revision: 1.1.1.1)
branch1 (branch: 1.1.1)
The "initial2" tag should point to *revision* 1.1.3.1 and not to *branch*
1.1.1.
Alberto Barbati