RE: Issue with order of svn:mergeinfo revision ranges vs. svnmerge-migrate-history.py..
From: Gunter Woytowitz <gunter.woytowitz_at_jdsu.com>
Date: Thu, 22 Jan 2009 12:11:45 -0800 (PST)
I have the same problem with out of order AND overlapping svn:mergeinfo properties created by the svnmerge-migrate-history.py script. The problem is that I was not aware of the error for some time and many revisions were commited to the repository with improper svn:mergeinfo data. I have since fixed the invalid svn:mergeinfo properties, but now when someone tries to merge older revisions with a "bad" svn:mergeinfo property I get the "out of order" or "overlapping" revision errors.
THIS IS A HUGE PROBLEM FOR ME!!
Here's the svn:mergeinfo property that's giving me problems.
As you can see it is both out of order (43832 is after 53669) and overlapping (43832-45742 overlaps 43832-49987)
This issue and a partial fix for it is discussed in Issue# 3302.
------- Additional comments from Paul T. Burba Fri Jan 16 17:54:55 -0800 2009 -------
In r35297 I loosened svn_mergeinfo_parse()'s restrictions on unsorted
I have built subversion from sources using the latest trunk revision (r35389), which has the above mentioned change in it. This fixes the "out of order" problem, but not the "overlapping" problem.
The subversion code needs to be modified to relax the tests for overlapping revisions too.
I would accept, as a temporary workaround, some way to completely disable all svn:mergeinfo processing and make the svn client behave as if the repository format was rev 4 instead of rev 5. I would lose svn:mergeinfo data, but at this point I just need to get a merge done!!!
Please help, I need this fixed ASAP!!!
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
This is an archived mail posted to the Subversion Users mailing list.