Stefan Sperling <stsp_at_elego.de> writes:
> On Thu, Oct 13, 2011 at 04:28:21PM +0200, Daniel Sparing wrote:
>> Dear fellow subversion users,
>>
>> as requested by the error message, i would like to report an error as
>> the following:
>>
>> ---8<---
>> In file
>> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\entries.c'
>> line 1935: assertion failed (svn_checksum_match(entry_md5_checksum,
>> found_md5_checksum))
>> ---8<---
>>
>> what i was doing: I updated my TortoiseSVN client to 1.7.0, then tried
>> to upgrade my two working copies to the new 1.7 format, one of them
>> succeeded, the other one repeatedly returns the error message above.
>>
>> daniel
>
> You had a broken 1.6 working copy which cannot be upgraded.
> See http://svn.haxx.se/tsvnusers/archive-2011-10/0086.shtml
>
> We've been getting this report a lot lately.
> Maybe it's time to add this to the FAQ?
>
> I also think we should change the assert into a proper error message.
In this particular case one of the checksum values in one of the
.svn/entries files doesn't match the checksum of the corresponding file
in .svn/text-base. The incorrect checksum won't show up as an error in
1.6 until an update or commit attempts to modify the corresponding file.
The 1.7 upgrade process checks all checksums so it will detect errors
that lie dormant in 1.6 working copies.
I agree we should be returning a better error, one that includes the
name of the file with the incorrect checksum.
--
Philip
Received on 2011-10-13 17:29:41 CEST