[MacPorts] #47314: Error: org.macports.fetch for port mesa returned: fetch failed

[MacPorts]

#47314: Error: org.macports.fetch for port mesa returned: fetch failed
-------------------------+-------------------
  Reporter:  diochnos@…  |      Owner:  jmr@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  base        |    Version:  2.3.3
Resolution:              |   Keywords:  ftp
      Port:  curl        |
-------------------------+-------------------

Comment (by russ.bubley@…):

 Replying to [comment:20 diochnos@…]:

 I just tried again on a machine apparently running the same software as
 diochnos (Yosemite 10.10.3, with the exact same version of `curl`).

 I get the same at the start
 {{{
 $ /usr/bin/curl -v
 ftp://ftp.freedesktop.org/pub/mesa/10.4.7/MesaLib-10.4.7.tar.bz2
 * Hostname was NOT found in DNS cache
 *   Trying 131.252.210.176...
 * Connected to ftp.freedesktop.org (131.252.210.176) port 21 (#0)
 < 220 Welcome to the freedesktop.org FTP server.
 > USER anonymous
 < 331 Please specify the password.
 > PASS ftp at example.com
 < 230 Login successful.
 > PWD
 < 257 "/"
 * Entry path is '/'
 > CWD pub
 * ftp_perform ends with SECONDARY: 0
 < 250 Directory successfully changed.
 > CWD mesa
 < 250 Directory successfully changed.
 > CWD 10.4.7
 < 250 Directory successfully changed.
 > EPSV
 * Connect data stream passively
 }}}

 then it waits for 5 minutes followed by
 {{{
 421 Timeout.ng Extended Passive Mode (|||36683|)
 * Hostname was NOT found in DNS cache
 * Connection time-out
 * Failed EPSV attempt. Disabling EPSV
 > PASV
 * response reading failed
 * Closing connection 0
 curl: (56) response reading failed
 }}}

 So where does that leave us? It seems that there isn't a problem at the
 server end, and with configs that are pretty close at the client end, it
 seems unlikely that the problem is there, either.

 According to http://blogs.msdn.com/b/spike/archive/2013/07/04/a-network-
 analysis-of-passive-epsv-or-pasv-ftp-connection.aspx, EPSV connections can
 be troublesome to get right in firewalls - so it may well be a bug in my
 router, or a problem with the firewall at my ISP. So not obviously
 something that macports can fix, in general.

 In the specific case of `mesa`, the problem may be worked around by adding
 the following to the port file:
 {{{
 fetch.use_epsv      no
 }}}

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