[cvsnt] Vendor branch bug in CVSNT 2.0.9?

[Jussi Lahdenniemi]

Hello!

I upgraded cvsnt from 2.0.3 to 2.0.9. After that, I ended up in a weird 
situation when using vendor branches. I was able to reduce the bug (?) into 
this:

G:\dist>dir
16.09.2003  14:14               5  file1.txt

G:\dist>cvs import -m "" test test-dist v1
N test/file1.txt

No conflicts created by this import

G:\>cvs co test
cvs checkout: Updating test
U test/file1.txt

All fine. Now, add a file and import another vendor revision.

G:\dist>dir
16.09.2003  14:16              10  file1.txt
16.09.2003  14:16               5  file2.txt

G:\dist>cvs import -m "" test test-dist v2
U test/file1.txt
N test/file2.txt

No conflicts created by this import

G:\test>cvs up
cvs update: Updating .
U file1.txt
U file2.txt

Good this far. But,

G:\test>cvs up -r test-dist
cvs update: Updating .
cvs update: file2.txt is no longer in the repository

G:\test>cvs up -r v2
cvs update: Updating .

That is, the new file (file2.txt) seems to have ended correctly in the 
vendor branch, but it does not show up when updating with either the vendor 
branch tag or with the second import's tag. This works on 2.0.3 and also 
works when the server is 2.0.3 and client is 2.0.9 (even when the import 
was made with a 2.0.9 server).

I worked around by temporarily downgrading to 2.0.3.


- Jussi Lahdenniemi