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

Re: git svn bug?

From
Deskin Miller <deskinm@umich.edu>
Date
Oct 2, 2008, 14:59 UTC
Message-ID
<86d4c5e00810020759n6f64f0acx575a1dede5d7aba8@mail.gmail.com>
In-Reply-To
<20081002144916.GA3644@atjola.homenet>
On Thu, Oct 2, 2008 at 10:49 AM, Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
Show 16 quoted lines
> On 2008.10.02 16:50:45 +0800, Ark Xu wrote:
>>   Now I got a tough problem which stopping me for any svn related
>> operations. There is a file log4j.xml that is somehow strange because
>> when I fetch it, i got the following message:
>>
>> tms-service/src/test/resources/log4j.xml has mode 120000 but is not a
>> link at /opt/local/bin/git-svn line 3230.
>> M     tms-service/src/test/resources/log4j.xml
>>
>>   And then, all the operation will lead to :
>> Checksum mismatch: branches/5.3/tms-service/src/test/resources/log4j.xml
>> 51031cbb0e1a2e878e4a3836cf0baa9b80a037a5
>> expected: fab6daef9fc355b9342e26047f5d0141
>>      got: 0e7e9081d608c80d2de0340ba5cd1600
>
> Which git version? And is your /tmp large enough to store that file?

I've had issues similar to this when I did Ctrl+C during git svn fetch. Prior to the issue you've pointed out popping up, though, I could compare the repo against another git svn fetch which was not interrupted, and the commits would diverge at some point. When I looked into the commit which diverged, the commit object was present in my interrupted repo, but the diff was empty, while it was non-empty in the other repo.

It seems there's an issue with git svn fetch atomically fetching and updating its refs. I've not had time to investigate further, but I certainly want to.

In the meantime, I worked around it on initial fetch from a big svn repository by using git svn fetch -r1:n , and increasing n in increments, so it could run to completion without me interrupting it.

This was seen using git 1.5.4.3 from Ubuntu.
Deskin Miller
Previous: Björn Steinbrink
Message 3 of 3 in “git svn bug?”
  1. Ark XuOct 2, 2008
  2. Björn SteinbrinkOct 2, 2008
  3. Deskin MillerOct 2, 2008

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.