Hmmm. Thanks for the suggestion, but that doesn't seem to do anything:
[exschmoo:~] adpeters% curl --disable-epsv -f -L -P - -O ftp://ftp.gnome.org/pub/GNOME/sources/gnome-print/0.36/gnome-print- 0.36.tar.bz2
curl: (19) Server does not grok EPRT
Another strange thing about this problem is it's not always error code 19 that curl exits with.
--A
On Tuesday, November 12, 2002, at 01:45 PM, Daniel Westermann-Clark wrote:
I don't know if your version of curl supports it, but mine (on Red Hat
7.3, curl 7.9.5 (i386-redhat-linux-gnu) libcurl 7.9.5 (OpenSSL 0.9.6b)
(ipv6 enabled)) accepts the --disable-epsv command line option. Give it a
try in your version by calling curl on the command line with one of the
failed fink downloads:
curl --disable-epsv -f -L -P - -O
ftp://ftp.gnome.org/pub/GNOME/sources/gnome-print/0.36/gnome-print- 0.36.tar.bz2
Hope this helps,
-Daniel
On Tue, 12 Nov 2002, Andy Peters wrote:
Howdy, folks-
Yes, this might look like a newbie question, but it's not.
I've been running fink forever, and I'm in the midst of installing it
on my new (pre-latest update) 14-inch iBook. I'm getting some strange
behavior from curl when I try to fun a fink update-all (or any other
fink command that calls curl a lot). Basically, downloads very often
fail to work for particular types of files (files from gnome and gnu
mirrors seem particularly bad, but they're not the only ones). For
example, here's an abridged version of my latest run of fink update-all:
curl -f -L -P - -O
ftp://ftp.gnome.org/pub/GNOME/sources/gnome-print/0.36/gnome-print-
0.36.tar.bz2
curl: (19) Server does not grok EPRT
### execution of curl failed, exit code 19
[...]
<snip>The problem is NOT that the path is wrong. This is what's so weird: I
just did a fink selfupdate-cvs. And even weirder: I can copy the path
from the fink output (e.g.,
ftp://ftp.gnome.org/pub/GNOME/sources/gnome-print/0.36/gnome-print-
0.36.tar.bz2), and feed it directly to the ftp client (e.g., on the
command line: ftp
ftp://ftp.gnome.org/pub/GNOME/sources/gnome-print/0.36/gnome-print-
0.36.tar.bz2), and it downloads without a problem!
The weirdest thing of all is that I'm running a fink update-all on my
desktop machine at the same time in order to bring it up to date with
OS X 10.2 -- and it's not giving me the same problem! Is it possible
for curl to be broken on my machine in some way? (Yes, I've tried fink
update curl).
Please help -- it's sort of maddening to have to run fink to find out
which file it can't download next, manually download the file, restart
fink to find out what the next problem file is, manually download the
next file, etc., etc.
PGP.sig
Description: PGP signature
