You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Ng, Alan" <an...@dcs.wisc.edu> on 2012/01/27 21:18:34 UTC

TortoiseSVN crash report (cleanup failed)

As far as I can tell, the repository on this machine (which generated the 
error message copied below) got confused at some point in the past about 
upper/lowercase on one filename. My SourceForge repository has the filename 
all in lowercase, whereas this Windows machine had the corresponding file in 
uppercase. My attempts on this machine to synchronize or update the local 
repository with the SF repository failed. When I then manually deleted the 
Window file and attempted to synchronize or update, then SVN asks me to run 
cleanup first. Clean up attempts (involving the folder which had the offending 
uppercase file) then fail with this message:

---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
 'D:\Development\SVN\Releases\TortoiseSVN-1.7.4\ext\subversion\subversion\libsvn_wc\workqueue.c' line 673: assertion failed (checksum != NULL)---------------------------OK---------------------------

RE: TortoiseSVN crash report (cleanup failed)

Posted by "Ng, Alan" <an...@dcs.wisc.edu>.
Additional information: I discovered that the root of the problem was that
at some point in the past (months ago) the SourceForge repository got *both*
a lowercase and an uppercase version of the same filename. On Macs, svn
brought down only the uppercase file. On Windows XP, TortoiseSVN brought
down only the lowercase file. Presumably commits from both machines over
time got everything all mucked up.

This does suggest that some improvement could be made in SVN regarding
committing filenames differing only in case from what's already in the
repository.

> -----Original Message-----
> From: Ng, Alan
> Sent: Friday, January 27, 2012 2:19 PM
> To: 'users@subversion.apache.org'
> Subject: TortoiseSVN crash report (cleanup failed)
> 
> As far as I can tell, the repository on this machine (which generated the
> error message copied below) got confused at some point in the past about
> upper/lowercase on one filename. My SourceForge repository has the
filename
> all in lowercase, whereas this Windows machine had the corresponding file
in
> uppercase. My attempts on this machine to synchronize or update the local
> repository with the SF repository failed. When I then manually deleted the
> Window file and attempted to synchronize or update, then SVN asks me to
run
> cleanup first. Clean up attempts (involving the folder which had the
offending
> uppercase file) then fail with this message:
> 
> ---------------------------
> Subversion Exception!
> ---------------------------
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
> you were trying to do.
> But please first search the mailing list archives for the error message
> to avoid reporting the same problem repeatedly.
> You can find the mailing list archives at
> http://subversion.apache.org/mailing-lists.html
> 
> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C):
> 
> In file
>  'D:\Development\SVN\Releases\TortoiseSVN-
> 1.7.4\ext\subversion\subversion\libsvn_wc\workqueue.c' line 673: assertion
> failed (checksum !=
NULL)---------------------------OK---------------------------