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

git svn: how to recover from checksum mismatch?

From
Alexander Gladysh <agladysh@gmail.com>
Date
Jun 20, 2008, 10:56 UTC
Message-ID
<c6c947f60806200356s285ac4s7a4affc108c7f311@mail.gmail.com>
Hi, list!

Today I've upgraded to git 1.5.6 from 1.5.5.something (probably 1). When I've run git svn rebase on my repo, it complained about "checksum mismatch: trunk/path/myfile HASH".

BTW, Before that failing commit there were one more (successful) with some strange complains about whitespace errors:

    warning: CRLF will be replaced by LF in
/var/folders/8u/8uiW+GhrGka2OlIHiT1fsU+++TI/-Tmp-/hoizGwiM2P

I'm on OS X 10.5.3 and my repo is not in /var/folders tree (trailing part of path is different for each file).

The same errors are on my second copy of that repo (independent git repo made by the same git svn init as first).

When I run git svn init + git svn fetch on a fresh folder, it bails out with checksum error after a few first commits (on 20th commit actually) while giving the same odd CRLF warnings.

When I run git svn rebase on another machine (Ubuntu Hardy, git 1.5.5.1), it run smoothly without errors, so this, probably, is not an SVN repo corruption.

I have reverted back to git 1.5.5.1, but I still get that checksum error. I'm fetching a fresh git svn init+fetch from svn, but it takes a few hours, and I have to do it twice (for each of my two repos). Any advice on how can I recover less painlessly?

Thank you in advance, Alexander.

Next: Alexander Gladysh
Message 1 of 2 in “git svn: how to recover from checksum mismatch?”
  1. Alexander GladyshJun 20, 2008
  2. Alexander GladyshJun 20, 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.