On 22 August 2012 15:16, Dale Henrichs <dhenrich@vmware.com> wrote:
Yes, it's the travis builds ... It's more than ObjectsAsMethodsWrapper, because once the mirror is installed all squeaksource requests are routed to the mirror, so failing to load ObjectsAsMethodsWrapper is not the only issue.
I am unconditionally using the mirror in the Travis images...
I will now have to make a flag in the builder to allow one to choose whether to use the mirror or not ... that way when squeaksource flakes out you can use the mirror (assuming the mirror is resurrected ... it's been down for days) and use squeaksource when it is available ...
Isn't a flag more complicated than a fall-over? In other words, try SS, fail, use LatAm (or vice versa). My hacks for ConfigurationOfControl class >> bootstrapPackage:from: did this, and I'd like to think they don't completely suck. Otherwise your build fails and you have to edit its invocation to get it to work, by which time source A has disappeared and source B's back up, so you unflick the flag and ... There's a thought half-formed in my head. It's something like this: a configuration says "I'm built out of parts called foo, bar and baz. Where they come from I don't care." Something else (by default, at least) does the searching, trying various well-known configurations. Er, I guess something a bit like Maven's repository mirrors: http://maven.apache.org/guides/mini/guide-mirror-settings.html. But that's more of a long term solution, and not something you'd want to get into just before ESUG. frank
Dale ----- Original Message ----- | From: "Frank Shearar" <frank.shearar@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, August 22, 2012 12:54:15 AM | Subject: Re: [Pharo-project] latam mirror down? | | On 21 August 2012 22:20, Dale Henrichs <dhenrich@vmware.com> wrote: | > http://www.dsal.cl/squeaksource/ | > | > http://www.downforeveryoneorjustme.com/http://www.dsal.cl/squeaksource/ | | It's down for me too. I'm assuming it's your Travis builds failing | like mine are. One option that occurs to me is to convert | ObjectsAsMethodsWrapper to filetree and store a copy on GitHub? | GitHub | have rather more resources to through at availability than we do, so | we might as well take advantage. | | frank | |