Re: git svn clone terminating prematurely (I think)

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jan 11, 2012, 22:48 UTC
Message-ID: <20120111224833.GA29654@burratino>
In-Reply-To: <CALkWK0nyc6NVE7Qpvbc0dXb1UHGM_=uYbCS+a53HZxiBRG9HvQ@mail.gmail.com>

Ramkumar Ramachandra wrote:

> Interesting.  From the git-svn-id of the most recent commit, can you
> tell if there's anything especially fishy about the revision where
> git-svn stops?  Your Subversion repository is probably broken in some
> way,

I wouldn't necessarily assume that. My first hunch would have been that this is some variation on the SIGPIPE bug[1]. The usual workaround for that[2] is to get git-svn to continue by running "git svn fetch" again. Nobody's fixed it because nobody's stared at the SVN perl bindings for long enough to find the cause.

Modern git versions produce a message in that case, though:

	error: git-svn died of signal 13

So you are probably running into something else. I only mention this for context.

Does svnsync work for making a local copy of whatever subset of the repository is relevant? Alternatively (this is basically the same), is the network connection stable enough for e.g. svnrdump[3] to get a dump?

Sorry for the trouble, and hope that helps, Jonathan

[1] http://thread.gmane.org/gmane.comp.version-control.git/134936/focus=134940 [2] Maybe it deserves a note in the manpage. [3] http://repo.or.cz/w/svnrdump.git