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 1BCDD98CC for ; Wed, 4 Apr 2012 02:20:47 +0000 (UTC) Received: (qmail 45697 invoked by uid 500); 4 Apr 2012 02:20:46 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 45682 invoked by uid 500); 4 Apr 2012 02:20:46 -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 Delivered-To: moderator for users@subversion.apache.org Received: (qmail 71649 invoked by uid 99); 3 Apr 2012 21:50:48 -0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jklida@amadeusconsulting.com designates 74.92.208.181 as permitted sender) X-ASG-Debug-ID: 1333489820-04712d0e091283e0001-bBppbA X-Barracuda-Envelope-From: jklida@amadeusconsulting.com X-ASG-Whitelist: Client From: Joseph Klida X-Barracuda-Apparent-Source-IP: ::1 To: "users@subversion.apache.org" Subject: Checksum Kind Mismatch Thread-Topic: Checksum Kind Mismatch X-ASG-Orig-Subj: Checksum Kind Mismatch Thread-Index: Ac0R4o10H9/5PNCbRniBvsWoWbu7Dw== Date: Tue, 3 Apr 2012 21:50:28 +0000 Message-ID: <173BB3BEA08B6843978B6E8D0E2EF146C4F06E47@acg-prod-xch.wolfgang.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.99.251.47] Content-Type: multipart/alternative; boundary="_000_173BB3BEA08B6843978B6E8D0E2EF146C4F06E47acgprodxchwolfg_" MIME-Version: 1.0 X-Barracuda-Connect: exchange.wolfgang.com[10.99.133.9] X-Barracuda-Start-Time: 1333489820 X-Barracuda-URL: http://spam.wolfgang.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at wolfgang.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_173BB3BEA08B6843978B6E8D0E2EF146C4F06E47acgprodxchwolfg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am seeing a problem where I am trying to commit a file change to Subversi= on 1.7.4 over HTTP (via Apache) and am getting the following error: Transmitting file data .svn: E235000: In file 'D:\Development\SVN\Releases\= TortoiseSVN-1.7.6\ext\subversion\subversion\libsvn_wc\wc_db_pristine.c' lin= e 482: assertion failed ((*md5_checksum)->kind =3D=3D svn_checksum_md5) Using SmartSVN, I get a similar error that provides a little more info: Commit failed (details follow): Checksum mismatch for 'C:\Projects\...'; ex= pected '$sha1$...', actual: '$md5$...' Why would svn not be able to determine the correct checksum alg to use? All machines involved are Windows (7 SP1 and 2008R2 SP1). Server is using V= isualSVN Server (Apache based). Would it be possible that VisualSVN-Apache = are always assuming MD5? Would this a bug in svn? TortoiseSVN? VisualSVN Server? FYI, I am NOT on the mailing-list, so please CC me. Thanks -joe --_000_173BB3BEA08B6843978B6E8D0E2EF146C4F06E47acgprodxchwolfg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am seeing a problem where I am trying to commit a = file change to Subversion 1.7.4 over HTTP (via Apache) and am getting the f= ollowing error:

 

Transmitting file data .svn: E235000: In file 'D:\De= velopment\SVN\Releases\TortoiseSVN-1.7.6\ext\subversion\subversion\libsvn_w= c\wc_db_pristine.c' line 482: assertion failed ((*md5_checksum)->kind = =3D=3D svn_checksum_md5)

 

Using SmartSVN, I get a similar error that provides = a little more info:

Commit failed (details follow): Checksum mismatch fo= r ‘C:\Projects\...’; expected ‘$sha1= $...’, actual: ‘$md5$...’=

 

Why would svn not be able to determine the correct c= hecksum alg to use?

 

All machines involved are Windows (7 SP1 and 2008R2 = SP1). Server is using VisualSVN Server (Apache based). Would it be possible= that VisualSVN-Apache are always assuming MD5?

 

Would this a bug in svn? TortoiseSVN? VisualSVN Serv= er?

 

FYI, I am NOT on the mailing-list, so please CC me.<= o:p>

 

Thanks

-joe

--_000_173BB3BEA08B6843978B6E8D0E2EF146C4F06E47acgprodxchwolfg_--