Greetings -
I am experiencing trouble with git svn, trying to import a
large repository (7.9 gigs, ~54000 commits) from Git into
SVN.
This has failed in a couple of different ways, depending
on the operating environment. With Git version 1.7.3.5
running on Ubuntu 9.10, in the final step
git svn dcommit --no-rebase
of the formula described below, I get:
failing with "Can't fork at /usr/share/perl/5.10.0/Git.pm line 1261."
after committing just over 2000 revisions.
Previously, on Mac OS X 10.6.4 with git version 1.7.3.4,
it made it through about 18000 commits before failing with
some other error. (I don't have that one recorded at the
moment.)
Separately from the latest attempt, I tried repacking the
repository before doing the "git svn" stuff, with
git repack -a -d --depth=250 --window=250 -f
but that also failed ("pack-objects died of signal 11").
Any tips for dealing with new, large, repositories would
be appreciated. The sequence of commands I used are below
the 8<.
Thanks,
Joe
8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<-8<
## Creating an svn repo
$ mkdir repo;
$ svnadmin create repo;
$ mkdir init;
$ touch init/README;
$ svn import init file://`pwd`/repo/init -m "Initial import";
$ svn checkout file://`pwd`/repo/init working;
## THIS PART FOLLOWS THE MODEL SUGGESTED BY THE FOLKS AT code.google.com
## (/Users/jac2349/planetary/destination/ IS THE LOCATION OF MY GIT REPO.)
$ mkdir cloning
$ cd cloning
$ git svn clone file:///Users/jac2349/planetary/repo/init
$ cd init
$ git fetch git:///Users/jac2349/planetary/destination/.git
$ git branch tmp $(cut -b-40 .git/FETCH_HEAD)
$ git tag -a -m "Last fetch" last tmp
$ INIT_COMMIT=$(git log tmp --pretty=format:%H | tail -1)
$ git checkout $INIT_COMMIT .
$ git commit -C $INIT_COMMIT
$ git rebase master tmp
$ git branch -M tmp master
$ git svn dcommit --no-rebase
$ mv .git/refs/tags/newlast .git/refs/tags/last
## BTW, THE --no-rebase FLAG KEEPS IT FROM BEING IMPOSSIBLY SLOW!
--
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