I've been trying for a couple daze to get Darwin/MacPorts to install but still have problems. I followed the directions on the wiki http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts but when I get to the update step I get.... $ sudo port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. DEBUG: Synchronizing ports tree(s) Synchronizing from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/ release/ports/ /opt/local/var/macports/sources/rsync.macports.org/ release/ports rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-24.1/rsync/clientserver.c(94) DEBUG: Couldn't sync the ports tree: sync failed doing rsync while executing "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldn't sync the ports tree: sync failed doing rsync It looks like rsync is failing to connect. Perhaps the server is too busy? Or perhaps my company firewalls are blocking it? Suggestions? Thanks Jerry Isdale isdale@avinc.com
Hi Jerry,
It looks like rsync is failing to connect. Perhaps the server is too busy? Or perhaps my company firewalls are blocking it? Suggestions?
My company firewalls does block rsync and it was my problem to get the updates. I could connect to rsync, so it seems working well. The solution to the firewall problem was to change the rsync target for the svn repository in /opt/local/etc/macports/source.conf. The svn address is: http://svn.macosforge.org/repository/macports/trunk/ I wonder however whether the MacPorts team prefers users to avoid using the svn, as most of the official information leads to rsync. Eric Platon -- View this message in context: http://www.nabble.com/newbie-selfupdate-fails-tf4120147.html#a11755851 Sent from the MacPorts - Users mailing list archive at Nabble.com.
On Jul 23, 2007, at 21:11, Eric Platon wrote:
It looks like rsync is failing to connect. Perhaps the server is too busy? Or perhaps my company firewalls are blocking it? Suggestions?
My company firewalls does block rsync and it was my problem to get the updates. I could connect to rsync, so it seems working well. The solution to the firewall problem was to change the rsync target for the svn repository in /opt/local/etc/macports/source.conf. The svn address is: http://svn.macosforge.org/repository/macports/trunk/
I wonder however whether the MacPorts team prefers users to avoid using the svn, as most of the official information leads to rsync.
Feel free to use the svn method. The svn repository is, after all, the master; the rsync version is merely copied from that. I have used the svn method for many months. By doing so, you will get updates quicker than rsync users. (The rsync version only syncs with the svn repository every half hour or so.) The only reason (that I know of) that MacPorts does not use svn by default is that Mac OS X does not include the svn software, but does include the rsync software, and requiring users to build svn (and all its dependencies) would be a bit heavy.
participants (3)
-
Eric Platon
-
Jerry Isdale
-
Ryan Schmidt