Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

> > 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' is down when it's your mirror that went down! On the contrary, you should be using a mirror close to you for reg

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

On 26/11/2014, at 3:35 AM, Michael wrote: >> Good luck with that (in Australia). BigPond is the biggest ISP in Oz and >> is owned by Telstra, which owns the entire physical network and all the >> exchanges, though that is slowly changing. Their treatment of other ISPs, >> who share the physical ne

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

> Good luck with that (in Australia). BigPond is the biggest ISP in Oz and > is owned by Telstra, which owns the entire physical network and all the > exchanges, though that is slowly changing. Their treatment of other ISPs, > who share the physical network, and even of their own customers is quit

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

On Nov 24, 2014, at 3:17 PM, Dave Horsfall wrote: > On Mon, 24 Nov 2014, Lawrence Velázquez wrote: > >> There's no particular reason to stick with the "primary" MacPorts >> servers, if you find a mirror that works better for you. I'm not aware >> of problems with any of the mirrors. If you're

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

On 25/11/2014, at 10:11 AM, Clemens Lang wrote: > - On 24 Nov, 2014, at 22:17, Dave Horsfall d...@horsfall.org wrote: >> A minor problem with FreeBSD is that should an ISP-assigned DNS server >> report an error, said ISP helpfully redirects you elsewhere, but luckily >> FreeBSD handles this stu

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

Hi, - On 24 Nov, 2014, at 22:17, Dave Horsfall d...@horsfall.org wrote: > Seeing as MacPorts is based upon FreeBSD ports, perhaps it could copy the > latter's trick of trying servers one by one? That brings the problem that our mirrors are not that closely synced as we would expect, especial

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

On Mon, 24 Nov 2014, Lawrence Velázquez wrote: > There's no particular reason to stick with the "primary" MacPorts > servers, if you find a mirror that works better for you. I'm not aware > of problems with any of the mirrors. If you're not in North America, you > might even benefit from switch

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

On Nov 24, 2014, at 9:08 AM, Dan Johnson wrote: > 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' is down when it's your mirror that went down! There's no particular

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

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 ' is down when it's your mirror that went down! -^-rdj-^- > On Nov 24, 2014, at 9:07 AM, Carlo

Re: FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

Does this fix still allow port selfupdate to work once 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 wrote: > Yesterday, a "port -d selfupdate" revealed that 'rsync.macports.org' was > down. It remained down for many hours. De

FOR FUTURE REFERENCE: when rsync.macports.org is down hard...

Yesterday, a "port -d selfupdate" revealed that '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 bot