subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Hett <ste...@egosoft.com>
Subject Re: what's the cause of error 120108 and checksum mismatch
Date Mon, 04 Jan 2016 10:30:07 GMT
On 12/31/2015 8:35 AM, 黄章梁 wrote:
>
> Developers of subversion:
>
>          Hello!
>
>          I encountered two problems.
>
>          Question 1: When update the work-copy failed atfter that 
> update some files success , and tips:
>
>                            ‍svn: E120108: Unable to connect to a 
> repository at URL 'https://…. '‍
>
>                            ‍svn: E120108: Error running context: The 
> server unexpectedly closed the connection. ‍
>
>                    What’s the cause of this promble? Network error?
>
That would be one possibility. But honestly, your question sounds like 
you want us to guess what particular problem is rather than what kind of 
causes could cause such an error. That we certainly can't, since there 
is a multitude of possible explanations. Network error being just one of 
that.
>
>           Question 2: When update the work-copy, tips:
>
>                            ‍Error: Checksum mismatch while updating 
> 'D:\xx\xx.h':‍
>
>                             ‍Error:    expected: 
> e14ae03a45fcfb4d754531bb5b38d1fe ‍
>
>                             ‍Error:      actual: 
> d67898a0aae70499c71819a747b18a0a ‍
>
>                             ‍Error: Try a 'Cleanup'. If that doesn't 
> work you need to do a fresh checkout.‍
>
>                    “Cleanup” is not effective,  how to solve the 
> problem except as do a fresh checkout?
>
Did you try out the google resources already? For instance: 
http://stackoverflow.com/questions/10352934/svn-checksum-mismatch-while-updating
>
>                    And what is the cause or operation leads to this 
> problem?
>
Same situation as the question 1. Sorry, but I left my crystal ball at 
home. One possible explanation for that would be disk corruption. 
Whether that was the cause in ur case or whether there was some other 
underlying issue, I can't tell of cause.

-- 
Regards,
Stefan Hett


Mime
View raw message