Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2005-12

svn

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Bob Barry

The move from cvs to svn has been a disaster for me. There was a time that desproxy would circumvent the proxy of my uncooperative ISP, but the scripts which worked before no longer work. I tried to checkout subversion itself, and that doesn't work either. But I _can_ checkout subversion using https. Could fpc's subversion server be configured to accomodate https? Please?

Thanks,

Bob Barry

Florian Klaempfl
to Bob Barry
Bob Barry wrote
The move from cvs to svn has been a disaster for me. There was a time that desproxy would circumvent the proxy of my uncooperative ISP, but the scripts which worked before no longer work. I tried to checkout subversion itself, and that doesn't work either. But I _can_ checkout subversion using https. Could fpc's subversion server be configured to accomodate https?

How did you check out in cvs times then?

Show quoted text 9 lines
Please? Thanks, Bob Barry _______________________________________________ fpc-pascal maillist - http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Tomas Hajny
to Florian Klaempfl
Florian Klaempfl wrote 12 lines
Bob Barry wrote: > The move from cvs to svn has been a disaster for me. There was a time > that desproxy would > circumvent the proxy of my uncooperative ISP, but the scripts which > worked before no longer > work. I tried to checkout subversion itself, and that doesn't work > either. But I _can_ checkout > subversion using https. Could fpc's subversion server be configured to > accomodate https? How did you check out in cvs times then?

Maybe his ISP puts a transparent proxy in the way for all traffic on port 80 and that proxy doesn't work quite well in cooperation with SVN? That would clarify HTTPS working OK, because no transparent proxies are possible for HTTPS... If this guess is correct (and depending on the configuration of his ISP - whether the proxy is only triggered for port 80 or whether all communication is intercepted and analyzed for HTTP protocol), it might be enough to let SVN listen on another port (in addition to the default port 80) to avoid performance overhead required for https (if this overhead is not wanted/acceptable).

Tomas

Bob Barry
to Florian Klaempfl: How did you check out in cvs times then?

Florian -

you wrote 6 lines
> The move from cvs to svn has been a disaster for me. There was a time that desproxy would > circumvent the proxy of my uncooperative ISP, but the scripts which worked before no longer > work. I tried to checkout subversion itself, and that doesn't work either. But I _can_ checkout > subversion using https. Could fpc's subversion server be configured to accomodate https? How did you check out in cvs times then?

CVS works normally through the proxy. SVN demands a number of http services which the proxy does not provide (extension_methods REPORT MERGE MKACTIVITY CHECKOUT, etc). I gave the subversion page describing the required services (http://subversion.tigris.org/faq.html#proxy) to the ISP, but they have been uncooperative. Desproxy used to be sufficient to get around the proxy, but it stopped working a few months ago. I've tried proxychains, same story. I saw a Nov 2005 forum item from "Funky Beast" complaining of the same thing, and there must be others in the same predicament. Using https would provide a clean fix for all fpc users behind proxies, and would eliminate the need for each one to plead, cajole and fight with his ISP.

Thanks,

Bob