Unable to parse reversed revision range
Date: Thu, 22 Jan 2009 13:02:45 -0800 (PST)
I posted a reply to a thread in the Collabnet Users discussion list about a "Unable to parse reversed revision range" error. It has been suggested in that thread that I bring up the issue here as well.
The thread from the Collabnet User list (starting at my reply) is here:
The repo in question was created with 1.5.4. An upgrade to 1.5.5 seems to have no effect.
I am also seeing the "unable to parse reversed revision range" error when trying to merge from a parent branch to a child branch. In my case the parent is a user branch branched off of a feature branch and the child is a user branch branched off of the first user branch. The exact error I get is below between the lines of *s:
I believe that the diff between r2 and r3 in my repo is the creation of the feature branch.
In order to reduce the number of variables involved in trying to track this down I have reproduced the problem on a test server that no one but me has access to. I put a restore of the actual repository on the test server. I then created a user branch of of the feature branch. , made a couple changes to it and commited those changes. Then I created a a user branch off of the first user branch. I get this error immediately after creating the new user branch and then trying to merge from the parent to the new child branch. No changes have been committed to either user branch. Perhaps something in the creation of the branch itself is causing the problem?
I have isolated the problem to a specific directory fairly deep in the tree. Interestingly enough if I do a merge of just that directory or *any of its parents except* the very top level of the tree it works. After doing that merge I can then successfully merge the entire tree.
I get no output from the “svn propget svn:mergeinfo” command on the problem directory in either branch. (I tried verbose as suggested but propget doesn’t seem to allow for a verbose flag)
The diff of the problem directory after merging just the problem directory (which seems to solve the problem):
Any insight into what is going on will be much appreciated.
This is an archived mail posted to the Subversion Dev mailing list.