Also as UPDATING says you'll need to enable serf support if you still use http methods
-- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jun 22, 2013, at 18:30, Aryeh Friedman <aryeh.fried...@gmail.com> wrote: > Update replacing https:// with svn:// (not http://) does work > > On Sat, Jun 22, 2013 at 6:28 PM, Aryeh Friedman > <aryeh.fried...@gmail.com> wrote: >> SVN can not find the FreeBSD svn repositories despite networking being >> set up right: >> >> root@vcloud:/root # svn checkout >> https://svn0.us-west.FreeBSD.org/ports/head /usr/ports >> svn: E000065: Unable to connect to a repository at URL >> 'https://svn0.us-west.freebsd.org/ports/head' >> svn: E000065: Error running context: No route to host >> root@vcloud:/root # fetch https://svn0.us-west.FreeBSD.org/ports/head >> head 100% of 3378 B 32 MBps >> root@vcloud:/root # fetch https://svn0.us-east.FreeBSD.org/ports/head >> head 100% of 3378 B 32 MBps >> root@vcloud:/root # svn checkout >> https://svn0.us-east.FreeBSD.org/ports/head /usr/ports >> svn: E000065: Unable to connect to a repository at URL >> 'https://svn0.us-east.freebsd.org/ports/head' >> svn: E000065: Error running context: No route to host >> >> any ideas? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
smime.p7s
Description: S/MIME cryptographic signature
