--- Stephen Lee <[EMAIL PROTECTED]> wrote: > Jewgenij Moldawski wrote: > > > > Dear friends, > > > > I'm now testing the vss2svn (as .exe program, not > .pl) and migrating a > > very small (some MBs) VSS test-repository, Version > 6.0. > > > > The vss2svn reports first "Warning: Unknown Action > RestoreProject". > > After the migration and after I loaded the dump > file into Subversion, > > I see, that all but entire VSS-content is now > under /orphaned in > > Subversion. > > > > You probably created your test repository by > exporting a project and > importing this into a test database... vss2svn > doesn't work very well > like that - you're better off with a SourceSafe > database that doesn't > have archive/restore actions in its history. If > necessary due to large > database size, destroy all except the project you > want to test with on a > backup of the database and to a test conversion on > that. > > Also the Alpha that looks like its the one you want > is very old and very > fragile, and doesn't cope well with any > "complicated" actions on files > or projects. Many of the "nightly" builds are much > more stable and > reliable in my experience, particularly for > SourceSafe databases that > have had anything other than a trivial version > history.
Just as a second to what this chap replied with - I have just finished (well 2months ago) migrating several repositories with chequered histories at best.. and all quite large.. I got the best sucess when i did the following. Keep running VSS analysis until it complains no more. Sometimes you have to delete files of 0 bytes to obtain this. Purge all deleted files from the VSS repository. Run the migrate on the latest nightly (which is quite old) it is much better at histories and generally. Create your SVN repos.. and attempt an import. In my experience it kept falling over on the import back in. My cut and burn solution to this was to delete delete the file that caused the problem IN SOURCE SAFE. I also found that if 1 file in a dir complained it was likely several would - save yourself some time. if non of the histories to these files are import purge the directory containing them.. Repeat until you can migrate, and import without error. Then you overlay VSS with SVN by checking out the head of each and copying the VSS over the SVN stuff. The files that are identical will change nothing. new or changed files can be committed here. also - learn from my mistake and consider any file properties you might use.. like SVN needs lock and apply it NOW.. here.. use the python script called something like svn_auto_prop.py. Then update everyone's tortoise file (if that is what your using) to match these settings for new files. I can furnish you with a comprehensive one if you so care. Hope this helps. ----------------------- N: Jon Hardcastle E: [EMAIL PROTECTED] 'The writing is on the wall...' ----------------------- _______________________________________________ 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
