From users-return-24219-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Mon Jan 4 10:30:24 2016 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1BBB21866E for ; Mon, 4 Jan 2016 10:30:24 +0000 (UTC) Received: (qmail 53270 invoked by uid 500); 4 Jan 2016 10:30:23 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 53227 invoked by uid 500); 4 Jan 2016 10:30:23 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 53216 invoked by uid 99); 4 Jan 2016 10:30:23 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 10:30:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 06145C7818 for ; Mon, 4 Jan 2016 10:30:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, HTML_OBFUSCATE_05_10=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id m1JZCFZ8flDY for ; Mon, 4 Jan 2016 10:30:15 +0000 (UTC) Received: from deepth.de (deepth.de [81.169.159.190]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 072D623028 for ; Mon, 4 Jan 2016 10:30:15 +0000 (UTC) Received: from b2b-130-180-18-42.unitymedia.biz ([130.180.18.42] helo=[192.168.3.120]) by deepth.de with esmtpa (Exim 4.72) (envelope-from ) id 1aG2Ot-0001gs-V6 for users@subversion.apache.org; Mon, 04 Jan 2016 11:30:08 +0100 Subject: Re: what's the cause of error 120108 and checksum mismatch To: users@subversion.apache.org References: <68dd3f6b.8cf9.151f6f67fee.Coremail.huang1987112@163.com> From: Stefan Hett Message-ID: <568A49AF.3070301@egosoft.com> Date: Mon, 4 Jan 2016 11:30:07 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <68dd3f6b.8cf9.151f6f67fee.Coremail.huang1987112@163.com> Content-Type: multipart/alternative; boundary="------------040407080802010408070902" This is a multi-part message in MIME format. --------------040407080802010408070902 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 --------------040407080802010408070902 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
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
--------------040407080802010408070902--