On Jan 9, 2008, at 4:20 PM, Ryan Schmidt wrote:
Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Synchronizing local ports tree from rsync://rsync.macports.org/ release/ports/ Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: failed to connect to rsync.macports.org: Connection refused (61) Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ rsync/clientserver.c(94) Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: / opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization the local ports tree failed doing rsync Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An attempt to synchronize your recent MacPorts installation with the project's rsync server failed! Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please run 'port -d selfupdate' manually to find out the cause of the error. Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The following install step failed: run postflight script for MacPorts-1.6.0. Contact the software manufacturer for assistance.
So the postflight script failed because it couldn't connect to the rsync server. Doesn't matter why it happened (whether our rsync server was down (which it wasn't) or whether the user's firewall prevented the connection); we should ensure that any inability to connect to the rsync server does not cause the postflight script to fail like that. Best thing would be if we could pop up a friendly message to the user that they need to update their installation themselves, but it might also be ok to just silently fail. In any event, the installation in the Installer should complete.
Done! -jmpp