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

Re: SVN Migration from VSS

From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 15 Nov 2010 08:36:21 -0500

On Mon, Nov 15, 2010 at 7:28 AM, Neson Maxmelbin (RBEI/EMT5)
<Maxmelbin.Neson_at_in.bosch.com> wrote:
>
> I did a migrate of a project from VSS to SVN using the migrate.pl from
> http://neilsleightholm.blogspot.com/2007/08/migrating-from-visual-source-safe-to.html
> .
>
> Migration was ok . But I cant see the VSS labels been migrated?
> Is there a way to migrate the VSS labels also to some form in SVN?

Is there a "tags" directory? That's where labels are suppose to go.
Normally, conversion utilities have to be told where to put this
directory -- whether it should be at the root of the repository or the
root of the projects directory. The two most common ways are:

/trunk/proj1
/trunk/proj2
/branches/proj1
/branches/proj2
/tags/proj1
tags/proj2

/proj1/trunk
/proj1/tags
/proj1/branches
/proj2/trunk
/proj2/tags
/proj2/branches

Check both locations. Otherwise, you'll have to ask Neil Sleightholm
about his program. I don't know if too many people on this list are
familiar with it.

One of my concerns is that the migrate.pl program doesn't contain the
words "tags" or "branches" in it. I didn't do a code analysis to see
how it works, but unless you passed the names of your tags and
branches directory as parameters, I'd be concerned that tags and
branches weren't being created.

There was something about "Labeled" in the program. It appeared to be
a check in comment, but you can see if that exists as a directory
name, or check your "svn log" for a comment containing the word
"Labeled". If you do, do an svn log and see if you can find the actual
place the tag was created. It should be the revision right after the
"Labeled" comment.

If you can find the comments, but not the tags themselves, you might
be able to write a script to parse your SVN log, find the comments,
and make the tags yourself based upon the revision of those comments.

There are a few other VSS to SVN conversion utilities out there. The
one I'm most familar with are the tools from Polarion
<http://www.polarion.com/products/svn/svn_importer.php>. You might
want to try theirs and see if you get better results. There's also a
vss2svn project at http://www.pumacode.org/projects/vss2svn. Again,
take their utility for a spin and see what the results look like.

Again, your best choice for support on these VSS to SVN projects are
from the sites that offer these projects.

Please let us know what you find, so others who are in the same
situation can benefit from your knowledge. We're all volunteers here.
Most of us are on this list to get help, and some of us can
occasionally offer help in as a way of paying back the help we
previously had.

And, if you do use Subversion, I highly recommend keeping your
subscription on this list. It's a great way to learn about Subversion,
its problems, and the best ways to use it.

Sorry I couldn't be any more help.

-- 
David Weintraub
qazwart_at_gmail.com
Received on 2010-11-15 14:36:58 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.