Just verified the issue is present on trunk as well (r1587745):
subversion/libsvn_wc/wc_db_update_move.c:2493:
(apr_err=SVN_ERR_ASSERTION_FAIL)
svn: E235000: In file 'subversion/libsvn_wc/wc_db_update_move.c' line 2493:
assertion failed (move_src_op_root_relpath != NULL && move_dst_op_root_relpa
Hi Subversion developers,
Encountered the following assertion while trying to resolve a tree conflict:
svn: E235000: In file 'subversion/libsvn_wc/wc_db_update_move.c' line 2462:
assertion failed (move_src_op_root_relpath != NULL && move_dst_op_root_relpath
!= NULL)
./svn-bug.sh: line 33: 30387
On Mon, Apr 14, 2014 at 1:47 PM, Ben Reser wrote:
> On 4/12/14, 3:41 PM, Nico Kadel-Garcia wrote:
>> For our own safety and benefito of combined HTTP/HTTPS servers for
>> Subversion worldwide: is there a published test to verify that HTTP
>> servers do not have the same flaw due to also being conf
Hi Murali,I am also getting the similar svnsync error but tricky one.svnsync:
E22: Revision being currently copied (32529), last merged revision
(32527), and destination HEAD (32527) are inconsistent; have you committed
to the destination without using svnsync?Please note I have two slave
repos
hi,
i was wondering, what is the best possibility to use ldap groups for
authorizing access to svn on repositories itself, as well as on directory
level. authentication is done via ssh as described in the documentation, no
need to do this via ldap.
i saw:
http://svnbook.red-bean.com/en/1.7/svn
