FYI,
I ran into a similar problem (see earlier thread on openpkg-dev titled
"FYI: openpkg-tool -> openpkg-tools"), but in my case I have no control
over the firewall, so I had to find a workaround.
Modifying .curlrc did not help.
>From the earlier thread:
----------------------
So I found build.pl and examined it, and found this (starting at line
1100):
print "# curling index $fetch\n";
if ($fetch =~ /\.bz2$/) {
$path = "$CURL -q -s -o - \"$fetch\" | $bzip2 -dc |";
} else {
$path = "$CURL -q -s -o - \"$fetch\" |";
}
>From the docs for curl, it looks like -q as the first argument *disables*
.curlrc
Therefore, removing it solved my problem. Adding --disable-epsv to the
command line above also had the same effect.
I'm sure there are some good reasons to use -q, but in my case, since EPSV
doesn't work, it would be nice to disable it without modifying build.pl
Should we call this a bug or a feature? 8-)
-------------------------
On Thu, 22 Apr 2004, Aaron Bostick wrote:
> Michael van Elst wrote:
>
> > On Thu, Apr 22, 2004 at 10:37:11AM -0500, Aaron Bostick wrote:
> >
> >> Any other reasons why I would get a FATAL I/O error? Am I doing
> >> something
> >> wrong? Should I just stick with the rpm --rebuild / -Uvh cause that is
> >> working for me but doesn't do the nice dep checking.
> >
> > You probably have a firewall that blocks extended passive ftp transfers
> > (EPSV command).
> >
>
> Michael, you're beautiful! :) I did a "no fixup protocol ftp" on my pix and
> it works now! :)
>
> Thanks!
>
> PS Another really lame question: I ran "openpkg build -Dsudo::with_pam=yes
> sudo" and I saw it added to list pam, fsl, and sudo but it doesn't look
> like it actually installed them and there are no new packages in RPM/PKG.
> Am I missing a step?
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
