[MacPorts] #40706: port sync does not work with https source when behind authenticated proxy
MacPorts
noreply at macports.org
Wed Oct 9 09:33:49 PDT 2013
#40706: port sync does not work with https source when behind authenticated proxy
------------------------+-----------------------------------
Reporter: kcrwfrd@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone: MacPorts Future
Component: base | Version: 2.2.0
Resolution: | Keywords: proxy, sources, https
Port: |
------------------------+-----------------------------------
Old description:
> When I follow the directions here:
> https://trac.macports.org/wiki/howto/PortTreeTarball for using https
> instead of rsync to get the ports tree, it fails behind our authenticated
> https proxy server.
>
> We typically set http, https, ftp proxies using environment variables and
> these are picked up by tools like curl. And port install itself actually
> works fine for fetching and installing ports once the ports tar is
> downloaded manually.
>
> But getting the ports tar does not seem to work through a proxy server
> using the port -d sync command.
>
> I get the following:
>
> ---> Updating the ports tree
> Synchronizing local ports tree from
> https://distfiles.macports.org/ports.tar.gz
> Error: Fetching https://distfiles.macports.org/ports.tar.gz failed (Could
> not resolve host: distfiles.macports.org; nodename nor servname provided,
> or not known)
> DEBUG: Synchronization of 1 source(s) failed
> while executing
> "mportsync [array get global_options]"
> port sync failed: Synchronization of 1 source(s) failed
New description:
When I follow the directions here: wiki:howto/PortTreeTarball for using
https instead of rsync to get the ports tree, it fails behind our
authenticated https proxy server.
We typically set http, https, ftp proxies using environment variables and
these are picked up by tools like curl. And port install itself actually
works fine for fetching and installing ports once the ports tar is
downloaded manually.
But getting the ports tar does not seem to work through a proxy server
using the port -d sync command.
I get the following:
{{{
---> Updating the ports tree
Synchronizing local ports tree from
https://distfiles.macports.org/ports.tar.gz
Error: Fetching https://distfiles.macports.org/ports.tar.gz failed (Could
not resolve host: distfiles.macports.org; nodename nor servname provided,
or not known)
DEBUG: Synchronization of 1 source(s) failed
while executing
"mportsync [array get global_options]"
port sync failed: Synchronization of 1 source(s) failed
}}}
--
Comment (by ryandesign@…):
That looks like a DNS problem. Does DNS go through a proxy server as well?
I'm not really familiar with how they work. Are you able to visit
http://distfiles.macports.org in a web browser?
--
Ticket URL: <https://trac.macports.org/ticket/40706#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list