On Thu, Dec 10, 2015 at 6:01 PM, Levente Uzonyi <leves at caesar.elte.hu>
wrote:

> IMHO all you need to do is to fire up a Squeak image which has
> Squeak-Version-kfr.4713 loaded, open update-mt.339.mcm (open the Trunk
> repository, select this update map, and click Browse), remove
> Universes-mt.48 from the list (select, right click, remove), and update
> Squeak-Version to kfr.4713 (select, right click, update from image (or
> repository if you're brave), and finally save it (Store) using the same
> name (update-mt.339).
>

I tried this, but there is no stored file from the
MCConfigurationBrowser... I'm not sure what is going on, why it is not
outputting a update file to my local repository.

I also updated from a Squeak 5.0 image and I did not run into any problems
with the update...


Best,
Karl



> Here comes the tricky part: you can't overwrite an existing update map,
> nor can you move it away from the repository using the web interface, so an
> administrator of source.squeak.org will have to do one of these things to
> let you save the correct version.
> Alternatively, you could try to save it using different initials but same
> version (e.g. update-kfr.339) and hope that the update process will sort
> the maps lexicographically, but I'd rather not rely on this.
>
> Levente
>
> On Thu, 10 Dec 2015, karl ramberg wrote:
>
> Thanks,
>> Best,
>> Karl
>>
>> On Thu, Dec 10, 2015 at 5:00 PM, Eliot Miranda <eliot.miranda at gmail.com>
>> wrote:
>>       Hi Karl,
>>       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
>>
>>
>> As Chris says the updates live in the "update" package.  Open up a
>> repository browser on source.squeak.org/trunk and you'll see them
>> towards the bottom (update.spur contains older updates from the time of the
>> bootstrap from 4.6 to what became 5.0, you can ignore
>> them).
>>
>> What I would do is create a local mirror, either by fully populating my
>> package cache with all the 5.0 packages and updates, or creating a
>> directory repository and downloading all the packages and updates to there
>> and then play with the local repository until I
>> got the update working again, and then I would upload the changed updates
>> to trunk.
>>
>> I'm attaching SpurBootstrapMonticelloPackagePatcher which is the hack I
>> used to automate patching 4.6 packages to make them Spur compatible in the
>> run-up to 5.0.  I'm doing this because it contains methods like
>> downloadToSourceDirAllPackageVersionsStartingWith:
>> that download all versions of a package to a local repository starting
>> from a specific version.  Sao these hacks will help you in populating your
>> local repository prior to experimenting. Once I'd downloaded all packages I
>> would then take a local copy and modify
>> the copy, I could then diff the original and the modified clone to see
>> what had changed.
>>
>> HTH
>>
>>  _,,,^..^,,,_
>> best, Eliot
>>
>>       Best,
>> Karl
>> [cleardot.gif]
>>
>> 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/98d355d1/attachment.htm