cvs importer woes
- From
Andreas Ericsson <ae@op5.se>
- Date
- Jun 27, 2006, 10:05 UTC
- Message-ID
- <44A102F0.9090604@op5.se>
Sadly, the cvsimport command no longer works to create new repositories from scratch. I'm not nearly perl literate enough to fix it, but the problem seems to be firstly 061303f0b50a648db8e0af23791fc56181f6bf93. In particular "Also, make sure that the initial git-read-tree is performed." which fails if there is not a complete git repo already created with at least one tree committed.
Some sample output:
$ git cvsimport -k -u -d:local:/home/CVS packages fatal: Not a git repository: '/data/home/exon/git/packages/.git' read-tree failed: 32768
Removing the unconditional read-tree call, I get this (still in an empty directory which isn't a repo):
$ git cvsimport -k -u -d:local:/home/CVS packages fatal: Not a git repository: '/data/home/exon/git/packages/.git' read-tree failed: 32768
$ git init-db defaulting to local storage area
$ git cvsimport -k -u -d:local:/home/CVS packages fatal: Not a valid object name origin read-tree failed: 32768
Bisect running now. v1.3.1 is good and imports the stuff properly to an empty directory.
Oh, now it's done (4 minutes for 620 revisions with automated testing between good/bad. *LOVE* bisect).
The culprit is definitely 061303f0b50a648db8e0af23791fc56181f6bf93.
Any perl-literate takers? Otherwise, just reverting the patch makes things work (for me) again.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231