With each release I do copy the mcz files (source and configs) to http://www.squeaksource.com/metacello, however, at the moment it takes manual intervention to load using the alternate repository. I will spend some time looking at the problem and see if I can make the switchover to the alternate repository more automatic for Metacello itself...
As for the outage itself, we lost a critical machine in our data center and service was restored shortly after 7 am PST.
While talking to our IT folks I found out that now that we have joined VMWare, our GemStone data center will be moved to a VMWare data center which will be an upgrade over out current hardware, so we shouldn't see another outage like this for our server.
Dale Mariano Martinez Peck wrote:
On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <asta...@gmx.de<mailto:asta...@gmx.de>> wrote: http://seaside.gemstone.com/ss/metacello/ is down, therefore ConfigurationOfPharo can not be used to build Pharo 1.1. from an updated core. See http://downforeveryoneorjustme.com/seaside.gemstone.com Maybe the machine is switched to vmware.com<http://vmware.com>? However - we should again think about reliable infrastructure ... Once I remeber Dale though about having the code in both repositories: squeaksource and gemstone. And when doing ensureMetacello, checks first in gemstone. If it fails, it tries in squeaksource...at least that was the idea...I don't know if it was implemented or not. Cheers mariano Thx T. -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
