git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Blair Zajac <blair@orcaware.com>
To: git@vger.kernel.org
Subject: serf causing "temp file with moniker 'svn_delta' already in use"?
Date: Mon, 16 Nov 2009 13:55:23 -0800	[thread overview]
Message-ID: <4B01CA4B.7040103@orcaware.com> (raw)

I've seen some reports of the following error using git svn and encountered it 
myself with git 1.6.5.2 with Subversion 1.6.5:

Temp file with moniker 'svn_delta' already in use at 
/opt/local/lib/perl5/site_perl/5.8.9/Git.pm line 1022.

In Googling around I seen other people discussing the issue but with no real 
root cause.

I'm guessing that it may be due to an API violation of the Subversion RA editors 
when Serf is used:

http://subversion.tigris.org/issues/show_bug.cgi?id=2932
http://n2.nabble.com/git-svn-fails-to-fetch-repository-td2151475.html

I can generate the above error on demand with Serf but if I switch to Neon then 
everything works fine.  People may be using Serf because they compiled 
Subversion with Serf and without Neon or instructed Subversion to use Serf 
instead by this setting in their ~/.subversion/servers:

[global]
http-library = serf

I haven't looked at this issue beyond being able to reproduce it with Serf and 
without Neon, but hope this gives some direction to the issue.

This bug may get fixed in Subversion as we want to move to Serf as the default 
HTTP client away from Neon and this is one of the outstanding issues before 
making that switch.

Regards,
Blair

                 reply	other threads:[~2009-11-16 22:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=4B01CA4B.7040103@orcaware.com \
    --to=blair@orcaware.com \
    --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.
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 NNTP newsgroup(s).