[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.4.4 checksum mismatch error

From: Martin Hauner <Martin.Hauner_at_gmx.net>
Date: 2007-07-31 17:58:30 CEST

Hi,

Von: "David Glasser" <glasser@davidglasser.net>
> On 7/31/07, Martin Hauner <Martin.Hauner@gmx.net> wrote:
> [..]
> Martin, I can't reproduce this (svn 1.4.4 on OSX). I ran:

Interesting...

> svn co http://subcommander.tigris.org/svn/subcommander/trunk
> cd trunk
> svn merge http://subcommander.tigris.org/svn/subcommander/trunk@1840
> http://subcommander.tigris.org/svn/subcommander/branches/qt4@head .
>
> (Note to folks trying to reproduce: you can use the username/password
> guest/guest.)
>
> Two possibilities: Maybe the bug is win32-only? Or maybe there have
> been commits since you observed this problem (both the update and the
> @head in the merge depend on current trunk revision... can you
> reproduce it with explicit revisions in both places?).

I see the same error after replacing head with 1880 and i didn't touch
the repository after getting the error.

Since Mark says he can't reproduce it on windows it doesn't look like a
general windows error.

Strange is that the file in the .svn area has the expected checksum. The file in the wc has b9878da521fe53735e5df84baa22dbc6 (different to what
svn is complaining about). It also has a different size. As far as i can tell the only difference is eol style.

>
> --dave

-- 
Martin
Subcommander 2.0.0 Beta 1, http://subcommander.tigris.org
a cross platform Win32/Unix/MacOSX subversion gui client & diff/merge tool.
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 31 17:57:01 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.