[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

mks2cvs + cvs2svn selects wrong file versions in tags

From: Mats Nilsson <mats.nilsson_at_xware.se>
Date: 2003-08-29 16:16:52 CEST

Hi

I converted a MKS SI repository of ours to CVS using a tool called
mks2cvs.pl floating around the internet.
The repository contains an active main branch, and three active branches
off the main branch at various places. Multiple tags on each branch.

When running cvs2svn on this converted repository I notice that at least
one tag refers to the wrong version of a file, namely 1.15.1.2 instead
of 1.16.

Another thing that strikes me as odd is that /trunk received versions
1.15, 1.16, 1.15.1.2 of this file in that order (consistent with the
chronological order of these versions). Therefore, HEAD has the file
corresponding to 1.15.1.2, which is not what I'd expect.

Hmm. Now, this leads me to think that mks2cvs didn't manage to correctly
create branches according to the equivalent MKS construct (variant). I
guess it only created tags, not branch tags.

Well. Nevertheless, the ,v file contains explicit symbol definitions
like this:

head 1.16;
Access ;
symbols
        ..
        ..
        REL_4_2_1:1.16
        REL_4_1_8:1.15.1.2
        REL_4_2_0:1.16
        ..
        ..

And in spite this, svn directory 'tags/REL_4_2_1' contains the file at
version 1.15.1.2. (The other tags have the correct corresponding
version)

I guess I'm wondering if this is likely an effect of
missing/incompatible branch symbols in the cvs ,v file.

Thanks

Mats

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 29 16:17:19 2003

This is an archived mail posted to the Subversion Users mailing list.