Fwd: Issue with order of svn:mergeinfo revision ranges vs. svnmerge-migrate-history.py..

I just remembered this issue on the users list.

Could somebody please take a look at this issue. If the issue is valid
the result is pretty bad and it should be handled.

Thanks,
   Bert

---------- Forwarded message ----------
From: Clark, Rob <rob_at_ti.com>
Date: 2008/9/10
Subject: Issue with order of svn:mergeinfo revision ranges vs.
svnmerge-migrate-history.py..
To: "users_at_subversion.tigris.org" <users_at_subversion.tigris.org>

This might be something that depended on which version of svnmerge.py you
have, but it seems like svnmerge-migrate-history.py can put discontinuous
revision ranges in the wrong order (ie. '13322-13324,13320' instead of
'13320,13322-13324'). I've been manually fixing this in the latest revision
when merging branches and getting errors, but now I'm running into the issue
that 'svn log -g' is getting tripped up on some older revision:

  Exception: svn: Unable to parse unordered revision ranges '13322-13324'
and '13320'

So now I'm not really sure how to track down the past revisions that need to
be corrected.

I'm not sure if someone has a fix-svnmerge-migrated-history.py script ;-)

Or any other suggested way to fix this?

TIA,
-Rob

(btw, please CC me on reply, I'm not subscribed to the list)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-06 18:45:14 CEST