Hm, it seems to only happen with the 4.0.3-2202 which I compiled
myself.  I tried the downloaded 4.0.3-2202 and it works.  Sorry for
the false alarm.

Thanks..

On Sun, Jan 2, 2011 at 11:15 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Sun, Jan 02, 2011 at 09:04:16PM -0600, Chris Muller wrote:
>> I cannot upgrade a 10779 image using a 2202 Linux VM, however, I can
>> using a Cog VM.
>>
>
> Hi Chris,
>
> I just tried downloading the 10779 image from ftp.squeak.org and
> ran in on the 4.0.3-2202 VM on Linux, then did an "update code from
> server" without problems. What is the problem that are you seeing?
>
>> The possible outcomes for the 4.2 release are:
>>
>>   a) We release the 10779 image as 4.2.  None of the recent updates
>> would be included.
>>   b) We release the 10847 image as 4.2 saved under a Cog VM.  It would
>> not be able to be launched by the interpreter or older VM's.
>
> Regardless of the version we freeze at, the final release image
> should be saved from a standard VM, not from a Cog VM. I can help
> with this if the updated standard VM has not released when you need
> to take this step.
>
> Dave
>
>>   c) Debug it.
>>
>> Debugging might be difficult since the system is upgrading itself.
>> Certainly it would be impressive..
>
>
>
>
>