On 4/5/17, Levente Uzonyi <leves at caesar.elte.hu> wrote:
> It's because you have to update your image till 399.mcm first. I presume
> you just skipped that and loaded 400.mcm right into that image.

Thank you, Levent. And how to I update 17086 to 399.mcm only?

The screen shot shows the situation *not* doing this before loading 400.mcm

--Hannes

> Levente
>
> On Wed, 5 Apr 2017, H. Hirzel wrote:
>
>> *Not* easy.
>>
>> You were lucky applying the instructions.
>>
>> The first time I did it I had a walkback.
>>
>> The second time starting with
>> http://files.squeak.org/6.0alpha/Squeak6.0alpha-17086-32bit/
>> the process stalls while applying 'Installing Kernel-eem.1083'.
>>
>> On 4/5/17, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>> On Wed, Apr 5, 2017 at 4:55 PM, H. Hirzel <hannes.hirzel at gmail.com>
>>> wrote:
>>>
>>>> It seems that some people have managed to work around the issues of
>>>> the broken update and now have an updated image.
>>>>
>>>> Is it possible such  a fully updated image and changes file for the
>>>> meantime in
>>>> http://files.squeak.org/6.0alpha/ ?
>>>
>>>
>>> No. It's easy enough to follow Eliots instructions to get past the bump,
>>> but let's fix it properly. We can't leave the update stream broken.
>>>
>>> - Bert -
>>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Squeak6.0a_17086_updateing_Screenshot_2017-04-05.png
Type: image/png
Size: 246482 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170405/76701ae7/attachment-0001.png>