[MacPorts] #45190: llvm-3.5 : use https with svn when building
#45190: llvm-3.5 : use https with svn when building ------------------------------+-------------------------------- Reporter: mk-macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: llvm, snv, https | Port: llvm-3.5 ------------------------------+-------------------------------- Hi, i fell over this weird bug: http://stackoverflow.com/questions/21033706/svn-e175002-unable-to-connect- to-a-repository-at-url resulting in me being unable to build llvm-3.5 and getting this error: {{{ svn: E175002: Unable to connect to a repository at URL ... }}} Is there any reason in particular that you are not using https when fetching with svn? Otherwise this would solve 2 problems (weird bug above and insecure transfer) at once. cheers -- Ticket URL: <https://trac.macports.org/ticket/45190> MacPorts <http://www.macports.org/> Ports system for OS X
#45190: llvm-3.5 : use https with svn when building ----------------------------+------------------------ Reporter: mk-macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: llvm-3.5 | ----------------------------+------------------------ Changes (by ryandesign@…): * owner: macports-tickets@… => jeremyhu@… * keywords: llvm, snv, https => Comment: Much better would be to use a distfile, not fetch via svn. This would be solved by #44938. -- Ticket URL: <https://trac.macports.org/ticket/45190#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#45190: llvm-3.5 : use https with svn when building ----------------------------+------------------------ Reporter: mk-macports@… | Owner: jeremyhu@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: worksforme | Keywords: Port: llvm-3.5 | ----------------------------+------------------------ Changes (by jeremyhu@…): * status: new => closed * resolution: => worksforme Comment: Report your bug to Cisco if it is the same as the stackoverflow report. As far as "insecure transfer" ... uh... no. It's not worth the extra CPU overhead to encrypt public data. -- Ticket URL: <https://trac.macports.org/ticket/45190#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts