On Jul 5, 2013, at 16:07, David Rothenberger wrote:
On 7/5/2013 3:58 PM, Kyle McKay wrote:
On Jul 5, 2013, at 13:48, David Rothenberger wrote:
I recently upgraded my Subversion server to 1.8.0 and started
receiving the following error from "git svn fetch":

Temp file with moniker 'svn_delta' already in use at
/usr/lib/perl5/vendor_perl/5.10/Git.pm line 1024.

This occurs only when using an http:// URL; svn:// URLs work fine.
The client is Cygwin: svn version 1.8.0 and git version

The subversion 1.8 release has removed the neon library, all svn client
http access now always goes through the serf library.  If you put
"http-library = serf" in the "[global]" section of the
"~/.subversion/servers" file you will get the 'svn_delta' error with
git-svn when running earlier versions of the svn client as well.

That was not my experience. I did try this with the 1.7 perl bindings
and libraries and with "http-library = serf" in by servers and it worked
fine. I confirmed that serf was being used with a Wireshark trace.

I had it always fail right away from my home ISP (kinda slow connection), but when running on a host with quite a different internet connection it would sometimes run for a while before generating the error (maybe a couple hundred revisions fetched) for some sources, but it would *always* eventually fail.

For this reason I also believe the problem is timing sensitive.

Try doing "git svn clone --quiet http://dev.heuristiclab.com/svn/hl/ core" with "~/.subversion/servers" section "[global]" including "http_library = serf". I find this one always seems to fail right away for me with git-svn over serf but will clone fine over neon (if you can stand to wait long enough).

I have been looking into using serf for git-svn clones ever since I discovered how very much faster snvrdump works on an http url over serf as compared to neon.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to