Thanks

Best,
Karl

On Thu, Dec 10, 2015 at 4:36 PM, Chris Cunningham <cunningham.cb at gmail.com>
wrote:

> Hi Karl,
> I think to update the update map, open up trunk, go down and find the
> package called 'update', browse that. It should bring up an
> MCConfigurationBrowser. The order of the packages in that browser is the
> order that an update will try to upgrade the packages - and is the list of
> packages that the upgrade stream will upgrade.
>
> I think you'll want to remove from that list the packages that were
> removed in the SqueakVersion, and then save the configuration back to trunk.
>
> When you are doing tricky things, you can specify exactly which versions
> of packages should load in an update - and stack them one after the other -
> so that the update will load specific packages in a specific order.
> Probably not needed for this fix, though, right?
>
> All of this said, I don't actually have access to do this or test it, so
> take the info as you will.
>
> Good luck,
> cbc
>
> On Wed, Dec 9, 2015 at 9:27 PM, karl ramberg <karlramberg at gmail.com>
> wrote:
>
>> Hi,
>> It it related with this Levente mentioned in a mail earlier ?
>>
>> "Sadly the update process will break if your image has Universes-mt.48 in
>> it, because it'll try to load Universes-kfr.49 after it has been removed by
>> Squeak-Version. I think removing Universes from the update map will
>> help."
>>
>> I asked how to proceed but I got no answer.
>> I'm not sure how one make a update map
>>
>>
>> Best,
>> Karl
>>
>> On Thu, Dec 10, 2015 at 4:06 AM, Eliot Miranda <eliot.miranda at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>>     whatever happened in unloading Universes, it broke the ability to
>>> update a release Squeak 5.0 image to the current tip.  Hence my automated
>>> scripts to build 64-bit images are broken.  Can whoever broke the update
>>> either fix it, or provide some reasonable workaround so that I can restore
>>> my scripts?  What's at stake here is, well, a high performance 64-bit
>>> Squeak and/or Pharo.
>>>
>>> I think it's reasonable, even mandatory that we should be able to update
>>> a release N image to the tip of release N.  We should have CI servers that
>>> try and do this (I think we do, don't we?), and so IMO it's incumbent on
>>> whoever breaks the update to fix things, e.g. by changing update maps
>>> appropriately.  [and I don't mean this as a punishment, or something that
>>> the person has to do on their own; I'm happy to help fix things, it's
>>> /really/ important that the update works, and not just from the last
>>> update].
>>>
>>> Thanks in advance.  Apologies if I appear rude; it's not my intent.  I
>>> just want my auto-update back ;-)
>>>
>>> On Thu, Nov 26, 2015 at 2:55 PM, <commits at source.squeak.org> wrote:
>>>
>>>> Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24
>>>> hours:
>>>>
>>>>
>>>> http://lists.squeakfoundation.org/pipermail/packages/2015-November/009199.html
>>>>
>>>> Name: Squeak-Version-kfr.4713
>>>> Ancestors: Squeak-Version-kfr.4712
>>>>
>>>> Unload and unregister Universes
>>>>
>>>> =============================================
>>>>
>>>
>>> _,,,^..^,,,_
>>> best, Eliot
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20151210/3f0d64a0/attachment-0001.htm