Hello List, Thanks for your comments, replies below...
> There's no such thing as "normal" in VSS :) Every archive is > screwed up in its own unique way depending on usage patterns, > length of use, moon phases etc. I would highly recommend > that, before you run "analyze", you make a backup of the > existing repo first. We've seen cases where running analyze > makes it even more difficult to migrate rather than less. > > In general my advice would be to convert the existing repo > as-is, and then "fix" it using available Subversion tools > (svndumpfilter etc.), rather than try to fix it first and > then convert. > Thanks Toby, I made a copy of the repo files locally and run the tools against that, both quicker and safer than running against the network version. At the moment we are still evaluating subversion against another (expensive) tool used elsewhere in the company, so I can hone skills now before (hopefully) doing a final conversion sometime. > Are you running against the latest nightly? Or 11.1? > > Bryan > Thanks Bryan => I used vss2svn-0.11.0-alpha1.zip ~ I do not have perl installed (more of a python person) so went with the pre-built option. I am open to persuasion that it is worth the effort going for the nightly build (although I notice the last night seems to have been a while ago). > Some info on fixing orphans (rather than completely removing them) is at > http://www.pumacode.org/projects/vss2svn/wiki/FixingTheDumpfile#Orphaned Files > > -Nathan > Thanks Nathan, I did find this page, however I am not familiar with the contents of the archives as yet (one of the attractions of vss2svn was the lack of a VSS license!) as I only started here a few weeks ago. I tried archive/restore of an individual project out of the main large archive and ended up with everything under 'orphaned' so I am now mainly following the advice in: http://www.pumacode.org/projects/vss2svn/wiki/RunningTheMigration > I strongly recommend you to get all files from VSS database, all files > from resulting SVN database and compare it. The result will show you > whether you lose files (as 'orphaned' or not). If you frequently use > history, also check it for your most common projects - have you loose > it or not. > > Also check this mail list for fixes - there are some patches available > here but not in 'official' dist or repository. > > Best regards, > Dmitry > I have recently acquired a VSS license so am starting this process but as I said, I am new to the source so it is a slow process! I will trawl the back archives but patches mean I will need to install Perl and they are fussy about what you install here... With Thanks, ~ Mark C _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
