[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Gavin Lambert <tsvn_at_mirality.co.nz>
Date: Thu, 27 Jul 2017 19:52:08 +1200

On 22/06/2017 06:41, Jens Restemeier wrote:
> I'm trying to catch up a branch with the changes on trunk. It seems to update the correct files, though at the end it fails with
> [code]
> "Unable to parse reversed revision range '19634-19631'"
> [/code]
> I'm using TortoiseSVN 1.9.5:
> [code]
> E:\Subversion\game01_antiscriptos>svn --version
> svn, version 1.9.5 (r1770682)
> [/code]
> I looked both on trunk and the branch for odd mergeinfo. Trunk has no mergeinfo newer than the branch (the last merge was ages ago). I did a search for those revisions on the branch, but they don't appear reversed:
> [code]
> X:\Subversion>svn propget svn:mergeinfo --depth=infinity | find "19631"
> /trunk:15014-19472,19473-19612*,19613-19614,19615-19630*,19631-19634,19635-20055*
> [/code]
> What exactly is that error message telling me, and how do I resolve it?
>
> I did a google search, but the responses I found were for svn versions from years ago, or for svndumps.
>
> I'm tempted to just copy everything over and to hack the mergeinfo manually, but I'm sure that'll cause more problems.

I could be wrong, but I don't think --depth=infinity makes it do a
recursive search; you need -R for that. So the offending mergeinfo
might be on a subfolder or file rather than at the root. (The usual
guidance is to never merge anywhere but the root, but crap happens.)

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3273685

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-07-27 09:52:38 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.