On Fri, Jun 11, 2010 at 1:53 PM, Torsten Bergmann <astares@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?
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 http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project