On Wed, Oct 12, 2011 at 1:20 AM, Tommi Prami <groups.tprami_at_gmail.com>wrote:
> ---------------------------
> Subversion Exception!
> ---------------------------
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> (users_at_subversion.apache.org)
> 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.0\ext\subversion\subversion\libsvn_wc\entries.c'
> line 1935: assertion failed (svn_checksum_match(entry_md5_checksum,
> found_md5_checksum))
> ---------------------------
> OK
> ---------------------------
>
This *is* the wrong list... But I also had that exception when upgraging my
working copy. It turned out that I had some sub-trees that were in a broken
state as far as the .svn metadata. The release notes say that you *really*
need to do an svn cleanup (with a *1.6* client) on every working copy before
it's upgraded. My experience was that I svn cleanup wasn't enough - that
there were sub-trees in a wierd state that I had to fix by continuing to do
updates (to show which sub-trees were broken enough to not be updatable).
Once I could complete an update without any errors, then an svn cleanup,
then the working copy could be upgraded cleanly. YMMV.
<>< <>< <><
Bryce Schober
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2853954
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-12 17:36:22 CEST