Alexander K. Hansen wrote: > On 6/5/06, Kurt Lloyd <[EMAIL PROTECTED]> wrote: >> Hello, >> When I run fink selfupdate-cvs, >> it stalls and eventuall gives up: >> >> Could not connect to bindist.finkmirrors.net:80 (204.152.184.197). - >> connect (60 Operation timed out) > > This is not directly related to your selfupdate method (and why are > you using cvs rather than rsync anyway?) but comes from updating the > binary distribution information.
I had tried fink selfupdate-rsync but had the same problem. Then I read the March 3 note at http://fink.sourceforge.net/ which indicated that I would need the Fink rsync (instead of Apple's), which I don't have. >> I can ping bindist.finkmirrors.net just fine. >> >> Any idea what the problem is? > > And I was able to hit bindist.finkmirrors.net, so it doesn't appear to > be a problem at that end. Do you have a strict firewall? I haven't had a problem in past years with my company's firewall, as long as my proxies are set, which they are. Do you know for certain how I can tell if it's a firewall issue? (I can at least ping bindist.finkmirrors.net.) > You can work around this by running "fink configure" and say no to > "Should Fink try to download pre-compiled packages from the binary > distribution if available? [Y/n]" I would really rather not do this. I use a laptop and am very mobile. Install time is a big deal with me. Right now, for example, the icewm-basic package I'm trying to install wants gcc3.1. Arghhh!! It would be *sooooooo* much preferrable to me to just install the icewm binaries. -Kurt >> (Yes I have read the News at http://fink.sourceforge.net/) >> >> -Kurt Lloyd, [EMAIL PROTECTED] _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
