Robert Black wrote:
> Gents, ever since I upgraded to 10.5 on my PPC G5, I have used a  
> completely new installation of fink, not simply the 10.4 version from  
> 10.4.11. 
Which wouldn't work well in any case.  Did the 10.4 version selfupdate
properly before you updated the OS?
> This newer fink 1) does not selfupdate and 2) does not use  
> the unstable tree. 
The two aren't directly connected.
> The error is below. Please do not suggest anything  
> in the FAQ, as I have already tried all the suggestions offered.  There  
> have been 2 system updates since the initial installation, and I  
> haven't yet been able to do an update. I am behind a firewall, but I  
> do not administer that machine and I do not have an account on it. I  
> haven't needed one up to this point.
>
> Any suggestions?
>
> Robert A. Black
>
> Research Meteorologist                  4301 Rickenbacker Cswy.
> NOAA/AOML/HRD                            Miami, FL 33149-1026
>
> Ph:   (305) 361-4314
> FAX: (305) 361-4528 (NEW)
>
> E-Mail: [email protected]
> (Any opinions expressed are mine alone, not NOAA policy)
>
> /Users/rblack
> apollo18:~ rblack$ fink configure
> Password:
>
> OK, I'll ask you some questions and update the configuration file in '/ 
> sw/etc/fink.conf'.
>
> In what additional directory should Fink look for downloaded tarballs?  
> [/] /
>
> Which directory should Fink use to build packages? (If you don't know  
> what this means, it is safe to leave it at its default.) []
>
> Should Fink try to download pre-compiled packages from the binary  
> distribution if available? [Y/n] y
>
> The "unstable" tree contains many packages not present in the "stable"  
> tree and often has newer versions of those that are present.
> All package updates are tested in "unstable" before being approved for  
> "stable", so "unstable" gets new versions and bug-fixes
> sooner. However, that means packages in "unstable" can change rapidly  
> and are occasionally broken temporarily. In addition,
> packages from the "unstable" tree are less likely to be available from  
> bindist servers immediately (if at all).
> The "unstable" tree does not appear to be activated in your fink now.  
> Do you want to activate it? [y/N] n
>
> (1)     Quiet (do not show download statistics)
> (2)     Low (do not show tarballs being expanded)
> (3)     Medium (will show almost everything)
> (4)     High (will show everything)
>
> How verbose should Fink be? [2]
>
> Proxy/Firewall settings
> Enter the URL of the HTTP proxy to use, or 'none' for no proxy. The  
> URL should start with http:// and may contain username,
> password, and/or port specifications. Note that this value will be  
> visible to all users on your computer.
> Example, http://username:passw...@hostname:port
> Your proxy:  [172.16.100.247:80]
> Use the same proxy server for FTP connections? [y/N] y
> Use passive mode FTP transfers (to get through a firewall)? [Y/n] y
>
> Mirror selection
> All mirrors are set. Do you want to change them? [y/N] n
>
> Writing updated configuration to '/sw/etc/fink.conf'...
> apollo18:~ rblack$ fink selfupdate
>
> Fink has the capability to run the CVS commands as a normal user. That  
> has some advantages - it uses that user's CVS settings files
> and allows the package descriptions to be edited and updated without  
> becoming root. Please specify the user login name that should
> be used: [rblack]
>
> For Fink developers only: Enter your SourceForge login name to set up  
> full CVS access. Other users, just press return to set up
> anonymous read-only access. [anonymous]
>
> Checking to see if we can use hard links to merge the existing tree.  
> Please ignore errors on the next few lines.
> Now logging into the CVS server. When CVS asks you for a password,  
> just press return (i.e. the password is empty).
> /usr/bin/su rblack -c 'cvs - 
> d:pserver:[email protected]:/cvsroot/fink login'
> Logging in to :pserver:[email protected]:2401/cvsroot/ 
> fink
> CVS password:
> cvs [login aborted]: connect to  
> fink.cvs.sourceforge.net(216.34.181.110):2401 failed: Connection refused
> ### execution of /usr/bin/su failed, exit code 1
> Failed: Logging into the CVS server for anonymous read-only access  
> failed.
> apollo18:~ rblack$
>
>
>   
There's not much that can be configured via fink here. 

I got rid of our cvs packages on Leopard because Xcode comes with the
most recent version (and I think it actually works better).   Supposedly
Leopard's cvs has proxy support built in to it, but I don't know about
that for a fact. 

cvs-proxy is still available in the 10.5 binary distribution, so the
instructions in

http://www.finkproject.org/faq/usage-fink.php?phpLang=en#firewalled-cvs

may still apply.  However, I don't know how well they work on Leopard,
as I don't have a firewall.

I suggested a FAQ entry because a good fraction of the time time when
users say they "tried everything in the FAQ", they did not, in fact, try
_everything_ that was germane to their issue.  Moreover, saying "I tried
everything"is less helpful for diagnostic purposes than listing the
specific things that you tried.

If you _did_ try cvs-proxy, and it didn't work, then the best thing I
can come up with is to try to find what kind of proxy support (if any)
is built into Apple's cvs.  If there isn't any, then I can pull the
cvs-proxy package back out of retirement and maybe someone else can
actually figure out how to update it to work.  I only maintain cvs
because it was an easy update while I was still green at maintaining
packages.

-- 
Alexander Hansen
Fink User Liaison


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to