On Fri, Aug 12, 2011 at 1:52 PM, Ryan Schmidt <[email protected]> wrote: > Correct, selfupdate always uses rsync. There is no setting to change this. > MacPorts 2.0.x does not change this. > > You can use the 2.0.1 .dmg installer to upgrade your MacPorts. This will not > adversely affect any ports you have installed.
Thanks, I was able to upgrade using the installer. Although I should mention that the installer still hangs near the end and requires a force-quit just as it did with 1.9.2 -- I presume because of the rsync issue. I realize that this is an edge case, but it's not exactly friendly failure. > We don't appear to cache the homepage at all on our end (it's being > re-generated by PHP every time it's accessed) and we updated the homepage to > list version 2.0.1 right after it came out, 10 days ago. As soon as I explicitly told Firefox to reload the page, it came up as 2.0.1. I'm not well-versed enough in browser caching to figure out why it happened, but I wonder if there's a cache-control headers issue. Anyway, it's working again, and now this email thread will show up in Google if anyone else runs into this problem. Thanks. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
