I've got exactly the same exception from one of our old wc.
I'm not sure what's the reason for cleanup.
The wc was update-ed from 1.6 to 1.7
I did found some .svn directories deeper in the directory tree.
Maybe the update went wrong?
Can I help track this bug down?
I'm already using a fresh checkout so I'm going to have the wc around if
On 2012.01.12. 15:07, Andy Levy wrote:
> Please don't top-post.
> On Thu, Jan 12, 2012 at 09:02, Greg Townes<greg_townes_at_yahoo.com> wrote:
>> Hi Mark
>> Yes, I am asking how to solve this exception.
>> I required a cleanup to get my source code synched with the repository so
>> that I could do a Commit.
>> It should not matter why I needed the cleanup, exceptions should be handled
>> I upgraded from 1.7.1 to 1.7.3.
> It does matter why you needed the cleanup, because different reasons
> for the cleanup may trigger different conditions (and thus bugs) in
> the cleanup code.
>> From: "Cooke, Mark"<mark.cooke_at_siemens.com>
>> To: Greg Townes<greg_townes_at_yahoo.com>; "users_at_subversion.apache.org"
>> Sent: Thursday, 12 January 2012, 15:29
>> Subject: RE: Exception...line 673: assertion failed (checksum != NULL)
>>> Tried to do a cleanup on my folders and got this message.
>>> line 673: assertion failed (checksum != NULL)
>> Are you asking for help? In which case, what were you doing that required a
>> cleanup? Had you upgraded a pre-1.7 working copy by any chance?
>>> I think the last developer left hardcoded lines in the code
>>> as there is a reference to a "D" drive followed by the path
>>> of Development...
>>> I do not have that path on my pc.
>> FYI: That path is from the original source of your subversion client
>> (TortoiseSVN) and helps to identify where the error was trapped, it is
>> nothing to do with your code.
>>> Greg Townes
>> ~ mark c
Received on 2012-01-14 03:16:04 CET