From: Jason Baker <jbaker@zeomega.com>
To: git@vger.kernel.org
Subject: git-svn checksum mismatch
Date: Thu, 18 Feb 2010 08:55:30 -0600 [thread overview]
Message-ID: <fa34f1941002180655n79430e79yc8658ce17e4e1093@mail.gmail.com> (raw)
In-Reply-To: <fa34f1941002180652wb91c36bt8feba5c7f653701d@mail.gmail.com>
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!
next parent reply other threads:[~2010-02-18 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa34f1941002170821p66cf0ac7i9385b341c94993c3@mail.gmail.com>
[not found] ` <20100218005347.GA8528@dcvr.yhbt.net>
[not found] ` <fa34f1941002180652wb91c36bt8feba5c7f653701d@mail.gmail.com>
2010-02-18 14:55 ` Jason Baker [this message]
2010-02-18 23:08 ` git-svn checksum mismatch Eric Wong
2010-11-04 13:45 Reynald Borer
[not found] <AANLkTik0NBkjrPTzLp9ozMnnV+bng_u5Br1v+H4y6ed0@mail.gmail.com>
2010-12-08 15:17 ` Reynald Borer
2010-12-08 15:36 ` Patrick Doyle
2010-12-08 16:13 ` Reynald Borer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa34f1941002180655n79430e79yc8658ce17e4e1093@mail.gmail.com \
--to=jbaker@zeomega.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).