[Glass] [ANN] GsUpgrader

Fri Sep 19 15:00:36 PDT 2014

Hi Dale,

I tried to follow the upgrade metacello step, but it gave me an error

--transcript--'=====Upgrading Metacello'
--transcript--'...RETRY->BaselineOfMetacello'
--transcript--'...RETRY->BaselineOfMetacello'
--transcript--'gofer repository error: ''a GoferRepositoryError occurred
(error 2710)''...ignoring'
--transcript--'...FAILED->BaselineOfMetacello'
ERROR 2710 , a MetacelloPackageSpecResolutionError occurred (error 2710)
(MetacelloPackageSpecResolutionError)

... This was run from a topaz session

no problems with re-starting from scratch if i have messed something up at
the low level.

On Fri, Sep 19, 2014 at 2:10 PM, Dale Henrichs via Glass <
glass at lists.gemtalksystems.com> wrote:

> Okay ... submitted GsUpgrader issue[1] for tracking ... I should take care
> of this puppy shortly ...
>
> Dale
>
> [1] https://github.com/GsDevKit/gsUpgrader/issues/3
>
> On Fri, Sep 19, 2014 at 1:33 PM, Johan Brichau <johan at yesplan.be> wrote:
>
>> That’s pretty much what I was thinking :)
>>
>> Loading a newer version of Grease should not be a problem. I’m going to
>> check the delta from 1.0.x to 1.1.x to make sure.
>>
>> In the meantime, I removed the Grease project registration from the
>> registry before doing the upgradeGLASS1 to make Metacello pass through with
>> the load.
>>
>> Johan
>>
>> On 19 Sep 2014, at 21:34, Dale Henrichs <dale.henrichs at gemtalksystems.com>
>> wrote:
>>
>> Good catch ... I think:)
>>
>> You are right, GsUpgrader shouldn't be hitting conflicts for Grease...
>>
>> My inclination is to fix this and "force" the github-base Grease to be
>> loaded (unless the Grease project is locked, in which case the lock wins),
>> since the bugfixes there will always be more current ...
>>
>> What do you think?
>>
>> Dale
>>
>>
>> On Fri, Sep 19, 2014 at 12:12 PM, Johan Brichau <johan at yesplan.be> wrote:
>>
>>> Hi Dale,
>>>
>>> I’m currently applying the upgradeGLASS1 on a 3.1 stone running
>>> Seaside30 where I am upgrading to Zinc 2.4.3, which relies on GLASS.
>>> I’m getting a load conflict for Grease because I have the one loaded
>>> from Smalltalkhub.
>>>
>>> ERROR 2710 , a MetacelloConflictingProjectError occurred (error 2710),
>>> Load Conflict between existing ConfigurationOfGrease 1.0.9 from
>>> http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main and
>>> BaselineOfGrease [baseline] from
>>> github://GsDevKit/Grease:master/repository
>>>  (MetacelloConflictingProjectError)
>>>
>>> Is this not something we can safely allow? Grease is going to be loaded
>>> from smalltalkhub or gemsource in many cases.
>>>
>>> Johan
>>>
>>> On 16 Sep 2014, at 19:17, Dale Henrichs via Glass <
>>> glass at lists.gemtalksystems.com> wrote:
>>>
>>> With the move of more and more GsDevKit projects to github, the process
>>> of upgrading to the proper version of GLASS and Metacello has gotten fairly
>>> complicated:
>>>
>>>   - Upgrade to GLASS1.0-beta.9.3 (unless you have already upgrading to
>>> GLASS1)
>>>   - Upgrade to the latest version of Metacello (load preview unless you
>>> have already loaded a baseline)
>>>   - Upgrade to the latest version of GLASS1
>>>
>>> I am also still adding features and bugfixes to Metacello to improve the
>>> support of git/github projects, and unfortunately it is not always possible
>>> to use Metacello to install an upgrade of Metacello itself.
>>>
>>> I created the gsUpgrader[1] project to simplify the upgrade process for
>>> the github-based projects. GsUpgrader is a single class with four entry
>>> points:
>>>
>>>   - upgradeGLASS[3]
>>>   - upgradeGLASS1[4]
>>>   - upgradeGrease[5]
>>>   - upgradeMetacello[6]
>>>
>>> A fifth entry point: #metacelloReport produces a project/package version
>>> report that is useful to help debug upgrade issues ... I've tested
>>> GsUpgrader in a number of scenarios[7], but there always seem to be special
>>> cases that sneak through the cracks.
>>>
>>> The class is loaded from a package using the following expression:
>>>
>>>   Gofer new
>>>     package: 'GsUpgrader-Core';
>>>     url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>>>     load.
>>>
>>> A simple package is used so that the GsUpgrader class can be used to
>>> upgrade GemStone installations as old as GemStone 2.4.4.1[2] (the first
>>> GemStone version that officially supported GLASS).
>>>
>>> I will start updating the installation instructions for the various
>>> github-based projects to use GsUpgrader.
>>>
>>> I would recommend that all of you use GsUpgrader to upgrade to the
>>> latest version of Metacello using the following expression:
>>>
>>>   Gofer new
>>>     package: 'GsUpgrader-Core';
>>>     url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>>>     load.
>>>   (Smalltalk at: #GsUpgrader) upgradeMetacello.
>>>
>>> Having an up-to-date version of Metacello is probably the most important
>>> thing at this juncture and it is always a good idea to upgrade Metacello
>>> before upgading any other github-based projects.
>>>
>>> Dale
>>>
>>> [1] https://github.com/GsDevKit/gsUpgrader#gsupgrader-
>>> [2]
>>> http://gemstonesoup.wordpress.com/2010/07/15/gemstones-64-version-2-4-4-1-is-shipping/
>>> [3] https://github.com/GsDevKit/gsUpgrader#gsupgrader-classupgradeglass
>>> [4] https://github.com/GsDevKit/gsUpgrader#gsupgrader-classupgradeglass1
>>> [5] https://github.com/GsDevKit/gsUpgrader#gsupgrader-classupgradegrease
>>> [6]
>>> https://github.com/GsDevKit/gsUpgrader#gsupgrader-classupgrademetacello
>>> [7] https://travis-ci.org/GsDevKit/gsUpgrader/builds/35386940
>>>
>>> _______________________________________________
>>> Glass mailing list
>>> Glass at lists.gemtalksystems.com
>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>
>>>
>>>
>>
>>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140919/4ff1d96c/attachment-0001.html>