Re: "Unable to parse reversed revision range" when merging from trunk to branch

2017-07-03 Thread Daniel Shahaf
Jens Restemeier wrote on Mon, 03 Jul 2017 20:01 +0100: > > Am 03.07.2017 um 19:17 schrieb Stefan Sperling : > > > > On Mon, Jul 03, 2017 at 03:31:00PM +0100, Jens Christian Restemeier wrote: > >> Should I open a bug with my findings and the test case? > > > > Yes, please open a bug in the issue t

Re: "Unable to parse reversed revision range" when merging from trunk to branch

2017-07-03 Thread Jens Restemeier
Done: https://issues.apache.org/jira/browse/SVN-4686 > Am 03.07.2017 um 19:17 schrieb Stefan Sperling : > > On Mon, Jul 03, 2017 at 03:31:00PM +0100, Jens Christian Restemeier wrote: >> Should I open a bug with my findings and the test case? > > Y

Re: "Unable to parse reversed revision range" when merging from trunk to branch

2017-07-03 Thread Stefan Sperling
On Mon, Jul 03, 2017 at 03:31:00PM +0100, Jens Christian Restemeier wrote: > Should I open a bug with my findings and the test case? Yes, please open a bug in the issue tracker. A regression test for the subversion/tests tree would be essential. Since you already wrote a test program in C, this f

RE: "Unable to parse reversed revision range" when merging from trunk to branch

2017-07-03 Thread Jens Christian Restemeier
I narrowed it down to the code in subversion/libsvn_subr/mergeinfo.c line 892-898 in adjust_remaining_ranges. At that point next_range actually starts before modified_range, so my guess is svn_sort__array_insert has some unexpected behaviour. x892 svn_merge_range_t *new_mod