Re: Unable to parse reversed revision range

[Philip Martin]

Trent Fisher  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*

http:// works on intranet but not internet

[James]

I was able to access SVN server from different machines by using my public ip 
address, such as http://146.115.74.4/svn/repository1, within my home network. 
But I cannot access it from outside with internet. The test web page behave the 
same. I am using the default port: 80.

I have configured my FVS318 NETGRAR router forwarding the http traffic to my 
web server machine which is the same machine as the SVN server.
Any idea?
Thanks,James

Re: http:// works on intranet but not internet

[Joseph Bruni]

> On Feb 11, 2015, at 8:54 PM, James  wrote:
> 
> I was able to access SVN server from different machines by using my public ip 
> address, such as http://146.115.74.4/svn/repository1, 
>  within my home network. But I cannot 
> access it from outside with internet. The test web page behave the same. I am 
> using the default port: 80.
> 
> I have configured my FVS318 NETGRAR router forwarding the http traffic to my 
> web server machine which is the same machine as the SVN server.
> 
> Any idea?
> 
> Thanks,
> James


Many ISPs block port 80 unless you purchase a “commercial grade” internet 
connection. Check your terms and conditions. You’ll probably find some language 
that explicitly prohibits you from running a server.

This is easy enough to work around. Just have your web server listen on a 
different port other than the well known http port 80.