Re: [Fink-users] Using fink with password-protected proxies

2002-01-25 Thread Stuart Lamble
> On Thursday, January 24, 2002, at 03:30 PM, Max Horn wrote: > > > And b) we require you to have a valid SF ID first, because it means we > > are guranteed bug reporters are reachable by email. Bug reports are > > often utterly incomplete, and we have to ask back if we want to have > > chance

Re: [Fink-users] Using fink with password-protected proxies

2002-01-25 Thread Finlay Dobbie
On Thursday, January 24, 2002, at 03:30 PM, Max Horn wrote: > And b) we require you to have a valid SF ID first, because it means we > are guranteed bug reporters are reachable by email. Bug reports are > often utterly incomplete, and we have to ask back if we want to have > chance to fix 'em

Re: [Fink-users] Using fink with password-protected proxies

2002-01-24 Thread Max Horn
At 15:28 Uhr +1100 24.01.2002, Stuart Lamble wrote: >First off, a couple of (slightly off-topic) observations: > - The archives at geocrawler don't have any search facility. It's a bit > harsh to expect somebody to wade through nearly 6,000 messages in an > attempt to find relevant infor

Re: [Fink-users] Using fink with password-protected proxies

2002-01-23 Thread Stuart Lamble
> Hi, > try : > %sudo mv /sw/bin/curl /sw/bin/curl.not > %sudo mv /usr/bin/curl /usr/bin/curl.not > > Fink should then use wget. That worked. Thanks. ___ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users

Re: [Fink-users] Using fink with password-protected proxies

2002-01-23 Thread Peter O'Gorman
Hi, try : %sudo mv /sw/bin/curl /sw/bin/curl.not %sudo mv /usr/bin/curl /usr/bin/curl.not Fink should then use wget. Peter ___ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users

[Fink-users] Using fink with password-protected proxies

2002-01-23 Thread Stuart Lamble
First off, a couple of (slightly off-topic) observations: - The archives at geocrawler don't have any search facility. It's a bit harsh to expect somebody to wade through nearly 6,000 messages in an attempt to find relevant information... - I tried to submit a bug report, but sourcefor