[MacPorts] #47621: fetch failed, but should not

[MacPorts]

#47621: fetch failed, but should not
----------------------+--------------------------------
  Reporter:  bolet@…  |      Owner:  macports-tickets@…
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  base     |    Version:  2.3.3
Resolution:           |   Keywords:
      Port:           |
----------------------+--------------------------------

Comment (by larryv@…):

 Replying to [comment:5 bolet@…]:
 > But /opt/local/etc/macports/macports.conf mentions no proxy. And both
 > wget and curl work... maybe they don't use System settings whereas
 > MacPorts does?

 These comments in `macports.conf` explain exactly where MacPorts gets its
 proxy settings.

 {{{
 # Override proxy-related environment variables. By default, MacPorts
 # takes proxy settings from the environment, from the proxy_* options
 # below, and from Network Preferences, in that order. If this is set to
 # "yes", MacPorts uses proxy_*, then Network Preferences, then the
 # environment. (Note that Network Preferences does not have a setting
 # for rsync proxies. Also note that sudo(8) sanitizes its environment on
 # OS X 10.5 and later, so it may have to be configured to pass desired
 # variables to MacPorts.)
 #proxy_override_env     no

 # Proxies. These have no default values. The analogous environment
 # variables are "http_proxy", "HTTPS_PROXY", "FTP_PROXY", and
 # "RSYNC_PROXY".
 #proxy_http             proxy1:12345
 #proxy_https            proxy2:67890
 #proxy_ftp              proxy3:02139
 #proxy_rsync            proxy4:11377
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/47621#comment:6>
MacPorts <https://www.macports.org/>
Ports system for OS X