[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 while merging from trunk to a branch

From: <blackhole_at_collab.net>
Date: Mon, 16 Feb 2009 07:17:22 -0800 (PST)


I'm getting this error message when trying to merge a tag into a branch. Both the tag and the branch were derived from the same branch originally; the tag contains some changes made on the source branch that don't exist yet on the target branch.

A simplified diagram would look something like:

 -> copy to branches/branchB
make a change
make another change
 -> copy to tags/tag1
    -> attempt to merge tags/tag1 into branches/branchB

The output from svn was "Unable to parse reversed revision range '514863-514862'".

We're using svn 1.5.4 on the server, and svn 1.5.4 (command line) and Tortoise 1.5.6 (based on svn 1.5.4) on the client.

By drilling down and merging subfolder by subfolder, I've been able to identify the directory causing the issue. I've noticed the following:
* I can merge the subfolders of the problem directory without any problems
* after merging the subfolders, the problem directory still causes problems
* neither the source nor the target problem folder contain any note of a 514863-514862 reverse merge in their svn:mergeinfo properties
* in fact, the svn:mergeinfo properties for both the source and target problem folders are blank
* running "svn pg svn:mergeinfo --recursive" on the root folder of either the source or target branches doesn't turn up any "514863-514862" strings
* looking at the output of "svn log", it seems both revisions 514862 and 514863 involved copying branches from one place to another. One of those two involved copying to a branch which is the ancestor of the original branch (branchA in the example above), but that ancestor has since been deleted.

I see that this issue was posted to the dev mailing list, but the trail turns cold after a while. If anyone knows what whether this is a known issue and/or whether there is a workaround or resolution, any information would be greatly appreciated (I couldn't find anything in the issue tracker about this).



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-16 16:18:43 CET

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.