FOR FUTURE REFERENCE: when rsync.macports.org is down hard...
rdj999 at gmail.com
Mon Nov 24 06:08:32 PST 2014
You will be using the mirror until you revert your changes. I would restore the default configuration so you don't get caught mistakenly thinking that 'rsync.macports.org <http://rsync.macports.org/>' is down when it's your mirror that went down!
> On Nov 24, 2014, at 9:07 AM, Carlo Tambuatco <oraclmaster at gmail.com> wrote:
> Does this fix still allow port selfupdate to work once rsync.macports.org <http://rsync.macports.org/> is up again? Or do you need to reverse the changes?
> On Mon, Nov 24, 2014 at 8:52 AM, Dan Johnson <rdj999 at gmail.com <mailto:rdj999 at gmail.com>> wrote:
> Yesterday, a "port -d selfupdate" revealed that 'rsync.macports.org <http://rsync.macports.org/>' was down. It remained down for many hours. Despite mirroring, that's evidently an Achilles' Heel in the default configuration's mechanism. I found a way around it, and it wasn't obvious, requiring temporary modifications to both 'macports.conf' and 'sources.conf'.
> Should this happen again, here's a blog entry that others may find useful in the future:
> http://rdj999.blogspot.com/2014/11/eek-macports-is-down.html <http://rdj999.blogspot.com/2014/11/eek-macports-is-down.html>
> Note: after modifying those two files, 'port -d selfupdate' worked one time, however, one of the files required "re-fixing", because 'selfupdate' in MacPorts 2.3.3 evidently "fixes" the repository flags in 'sources.conf' to break it again. (That's also explained in the blog.)
> macports-users mailing list
> macports-users at lists.macosforge.org <mailto:macports-users at lists.macosforge.org>
> https://lists.macosforge.org/mailman/listinfo/macports-users <https://lists.macosforge.org/mailman/listinfo/macports-users>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users