Matt Doran wrote:
> John Szakmeister wrote:
>>On Wednesday 11 May 2005 04:37, Matt Doran wrote:
>>>Today I encountered a strange problem when trying to update a working
>>>copy. I'm running Debian Sarge, running svn 1.1.4, the server is
>>>hosted on the same machine and is accessed using mod_dav_svn over
>>>After working in windows for a while, I went back to my linux working
>>>copy and tried to "svn update", and received a "Checksum mismatch", as
>>> $ svn --version -q
>>> $ svn up
>>> svn: Checksum mismatch for 'providers.sln'; expected:
>>> '9cb298b2150e77340280d646c50d244a', actual:
>>> $ md5sum providers.sln
>>> 8f21805e9b084c2ce6cbbb52f325272e providers.sln
>>> $ md5sum .svn/text-base/providers.sln.svn-base
>>>* There were no local modification in this working copy.
>>>* Doing "svn up <subdir>" works fine
>>>* Doing a fresh checkout works fine.
>>>Any ideas? Anything I should try?
>>>(I can easily recreate this working copy .... just wondering if there
>>>is an issue lurking in there somewhere....)
>>Can you send a copy of your entries file as well (.svn/entries)? It's
>>strange to get this error in the first place (it usually means that you
>>somehow corrupted file in the .svn area). But it's more strange to see 3
> Attached are two entries files (one from the broken working copy, and
> one from a checkout of HEAD)
> (can you CC me, as I'm not subscribed to the list)
It's not your text-base. This is definitely pointing to some sort of
network error as Sussman suggested. Do you have a proxy in your path
that might be munging the data?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 11 14:35:28 2005