AW: Subversion exception! (common_util.c line 211)
From: Hahn Reinhard <Reinhard.Hahn_at_regiodata-gmbh.de>
Date: Wed, 26 Feb 2014 08:31:02 +0100
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:bert_at_qqmail.nl]
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.Hahn_at_regiodata-gmbh.de]
Hello list,
today the same exception occurred with TortoiseSVN version 1.8.5
Here the complete version information:
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
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 reported the following
In Datei
More Informations:
Client OS: Windows 7
Access to repository via svn protocol
SVN-Server: svn, Version 1.6.12 (r955767)
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
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.