I've figured it out. I just started a new job and I was trying to wrongly merge a older branch into a newer branch that already had the old branches revisions and that was how the exception was being generated.
On Thu, Apr 26, 2018 at 3:14 AM, Stefan Sperling <s...@apache.org> wrote: > On Wed, Apr 25, 2018 at 04:59:23PM -0700, Randy Martinez wrote: > > I'm on Tortoise SVN 1.10 and I'm getting this exception trying to resolve > > any merge conflict from a merge: > > Unfortunately, we do not learn enough from the information provided > to independently reproduce this problem. > > Can you explain which series of operations leads to this assertion > failure, ideally when starting from a new empty repository? > > Thanks. > > > > > --------------------------- > > 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 > > https://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 file > > 'D:\Development\SVN\Releases\TortoiseSVN-1.10.0\ext\ > subversion\subversion\libsvn_client\conflicts.c' > > line 2257: assertion failed (start_rev > end_rev) > > --------------------------- > > OK > > --------------------------- >
