Re: pkg/47054 (benchmarks/super_pi: source unfetchable and restricted)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/47054; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: John Marino <netbsd%marino.st@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, pkgsrc-bugs%NetBSD.org@localhost
Subject: Re: pkg/47054 (benchmarks/super_pi: source unfetchable and restricted)
Date: Sat, 13 Oct 2012 17:57:51 +0700

     Date:        Sat, 13 Oct 2012 09:41:50 +0200
     From:        John Marino <netbsd%marino.st@localhost>
     Message-ID:  <50791B3E.9040900%marino.st@localhost>
 
   | If I use filezilla in passive mode, I can connect.
 
 OK.  That's something.
 
   | I noted that ftp://pi.super-computing.org/Linux/ is a softlink to 
   | ftp://pi.super-computing.org/pub/exec_Linux/ but changing MASTER_SITES 
   | to that doesn't allow the package to fetch.  It still times out.
 
 That wouldn't be likely to alter anything, the problem you have seems to
 be when it tries the data transfer, which is the first time a data connection
 is required - so making the data connection looks to be the problem.
 
   | The client here (I think) is "fetch" which is what pkgsrc dictates.
 
 OK, in that case, it isn't likely to be an EPSV problem, as I don't
 thing fetch (or libfetch) attempt EPSV for IPv4 connections, only for
 IPv6 (which is probably a sensible design choice, even though EPSV should
 work just fine for v4 as well).
 
   | I'm wondering if there are any settings like passive that can be put 
   | into the makefile that could help fetch succeed.
 
 fetch should use passive mode by default, but you should be able to
 make quite certain by putting
        FTP_PASSIVE_MODE=YES
 in your environment.
 
 kre