Thanks a lot. The output I got was: Seans-Mac:~ seanh$ sudo port -d -v selfupdate Password: DEBUG: Rebuilding the MacPorts base system if needed. Synchronizing from rsync://rsync.darwinports.org/dpupdate/dports rsync: failed to connect to rsync.darwinports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-24/rsync/c lientserver.c(94) DEBUG: Couldn't sync dports tree: sync failed doing rsync while executing "darwinports::selfupdate [array get global_options]" Error: /opt/local/bin/port: selfupdate failed: Couldn't sync dports tree: sync f ailed doing rsync The timeout error led me to check my firewall settings. Apparently the stupid wireless gateway/router/cablemodem I have from timewarner wasn't letting rsync through. A few changes and MacPorts was working fine. On 10/3/06, Daniel J. Luke <dluke@geeklair.net> wrote:

On Oct 3, 2006, at 1:05 AM, Sean Hermany wrote:

...

Seans-Mac:~ seanh$ port -v MacPorts 1.320 Entering interactive mode... ("help" for help, "quit" to quit) [Users/seanh] > quit Goodbye Seans-Mac:~ seanh$ sudo port selfupdate Password: Error: /opt/local/bin/port: selfupdate failed: Couldn't sync dports tree: sync failed doing rsync Seans-Mac:~ seanh$

I've tried the command dozens of times thinking it might be busy servers. If anyone could shed some light, I'd really appreciate it.

Add -d -v to the command line to see what's really going on, ie:

port -d -v selfupdate -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+