Due to some dated problems with cvs, I made a slight modification to my fink set up to allow rsync to navigate past my proxy. I added some proxy info to the fink.conf
rsync_proxy=http://bpabbott:[EMAIL PROTECTED]:80 PROXYRSYNC=http://bpabbott:[EMAIL PROTECTED]:80 In addition, the following lines were be added to /sw/bin/init.sh. PROXYRSYNC=`grep ProxyRSYNC /sw/etc/fink.conf [...] `| grep -v "#" | cut -d " " -f2` if [ "$PROXYRSYNC" != "" ]; then RSYNC_PROXY=$PROXYRSYNC rsync_proxy=$PROXYRSYNC export RSYNC_PROXY rsync_proxy fi The equivalent lines were added to /sw/bin/init.csh set PROXYRSYNC=`grep ProxyRSYNC /sw/etc/fink.conf [...] | grep -v "#" | cut -d " " -f2` if ( "$PROXYRSYNC" != "" ) then setenv RSYNC_PROXY $PROXYRSYNC setenv rsync_proxy $PROXYRSYNC endif This solution worked for quite some time. However, since ~October I've not been able to do a selfupdate. Today I decided to do something about it. At the present time, I can neither get rsync to work, nor does cvs-proxy work. I've tried both Apple's rsync and fink's. They each produce the same result. ====================RSYNC===================== bpabbott:~ bpabbott$ fink selfupdate-rsync Please note: the command 'fink selfupdate' should be used for routine updating; you only need to use 'fink selfupdate-cvs' or 'fink selfupdate-rsync' if you are changing your update method. rsync -az -v rsync://master.us.finkmirrors.net/finkinfo//TIMESTAMP /sw/fink/TIMESTAMP.tmp bad response from proxy -- HTTP/1.0 403 Forbidden rsync: failed to connect to superman.sawtek.com: Unknown error: 0 (0) rsync error: error in socket IO (code 10) at clientserver.c(98) ### execution of rsync failed, exit code 10 Failed to fetch the timestamp file from the rsync server: rsync://master.us.finkmirrors.net/finkinfo/. Check the error messages above. (1) Give up (2) Retry the same mirror (3) Retry another mirror from your country (4) Retry another mirror How do you want to proceed? [3] <snip> ====================RSYNC===================== Seeing an error respecting the proxy made me suspicious that port 873 was closed. However, I asked and am told it is open. I noticed a fairly recent problem with rsync and fink version 0.22.0 ... so I checked my version Package manager version: 0.24.15 Distribution version: 0.8.0.rsync Copyright (c) 2001 Christoph Pfisterer Copyright (c) 2001-2006 The Fink Package Manager Team This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. Although, my version appears to be good, I decided to try cvs anyway. =====================CVS===================== bpabbott:~ bpabbott$ fink selfupdate-cvs Please note: the command 'fink selfupdate' should be used for routine updating; you only need to use 'fink selfupdate-cvs' or 'fink selfupdate-rsync' if you are changing your update method. 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: [bpabbott] 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 bpabbott -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 bpabbott(172.16.15.29):0 failed: Can't assign requested address ### execution of /usr/bin/su failed, exit code 1 Failed: Logging into the CVS server for anonymous read-only access failed. =====================CVS===================== Regarding cvs-proxy, I have a naive question; do I need port 2401 open? ... it is not. If the answer is yes, is the error I'm getting consistent with port 2401 being closed? Also, I'd prefer to use rsync, any idea why I'm having trouble? TIA ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-beginners mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-beginners
