On Tue, 20 Jan 2009, Kelly F. Hickel wrote: > Hello all, > > Back in June I had done a test convert of our CVS repo using git 1.5.5.1 > and cvs2svn 2.2.0 that went reasonably well (although it takes nearly a > week to finish!). Recently I wanted to try again with the latest > versions of git and cvs2svn. > > When I get to the final stage (running git fast-import to build the > converted repo), I get the following output: > cat ../cvs2svn-tmp/git-blob.dat ../cvs2svn-tmp/git-dump.dat | git > fast-import > fatal: Unsupported command: '. > fast-import: dumping crash report to .git/fast_import_crash_19097 > > The crash is 18MB and I'd rather not post it, but the only bits that > seem somewhat interesting are: > fast-import crash report: > fast-import process: 19097 > parent process : 19095 > at Mon Jan 19 11:44:42 2009 > > fatal: Unsupported command: '. > > Most Recent Commands Before Crash > --------------------------------- > (...) > reset refs/tags/T_9772 > from :1000007127 > reset refs/heads/TAG.FIXUP > > commit refs/heads/TAG.FIXUP > mark :1000007128 > committer cvs2svn <cvs2svn> 1002043747 +0000 > data 88 > * '. > > > Has anyone got any ideas how to resolve this? Can you find that part of the input? I wouldn't be too surprised if something were giving the wrong length in a data command, causing it to either eat another data command and end up in the data or to use not-quite-all of the data and end up near the end of the data. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
