Re: git-svn checksum mismatch

Hi again,

Sorry to bother you again but I am still experiencing this problem. I tried with a more up to date version of Git (version 1.7.3.2), and this is still happening. I also tried to diagnose this issue but I am completely lost.

I am very annoyed because this is preventing me using Git on all my SVN repos (2 are failing on 30...)

Does anyone know how I could try to solve this issue?

Thanks very much in advance.

Regards, Reynald

---------- Forwarded message ----------
From: Reynald Borer <reynald.borer@gmail.com>
Date: Wed, Dec 8, 2010 at 3:28 PM
Subject: git-svn checksum mismatch
To: git@vger.kernel.org

Hello all,

I'm using git with a subversion repository and am experiencing the well known checksum mismatch problem when I try to fetch from our repository:

r5289 = f110f54fc3a488639e8b645438c4538e7785228f (refs/remotes/trunk)
Checksum mismatch:
app/tnin/model/src/main/resources/etc/sql/migration_scripts/STX-12229.sql
expected: c70c72fe170781e3279c37d0de637a55
    got: f90d31e1fd8e0f88569f87eb087c06c9

I have already been trying to diagnose this issue and have found nothing to fix it so far. I have tried to do a checkout with an svn client of the revision 5289, the previous one and then do an update, everything works fine when doing so.

The only thing I see that may cause this issue is that the file has special svn property (eol-style=native).

I am using git version version 1.7.2.3 (using svn 1.6.13).

Thanks in advance for your help, Reynald Borer

On Wed, Dec 8, 2010 at 10:17 AM, Reynald Borer <reynald.borer@gmail.com> wrote:

Tossing out a random theory with nothing to back it up...

I don't know anything about the "well known checksum mismatch problem", but are you trying to check out the SVN repository onto a file system that is case insensitive, such as on a Windows or (default setup) Mac host?

If so, the repository might have files with different spellings such as README and Readme in the same directory, which will get clobbered on such a host. I've run into that issue in the past in a different context.

--wpd

Hello Patrick,

Thanks for your quick answer. I'm doing a checkout on a Linux box, so there is no problem with the case of files. Thanks for the tip anyway.

Apparently it seems that SVN commits causing issues are the ones where the svn property "eol-style" has been changed to native (because the repositories are shared between Windows and Linux clients). I tried to reproduce this in a clean repository but I did not succeed at exhibiting the problem.

Cheers, Reynald

On Wed, Dec 8, 2010 at 4:36 PM, Patrick Doyle <wpdster@gmail.com> wrote: