On 9/4/06, Jens Seidel <jensseidel@users.sf.net> wrote:
> Hi,
>
> I just want to inform you that my reproducable checksum mismatch error is still
> available in 1.4.0 (Release Candidate 5). I failed to reproduce it on a small
> code base, also because of errors in svndumpfilter (#1853) which prevents that
> I just try it with the affected files only.
>
> Nevertheless I'm sure you want to fix it in 1.4.0 and a developer can maybe
> easily imagine what's going on.
>
> On Thu, Aug 03, 2006 at 10:38:30PM +0200, Jens Seidel wrote:
> > On Thu, Aug 03, 2006 at 02:31:49PM -0400, Garrett Rooney wrote:
> > > On 8/3/06, Jens Seidel <jensseidel@users.sf.net> wrote:
>
> Again: I performed a big merge and after this did a "svn up". I got:
>
> > > >The last update results now in
> > > >svn: Checksum mismatch for 'dir/.svn/text-base/file.cc.svn-base';
> > > >expected: 'bc0c5b04db8bb787c25b95a61e372452', actual:
> > > >'d46738f6464df5a5ec690101b85664bc'
> > > >
>
> The following is essential to understand this problem:
> $ svn status dir/file.cc
> R + dir/file.cc
>
> The file dir/file.cc is replaced and the checksum of the wrong file is probably
> used for comparison.
I doubt that. But it's a bug (in the client), yes.
Though I have 1 question: given that the file is locally replaced,
what do you expect to happen to any updates you receive for the -now
deleted- file? (Because I think you're receiving updates for that file
in your scenario)
bye,
Erik.
PS: Could you describe *exactly* what your merge does, then what your
update is supposed to do, what you expect subversion to do and what
you're actually observing? (I already saw what you're observing, but
not what you expect update to do: which files should be updated, which
ones left alone, any ones removed or added?).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 4 16:47:09 2006