git-svn checksum mismatch

git-svn checksum mismatch

[Jason Baker]

On Wed, Feb 17, 2010 at 6:53 PM, Eric Wong <normalperson@yhbt.net> wrote:
>
> Jason Baker <jbaker@zeomega.com> wrote:
> > Hey Eric,
> >
> > I'm emailing you because you're listed on the git-svn manpage.  I'm trying
> > to import an svn repository using git svn, and I'm running into a bit of a
> > problem:
> >
> > r57269 = f5bbaec2f7e8d866d794b421f68706baf81b16ec
> > (jiva_model_0.6-Jiva-4.5.0)
> >     M    src/jiva_model/schema/episode.py
> >     M    src/jiva_model/schema/group.py
> > Checksum mismatch: src/jiva_model/schema/member.py
> > expected: d6f1b614f3ec9c757ab21ebdfd01e011
> >     got: a90dbcbdb3082deadecca9d1d00879bd
> >
> > I'm running git version 1.6.3.3 and git-svn version 1.6.3.3-2 on Ubuntu
> > Karmic.
> >
> > I'm able to check out these files at this revision normally through svn.
> > Does this mean that there's a problem somewhere in git svn?  Or do I need to
> > do something more complex to reproduce it outside of git svn?  It is
> > entirely possible that something's wrong with our svn repository.
>
> Hi Jason,
>
> It could be a problem with either the repo or git svn.  Is the repo
> public by any chance?  If it's a smallish repo I'd be glad to try
> reproducing it on my end.

Nope, it's a private repo and it's rather largeish.

>
> The checksum SVN relies on is just an MD5, so it should be easy to
> test arbitrary revisions of it (svn cat -r$rev $URL@$rev | md5sum)
> and see if there's an error for that repository.

This gives me something different from either value.  :-/

$ svn cat -r57269
$URL/jiva_model_0.6-Jiva-4.5.0/src/jiva_model/schema/member.py@57269 |
md5sum
b5a6b9473d602027b1fe9b5b9d993cc0  -

 (URL being the path to the root of the repo of course)

>
> You could also try updating between two revisions:
>
>  svn co -r57269 $URL FOO # (57269 was the last successful one)
>
>  cd FOO
>  svn up -r$NEXT_REV      # see if this errors out

This works:

$ svn co $URL/branches/jiva_model_0.6-Jiva-4.5.0/src/jiva_model/schema/
-r 57269
Checked out revision 57269.

$ cd schema

$ svn up -r 57270
At revision 57270.

So does this mean there's a problem on my side somewhere?

>
> > Also, is there a mailing list I should send questions like this to?
>
> The normal git mailing list, git@vger.kernel.org, but feel free to Cc me
> to increase my chances of seeing it.

Added that list to this email.  Thanks!

Re: git-svn checksum mismatch

[Eric Wong]

Jason Baker <jbaker@zeomega.com> wrote:
> This works:
> 
> $ svn co $URL/branches/jiva_model_0.6-Jiva-4.5.0/src/jiva_model/schema/ -r
> 57269
> Checked out revision 57269.
> 
> $ cd schema
> 
> $ svn up -r 57270
> At revision 57270.
> 
> So does this mean there's a problem on my side somewhere?

Did r57270 change anything at all in the directories you're tracking?
You might need to step the revision up to the next one you're
tracking...

Not sure what else could be the cause...  Did you run out of disk space
or encounter any hardware failures at any time during the fetches?

-- 
Eric Wong

git-svn checksum mismatch

[Reynald Borer]

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

Re: git-svn checksum mismatch

[Reynald Borer]

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

Re: git-svn checksum mismatch

[Patrick Doyle]

On Wed, Dec 8, 2010 at 10:17 AM, Reynald Borer <reynald.borer@gmail.com> wrote:
> 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?

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

Re: git-svn checksum mismatch

[Reynald Borer]

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:
> On Wed, Dec 8, 2010 at 10:17 AM, Reynald Borer <reynald.borer@gmail.com> wrote:
>> 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?
>
> 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
>