Hi Bert, > I'm guessing that you tried to commit a delete somewhere in a directory that > you just copied and didn't commit yet.
Yes it is very, very likely that something like that was part of what I've tried to commit > I'm nominating the fix for this issue for 1.8.9. Thank you, Reinhard Von: Bert Huijben [mailto:b...@qqmail.nl] Gesendet: Dienstag, 25. Februar 2014 20:40 An: Hahn Reinhard; users@subversion.apache.org Betreff: RE: Subversion exception! (common_util.c line 211) Hi, I'm guessing that you tried to commit a delete somewhere in a directory that you just copied and didn't commit yet. In this specific case I finally found a reproduction for this specific assertion, which requires a few more conditions. (See http://svn.apache.org/viewvc/subversion/trunk/subversion/tests/cmdline/commit_tests.py?r1=1571747&r2=1571746&pathrev=1571747 if you want to look at the details). I'm nominating the fix for this issue for 1.8.9. Bert From: Hahn Reinhard [mailto:reinhard.h...@regiodata-gmbh.de] Sent: dinsdag 25 februari 2014 14:15 To: users@subversion.apache.org<mailto:users@subversion.apache.org> Subject: AW: Subversion exception! (common_util.c line 211) Hello list, today the same exception occurred with TortoiseSVN version 1.8.5 Here the complete version information: * TortoiseSVN 1.8.5, Build 25224 - 64 Bit , 2014/02/18 20:05:11 * Subversion 1.8.8, -release * apr 1.5.0 * apr-util 1.5.3 * serf 1.3.4 * OpenSSL 1.0.1f 6 Jan 2014 * zlib 1.2.8 Perhaps the situation was more complicated, with many moves and renames, maybe even the same element moved/renamed twice. Cleanup and update didn't help. My workaround was doing several commits, each one committing only a part of the changes. I presume it is difficult to reproduce the situation. If it happens, that I can reproduce it, I'd try to add a "HOWTO REPEAT" to this mail thread. Thanks Reinhard Von: Hahn Reinhard Gesendet: Dienstag, 11. Februar 2014 12:36 An: 'users@subversion.apache.org' Betreff: Subversion exception! (common_util.c line 211) Hello list, I'm not subscribed in the list, but like to be cc:ed in any responses to this mail. Today I've got the following subversion exception: 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 Datei »D:\Development\SVN\Releases\TortoiseSVN-1.8.4\ext\subversion\subversion\libsvn_client\commit_util.c«, Zeile 211: Assert-Anweisung schlug fehl (repos_root_url && repos_relpath) ----------------------------------------------------------------- OK More Informations: Client OS: Windows 7 SVN-Client: TortoiseSVN-1.8.4 Access to repository via svn protocol SVN-Server: svn, Version 1.6.12 (r955767) Server-OS: Linux 2.6.32-5-686-bigmem #1 SMP Mon Feb 25 01:53:47 UTC 2013 i686 GNU/Linux What I've tried: - Do a commit - Then a warning popped up (which was not surprised due to what I wanted to commit): Non-recursive commit of moved/renamed folders. This commit is not recursive, and there are moved/renamed/copied folders selected for commit. Such moves/renames are always performed recursively in the repository. Do you want to commit anyway? I've selected: Proceed with the commit The renamed/moved folders are committed recursively in the repository. - After that, the a.m. exception occurred Then I tried again after a cleanup --> the same behaviour as described above Then I tried again after a cleanup & update --> committed successfully Thanks Reinhard
