Broken trunk update and workaround

> On 4/5/17, Levente Uzonyi <[hidden email]> 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 <[hidden email]> wrote:
>>>> On Wed, Apr 5, 2017 at 4:55 PM, H. Hirzel <[hidden email]>
>>>> 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 -
>>>>
>>
>>
>

> I started again with a pristine image again from
> http://files.squeak.org/6.0alpha/Squeak6.0alpha-17086-32bit/
>
> By reading
>     Update stream
>     http://wiki.squeak.org/squeak/3154
>
> I was directed to class MCMcmUpdater
>
> After having a look at the code of this class I did
>
>     MCMcmUpdater default lastUpdateMap
>
> and got
>
> a Dictionary('http://source.squeak.org/trunk'->402 )
>
> Which is more than the 399 you recommend and the 400 Eliot recommends
> to start with. [1]
>
> Do I need to start with an earlier version? If yes, which one?
>
> --Hannes
>
>
>
> [1] Instructions by Eliot M. to do the manual update
> http://forum.world.st/Broken-trunk-update-and-workaround-td4940633.html
> (= the start of this thread)
>
> 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
>
>
>
> On 4/5/17, H. Hirzel <[hidden email]> wrote:
>> On 4/5/17, Levente Uzonyi <[hidden email]> 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 <[hidden email]> wrote:
>>>>> On Wed, Apr 5, 2017 at 4:55 PM, H. Hirzel <[hidden email]>
>>>>> 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 -
>>>>>
>>>
>>>
>>

> On Wed, Apr 5, 2017 at 3:49 AM, David T. Lewis <[hidden email]> wrote:
>
> >
> > > Personally I like the idea of only updating progress while downloading
> > > files, and then during installation updating progress only between
> > package
> > > installs.
> >
> > Sounds good to me, we just need someone to make it happen :-)
> >
>
> I tried that, see MonticelloConfigurations-bf.152 in inbox. Update still
> crashes after 406 when loading Kernel-eem.1078.
>