git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode

From
BČBranko Čibej <brane@wandisco.com>
Date
Jul 6, 2013, 00:34 UTC
Message-ID
<51D7660F.6070901@wandisco.com>
In-Reply-To
<kr7il5$n0p$1@ger.gmane.org>

[Copying dev@ because it's related to a known issue that we document more loudly.]

On 06.07.2013 00:51, David Rothenberger wrote:
Show 17 quoted lines
> I cannot reproduce this problem using command-line tools, but I was
> able to do a trace of git-svn when it is failing and it looks to me
> that the problem is in the order in which the SVN::Delta::Editor
> (svn_delta_editor_t) function are being called.
>
> The order I see is:
>  1. open_root
>  2. open_directory
>  3. add_file
>  4. apply_textdelta
>  5. add_file
>  6. apply_textdelta
>
> The git-svn code is expecting a close_file call before the add_file
> call in #5. It appears to me that the svn_delta_editor_t API [1]
> requires this close_file call. It looks to me like this is Issue
> #2932 [2].
Indeed it is.
And it is actually documented here:
https://svn.apache.org/repos/asf/subversion/trunk/notes/api-errata/1.7/ra001.txt
and mentioned here:

http://subversion.apache.org/docs/release-notes/1.7.html#svnrdump In other words, this is a limitation of the Serf-based backend that has been around since Subversion 1.4. I'm aware that it isn't documented as well as it should be, but the bulk-mode workaround exists in part as a workaround for that, effectively disabling the more efficient HTTPv2 protocol.

In the meantime, it might be a good idea to relax the restrictions in git-svn to account for the way the HTTPv2 protocol works.

-- Brane
-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com
Next: Daniel Shahaf
Message 1 of 5 in “Re: git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode”
  1. Branko ČibejJul 6, 2013
  2. Daniel ShahafJul 6, 2013
  3. Daniel ShahafJul 6, 2013
  4. Branko ČibejJul 6, 2013
  5. Bert HuijbenJul 6, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.