Dev - Problems accessing the SVN repository

[Jacopo Cappellato]

Hi all,

one of our customers has recently had problems to perform the svn
checkout of OFBiz.

After a few research I've discovered that the problems were caused by:

1) the customer's firewall that was blocking the port 2401 (needed by svn)
2) the customer's proxy server that doesn't support the WebDav protocol
(needed by some of the svn commands like 'co' and not by others like 'ls')

We have resolved #1 opening the port in the firewall; about #2 we have
discovered that the anonymous checkout using the https protocol was
working fine, so we did:

svn co https://svn.ofbiz.org/svn/ofbiz/trunk ofbiz

I think that this information could be useful for other users and maybe
they could find a place in the following page:

http://svn.ofbiz.org

Jacopo
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Adam Heath-2]

On Tue, 4 Apr 2006, Jacopo Cappellato wrote:

> Hi all,
>
> one of our customers has recently had problems to perform the svn
> checkout of OFBiz.
>
> After a few research I've discovered that the problems were caused by:
>
> 1) the customer's firewall that was blocking the port 2401 (needed by svn)
> 2) the customer's proxy server that doesn't support the WebDav protocol
> (needed by some of the svn commands like 'co' and not by others like 'ls')

2401 is for cvs, 3690 is for svn.  And, besides, why would svn need cvs
access?  I'd consider this a svn bug.  Exactly how did they try to access it?
What program did they use?  What connection string?

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacopo Cappellato]

Adam,

well... the command that was failing was:

svn co http://svn.ofbiz.org/svn/ofbiz/trunk ofbiz

I don't know about the port, and now I'm not sure if opening that port
was useful to solve the problem...

However I'm sure that the:

svn co https://svn.ofbiz.org/svn/ofbiz/trunk ofbiz

has solved the problem.
They are using the svn client 1.3.0 for Windows.

Jacopo

Adam Heath wrote:

> On Tue, 4 Apr 2006, Jacopo Cappellato wrote:
>
>> Hi all,
>>
>> one of our customers has recently had problems to perform the svn
>> checkout of OFBiz.
>>
>> After a few research I've discovered that the problems were caused by:
>>
>> 1) the customer's firewall that was blocking the port 2401 (needed by svn)
>> 2) the customer's proxy server that doesn't support the WebDav protocol
>> (needed by some of the svn commands like 'co' and not by others like 'ls')
>
> 2401 is for cvs, 3690 is for svn.  And, besides, why would svn need cvs
> access?  I'd consider this a svn bug.  Exactly how did they try to access it?
> What program did they use?  What connection string?
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev
>

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacques Le Roux]

From: "Jacopo Cappellato" <[hidden email]>

> Adam,
>
> well... the command that was failing was:
>
> svn co http://svn.ofbiz.org/svn/ofbiz/trunk ofbiz
>
> I don't know about the port, and now I'm not sure if opening that port
> was useful to solve the problem...
>
> However I'm sure that the:
>
> svn co https://svn.ofbiz.org/svn/ofbiz/trunk ofbiz
>
> has solved the problem.
> They are using the svn client 1.3.0 for Windows.
>
> Jacopo

Jacopo,

I also use svn client 1.3.0 for Windows but have not port 2401 nor 3690 open in
my gateway and did not ever have a problem (either with http nor https)

Jacques

> Adam Heath wrote:
> > On Tue, 4 Apr 2006, Jacopo Cappellato wrote:
> >
> >> Hi all,
> >>
> >> one of our customers has recently had problems to perform the svn
> >> checkout of OFBiz.
> >>
> >> After a few research I've discovered that the problems were caused by:
> >>
> >> 1) the customer's firewall that was blocking the port 2401 (needed by svn)
> >> 2) the customer's proxy server that doesn't support the WebDav protocol
> >> (needed by some of the svn commands like 'co' and not by others like 'ls')
> >
> > 2401 is for cvs, 3690 is for svn.  And, besides, why would svn need cvs
> > access?  I'd consider this a svn bug.  Exactly how did they try to access

it?

> > What program did they use?  What connection string?
> >
> >
> > _______________________________________________
> > Dev mailing list
> > [hidden email]
> > http://lists.ofbiz.org/mailman/listinfo/dev
> >
>
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Jacopo Cappellato]

Jacques, Adam,

ok, maybe the firewall was not a problem (so please ignore #1), however
there was a problem with the Proxy server; this is an issue that others
have reported when accessing svn repositories using the http protocol
(not the https one) thru a Proxy that doesn't support the WebDav
protocol; for example see the following message:

http://lists.edgewall.com/archive/trac/2005-May/002961.html

Jacopo
 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev