Changes between Initial Version and Version 1 of Ticket #40706


Ignore:
Timestamp:
Oct 9, 2013, 4:33:48 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

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?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #40706 – Description

    initial v1  
    1 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.
     1When 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.
    22
    33We 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.
    … …  
    77I get the following:
    88
     9{{{
    910--->  Updating the ports tree
    1011Synchronizing local ports tree from https://distfiles.macports.org/ports.tar.gz
    … …  
    1415"mportsync [array get global_options]"
    1516port sync failed: Synchronization of 1 source(s) failed
     17}}}