It's me again, I have some additional information regarding the problem, maybe this helps:
> -----Ursprüngliche Nachricht----- > Von: Brockamp, Peter > Gesendet: Montag, 17. Oktober 2011 17:49 > An: 'users@subversion.apache.org' > Betreff: Supposed serious(?) bug in either subversion or > TortoiseSVN when upgrading to latest V1.7.0 version - I checked and had to realize that the described problem appeared in more than one of my projects. So this seems *not* to be a sporadic problem but rather often! - After the test with trying to revert one of those files I ended up with a broken local SVN-state, any attempt to "Clean Up..." the problem project yields the very same assertion: --------------------------- Subversion Exception! --------------------------- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list (users@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 Datei »D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c«, Zeile 672: Assert-Anweisung schlug fehl (checksum != NULL) --------------------------- OK --------------------------- -> Thus things obviously got severely and permanetly wrong with this directory! - I tried to do a "Clean Up..." on one of the other projects with broken file states. This gave me an alleged successful clean up, but afterwards still showed files as locally modified and empty in the repository. - By way of trial I locally erased one of these broken-state-files in my projects and tried an update. This again gives me the assertion above, leaving the second directory in an corrupted state. So, as I see it now, this is in fact a *serious* problem at least with TortoiseSVN 1.7.0 working against an 1.6 SVN-server! So actually I must severly warn about using this configuration in a production environment, it will potentially cause you problems! Regards Peter Brockamp
