git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kyle McKay <mackyle@gmail.com>
To: David Rothenberger <daveroth@acm.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode
Date: Fri, 5 Jul 2013 18:01:27 -0700	[thread overview]
Message-ID: <5675CCAE-F4E8-48B7-8B63-BE91AAE09DD5@gmail.com> (raw)
In-Reply-To: <51D75196.4030100@acm.org>

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.
>> [snip]
>>> The client is Cygwin: svn version 1.8.0 and git version
>>> 1.8.3.2.
>>
>> 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.

Kyle

  reply	other threads:[~2013-07-06  1:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 20:48 git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode David Rothenberger
2013-07-05 22:58 ` Kyle McKay
2013-07-05 23:07   ` David Rothenberger
2013-07-06  1:01     ` Kyle McKay [this message]
2013-07-06  2:02       ` David Rothenberger
2013-07-05 23:14 ` David Rothenberger
2013-07-06  3:41   ` Kyle McKay
     [not found] <kr6uvc$p8a$1@ger.gmane.org>
     [not found] ` <51D7072A.6080909@wandisco.com>
     [not found]   ` <kr75h0$qg5$1@ger.gmane.org>
     [not found]     ` <51D7362B.1040803@wandisco.com>
     [not found]       ` <kr7il5$n0p$1@ger.gmane.org>
2013-07-06  0:34         ` Branko Čibej
2013-07-06  2:04           ` Daniel Shahaf
2013-07-06  2:15             ` Daniel Shahaf
2013-07-06  4:23           ` Branko Čibej
2013-07-06  7:30           ` Bert Huijben

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5675CCAE-F4E8-48B7-8B63-BE91AAE09DD5@gmail.com \
    --to=mackyle@gmail.com \
    --cc=daveroth@acm.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).