I used the 0.11.0-alpha, and nightly-20070214 releases to convert one of our VSS databases, and it seems to have worked pretty well (I did run into the "Unrecognized File Error" with alpha 0.11.0, but a --debug run and deleting the zero length file fixed it up just fine).
The second database didn't convert. I ran with --debug and without and the error messages seem not to differ from the ones I saw with the successful convert. Just for giggles I deleted all the empty files in the second database, but the convert still failed. The last thing output by vss2svn was: TASK: IMPORTSVN then it just exited. The last thing written to the dumpfile.txt was: Revision-number: 45 Prop-content-length: 144 Content-length: 144 K 7 svn:log V 41 Entrie contents of borland 5.0.2 IDE CD. K 8 svn:date V 27 2000-12-05T14:17:08.000000Z K 10 svn:author V 8 Diethelm PROPS-END Node-path: tools/installs/devsuites/borland/borland-5-0-2.zip Node-kind: file Node-action: add Prop-content-length: 59 Text-content-length: 343179847 Any chance 343MB is too big for a single file/commit? I'm running the executable from a Cygwin bash script on a windows XP host using "nohup". I can provide (information from) the output log if that would help. The non debug version is about 22KB, the debug version is ~120MB. _______________________________________________ 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
