Might be but doing make in the pharo repo gives you this … Project: Hermes baseline Project: Ficus 0.3.8 ...RETRY->Hiedra ...RETRY->Hiedra gofer repository error: 'GoferRepositoryError: Could not access http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut: Cannot connect to 128.93.162.53:80'...ignoring ...FAILED->Hiedra'Errors in script loaded from /Users/norbert/play/iot/pharo/bootstrap/scripts/prepare_image.st' Could not resolve: Hiedra [Hiedra] in /Users/norbert/play/iot/pharo/pharo-local/package-cache http://smalltalkhub.com/mc/MartinDias/Ficus/main/ ERROR: ‚GoferRepositoryError: Could not access http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut: Cannot connect to 128.93.162.53:80' …
> Am 08.08.2018 um 11:21 schrieb Esteban Lorenzano <esteba...@gmail.com>: > > I was convinced that Epicea was now managed inside Pharo. > >> On 8 Aug 2018, at 11:15, Norbert Hartl <norb...@hartl.name >> <mailto:norb...@hartl.name>> wrote: >> >> The one thing is not be able to run the CI. The bigger problem is that pharo >> is not buildable at all. Can we please move mission critical repos like >> epicea to github? >> >> Norbert >> >>> Am 08.08.2018 um 09:55 schrieb Guillermo Polito <guillermopol...@gmail.com >>> <mailto:guillermopol...@gmail.com>>: >>> >>> Hi all, >>> >>> Since yesterday evening, CI is down because of Inria network problems at >>> the level of Paris. >>> Inria tells us that they do not have yet an estimation of how much time it >>> will take to fix it. >>> >>> Until then, there will be no CI testing PRs nor new builds. >>> Previous Pharo builds are still available in http://files.pharo.org/ >>> <http://files.pharo.org/>, which is hosted in OVH. >>> >>> I'll keep you updated, >>> Guille >> >
