Installed macports what to do next

james collins james.collins75 at
Thu Aug 25 13:59:51 PDT 2011


I was showing the output to try and find out what is wrong with rsync.

I won't run selfupdate

Is there a way to test rsync? Like can I try to connect to the macports website to debug?

Also does anyone know how I can view the log file? Or why macports can't find recoll?

Thanks for the help. I appreciate it.

Sent from my iPhone

On Aug 25, 2011, at 4:53 PM, Ryan Schmidt <ryandesign at> wrote:

> On Aug 25, 2011, at 15:48, james collins wrote:
>> Here is what I got from terminal:
>> sudo port -v selfupdate 
>> ----> Updating MacPorts base sources using rsync
>> rsync: failed to connect to Operation timed out (60)
>> rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105)
>> [receiver=2.6.9]
>> shell command "/usr/bin/rsync -rtzv --delete-after rsync:// /opt/local/var/macports/sources/" returned error 10
>> Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)
> "sudo port selfupdate" will not work on your network because rsync does not work on your network.
> "selfupdate" first updates MacPorts base, then, if there were no errors, updates the ports tree. Updating MacPorts base always happens over rsync; there is no option to make this happen over any other protocol. Updating MacPorts base will therefore fail, and selfupdate won't continue to sync your ports.
> So until the rsync issue on your network is fixed, don't run "sudo port selfupdate". Run "sudo port sync" instead.

More information about the macports-users mailing list