Okay, I found the culprit: Glorp.

If you execute this, it will load a class named Cache, which will overwrite Pharo's version. As happened with the referenced issue.

Gofer it�
url: 'http://smalltalkhub.com/mc/DBXTalk/Glorp/main';
package: 'Glorp';
load.

No one ever tried loading Glorp into a Pharo3 image? What do people use for ORM?

Regards!


Esteban A. Maringolo


2014-04-08 17:00 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
https://pharo.fogbugz.com/f/cases/12667

It was BabyMock-Examples.

HTH,

Sven

On 08 Apr 2014, at 21:59, Sven Van Caekenberghe <sven@stfx.eu> wrote:

> What are you loading ? There was a report back of some package overwriting system code leading to this error, I'll see if I can find it.
>
> On 08 Apr 2014, at 21:05, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
>
>> I'm trying to load a Metacello Configuration I use in Pharo 2 into a brand new Pharo 3 image.
>>
>> However I'm getting an error when attempting to load it, and it opens the emergency evaluator.
>>
>