[ comments inline]
> When using the beta2 conversion tools, I was able to create a
> dumpfile; however, the dumpfile has several problems when loading.
>
> The first failure was:
> ======================================
> <<< Started new transaction, based on original revision 5
> * adding path : IDEFiles ...COPIED... done.
> svnadmin: The root directory cannot be deleted
> * deleting path : ...
> ======================================
Did you actually delete the root path in VSS? Is that even possible? I
can add a check for that and ignore those in the script.
It doesn't appear as thought the root path was really deleted. When
looking at the VSS history of $/, the following happened:
Created
$FirstProject Added
$WholeIDE Added
$FirstProject Destroyed
$IDEFiles Renamed $WholeIDE to $IDEFiles
Then, when looking at the generated datacache.VssAction.tmp.txt, the
actions are recorded as listed below, which looks a bit off to me as
just "/" is named when possibly the project name should be listed:
----------------------------------------------------------------
0 AAAAAAAA 1 ADD / 1 0 \N
1 BAAAAAAA \N ADD /FirstProject/ 1 0 \N
2 FAAAAAAA 1 ADD /WholeIDE/ 1 0 \N
3 GAAAAAAA \N ADD /WholeIDE/forsafe.cpp 2 0
\N
4 HAAAAAAA \N ADD /WholeIDE/forsafe.ide 2 0
\N
5 AAAAAAAA 4 DELETE // 1 0 \N
6 AAAAAAAA 5 RENAME / 1 0 IDEFiles/
------------------------------------------------------------------------------
> Then, the next error occurs:
>
> ======================================
> <<< Started new transaction, based on original revision 4099
> svnadmin: File not found: transaction '4098-1', path
> 'Installation/system/SBE6_32.DLL'
> * deleting path : Installation/system/SBE6_32.DLL ...
> ======================================
>
> What is the best course of action? Should I just keep parsing the
> dumpfile to get around these errors?
Somehow these non-existent deletions are making it past the sanity
checker. I wonder if it's related to the other errors you're getting.
I'll have to play around with deleting the root directory and see if the
checker is handling that properly.
Yes, it sounds like you should just keep parsing the dumpfile for now...
"svndumpfilter" (included with Subversion) will help you here; type
"svndumpfilter help exclude" for info on how to remove certain paths
from your dumpfile altogether. Please let us know if there are other
types of errors encountered. We are trying to account for all the
different types of VSS corruption out there but obviously we're not
quite there yet.
I tried using the svndumpfilter for quite awhile before giving up.
Sooner or later, I would always get the "Invalid copy source path".
I'll keep trying though...
http://svn.haxx.se/users/archive-2005-08/0748.shtml
Thank you,
-Jon
_______________________________________________
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
