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

Re: "Checksum mismatch" when performing update

From: Matt Doran <matt.doran_at_papercut.biz>
Date: 2005-05-11 12:47:16 CEST

John Szakmeister wrote:

>On Wednesday 11 May 2005 04:37, Matt Doran wrote:
>>Hi there,
>>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
>>shown below.
>> $ svn --version -q
>> 1.1.4
>> $ svn up
>> svn: Checksum mismatch for 'providers.sln'; expected:
>> '9cb298b2150e77340280d646c50d244a', actual:
>> '6590988692d8eb0e8ed5514b5821cd79'
>> $ md5sum providers.sln
>> 8f21805e9b084c2ce6cbbb52f325272e providers.sln
>> $ md5sum .svn/text-base/providers.sln.svn-base
>> 8f21805e9b084c2ce6cbbb52f325272e
>>* 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
>different md5sums!
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)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Wed May 11 12:51:31 2005

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

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