Unable to parse reversed revision range

[Trent Fisher <tr...@oracle.com>]

I am doing a dump/load of a repository, and ran into an odd (fatal) 
error on the load:

<<< Started new transaction, based on original revision 209
svnadmin: E200020: Unable to parse reversed revision range '29584-200'

I figured this would be easy enough to fix by adding 
--bypass-prop-validation to the load, but I got the same error.  I 
looked in the dump file, and sure enough, the rev numbers are backwards 
as stated.  However, I don't understand why load would fail.  I am just 
trying to do some repository migrations and I could care less whether 
those properties are correct or not, that's the users' problem (good 
attitude, eh? :)  Shouldn't --bypass-prop-validation cover this 
validation as well?

I thought about correcting the property, but since it is a versioned 
property, I'm not sure how it can be fixed (without doctoring the svn 
dump file).

I tried this with both SVN 1.6.11 and 1.8.9.  But both got the exact 
same error.

Is this a known problem (fixed since 1.8.9) or is there a workaround?

++thanks,
trent...

Re: Unable to parse reversed revision range

[Philip Martin <ph...@wandisco.com>]

Trent Fisher <tr...@oracle.com> writes:

> However, in the mean time, I'll need to correct that svn:merginfo
> property so it is not invalid.  Am I correct that the only way to do
> this is via a dump/filter/load sequence?

Yes, you are changing a versioned property that is part of a revision
and revisions are immutable.

In 1.9 "svnadmin verify" has new options --check-normalization and
--keep-going that make it easier to identify the revisions that need to
be changed.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*

Re: Unable to parse reversed revision range

[Trent Fisher <tr...@oracle.com>]

On 02/11/2015 04:31 AM, Philip Martin wrote:
> Trent Fisher<tr...@oracle.com>  writes:
>> Is this a known problem (fixed since 1.8.9) or is there a workaround?
> Issue 4414 applies:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4414
>
> Your particular case is fixed by r1643074 and proposed for the next 1.8:
> ...

Many thanks!

However, in the mean time, I'll need to correct that svn:merginfo 
property so it is not invalid.  Am I correct that the only way to do 
this is via a dump/filter/load sequence?

++thanks,
trent...

Re: Unable to parse reversed revision range

[Philip Martin <ph...@wandisco.com>]

Trent Fisher <tr...@oracle.com> writes:

> Is this a known problem (fixed since 1.8.9) or is there a workaround?

Issue 4414 applies:
http://subversion.tigris.org/issues/show_bug.cgi?id=4414

Your particular case is fixed by r1643074 and proposed for the next 1.8:

$ svnadmin create repo
$ svnmucc -mm -U file://`pwd`/repo mkdir A propset svn:mergeinfo /B:1-3 A
$ svnadmin create repo2
$ svnadmin dump repo | sed 's/1-3/3-1/' | svnadmin load repo2
svnadmin: E200020: Unable to parse reversed revision range '3-1'

$ svnadmin dump repo | sed 's/1-3/3-1/' | svnadmin load repo2 --bypass-prop-validation
WARNING 0x0005: Invalid svn:mergeinfo value; leaving unchanged
------- Committed revision 1

$ svnlook propget repo2 svn:mergeinfo A
/B:3-1

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*