Re: Problem with CollateSymbolsPass conversion from CSRCS to CVS to SVN

Michael Haggerty <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
On 10/06/2011 01:26 AM, lee wrote:
> Next I run the following command to determine what I can see in
> regards to the tags mentioned in the error, and see the following:
> 0     microphone/volume_adjust       tag        tags/microphone/volume_adjust .trunk.
>       # 'microphone/volume_adjust' is a tag in 9 files, a branch in 0 files, a trivial import in 0 files, a pure import in 0 files, and has commits in 0 files
> [...]
> 0     microphone                     tag        tags/microphone .trunk.
>       # 'microphone' is a tag in 7 files, a branch in 0 files, a trivial import in 0 files, a pure import in 0 files, and has commits in 0 files

There are two RCS/CVS tags, "microphone/volume_adjust" and "microphone".
 Since Subversion represents tags and paths in the same namespace, these
two tags will overlap when converted to Subversion.  For example, if
your project has a file "README.txt" in it, then in subversion you would
end up with the following nonsensical organization:

    $URL/tags/microphone/
    $URL/tags/microphone/README.txt
    $URL/tags/microphone/volume_adjust/
    $URL/tags/microphone/volume_adjust/README.txt

Do you see how the root directory of one tag is mixed up with the file
contents of the other tag?

You need to tell cvs2svn to put one of the tags elsewhere, which you can
do by editing the symbol-info file and using it as a symbol-hints file.
 For example, you could change the first line from above to read:

> 0 microphone/volume_adjust tag tags/microphone-volume_adjust .trunk.

(notice how I changed the "/" to a "-") then the conversion should be
able to proceed.

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2850418

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.