Hi Eliot,
this remind me recent problems when we wanted to upgrade the
SystemProgressMorph itself

http://lists.squeakfoundation.org/pipermail/squeak-dev/2016-August/191722.html

I didn't look at the problem, but maybe an option is tp detach the Context*
classes from the SystemDictionary in some preamble so that they are immune
to any refactoring while still in use...

Nicolas

2017-03-31 4:32 GMT+02:00 Eliot Miranda <eliot.miranda at gmail.com>:

> Hi All,
>
>     I'm very sorry to report that my recent changes (adding CompiledCode
> and CompiledBlock to the CompiledMethod hierarchy in anticipation of full
> blocks, and merging ContextPart and MethodContext and renaming them as
> Context, to eliminate obsolete block and closer implementations) has broken
> the update process.  I do not believe there is an easy fix as i think the
> issues are to do with the citations that exist on the stack while the
> update proceeds (the progress indicators).
>
> There is a clumsy work-around that appears reliable.  The pauses between
> loads get rid of the progress indication activations and hence avoid trying
> to upgrade running processes through these kernel changes.
>
> Open the trunk repository from your Monticello Browser.
> Locate the update package (the penultimate entry in the list of packages).
> Load (or merge) update-eem.400.mcm.
> Load (or merge) update-eem.403.mcm.
> Load (or merge) update-eem.406.mcm. Save your image.
> Local the Kernel package.
> Load Kernel-eem.1078. Save your image.
> Update
>
> I'm so sorry.
> Eliot
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170331/b47f2f66/attachment.html>