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

Re: No Commit/Checkout. Both Errors.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-11-02 12:26:05 CET

Anthony wrote:
> I am getting a strange issue...
> I tried to commit on a directory with some folders which have files that
> changed. Nothing too out of the ordinary, meaning normal size/type of
> files. I have commited/updated/checkout on this directory in the past
> with no problem. Now when committing, I seem to constantly get the
> message:
> Error: Commit failed (details follow):
> Error: Checksum mismatch while reading representation:
> Error: expected: b91aac274943c0d278ad6c82c5c98453
> Error: actual: 2e5c63f7dc9e65695410ade1f4e92b7c
>
> I tried running cleanup/update and again, I get same message. I then
> tried checkout new copy and I can't seem to do this either as I get the
> following error:
> Error: REPORT request failed on '/svn/REPONAME/!svn/vcc/default'
> Error: REPORT of '/svn/REPONAME/!svn/vcc/default': Could not read chunk
> delimiter: Secure connection truncated (https://www.SVNSITE.com)
>
> I am able to commit in other directories of the same REPO.
>
> Any idea why this happens and how to solve?

Your repository most likely got corrupted. Run 'svnadmin recover' on the
repository.
You should ask such server based questions on the subversion mailing
list (users at subversion tigris org).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Nov 2 12:26:35 2007

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

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