Opened 11 years ago
Last modified 12 months ago
#40706 closed defect
port sync does not work with https source when behind authenticated proxy — at Version 1
Reported by: | kcrwfrd@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.2.0 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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
Change History (1)
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
Note: See
TracTickets for help on using
tickets.
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?