[Glass] SIXX load conflict
Dale Henrichs via Glass
glass at lists.gemtalksystems.com
Thu Dec 18 10:08:29 PST 2014
Mariano is correct that `onLock: [:ex | ex honor];` will eliminate the
Warning, but I am suspicious that you are not running a recent version
of GLASS.
You are getting a Warning during a topaz load (I assume ... in GemTools
you would get a Warning dialog). There was a bug[1], where the wrong
default action for a Warning was triggered during non-interactive loads
and the bug was fixed back in June.
So I think you should upgrade GLASS1:
Gofer new
package: 'GsUpgrader-Core';
url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
load.
(Smalltalk at: #GsUpgrader) upgradeGLASS1.
Finally, when loading from within topaz, you should always use
GsDeployer class>>bulkMigrate::
GsDeployer bulkMigrate: [
Metacello new
baseline: 'SIXX';
repository: 'github://glassdb/SIXX:master/repository';
load ].
GsDeployer class>>bulkMigrate: wraps your code with an autoCommit
handler, a Warning handler, and instance migrations are deferred until
all of the loading is complete and then migrations are done with one
pass of the db...
Actually, it is not a bad idea to always use GsDeployer whether or not
you are loading in topaz:)
Dale
[1] https://github.com/GsDevKit/GsDevKit/issues/21
On 12/18/2014 04:24 AM, Mariano Martinez Peck via Glass wrote:
>
> On Thu, Dec 18, 2014 at 8:10 AM, Dario Trussardi via Glass
> <glass at lists.gemtalksystems.com
> <mailto:glass at lists.gemtalksystems.com>> wrote:
>
> I load SIXX support into GLASS 3.1.0.6 with the command:
>
> Metacello new
> baseline: 'SIXX';
> repository: 'github://glassdb/SIXX:master/repository';
> load.
>
> The system answer :
>
> a Halt occurred (error 2709), Debugging: Warning: LOCK ENFORCED:
> Attempt to 'load with conflicts' new project:
> 'ConfigurationOfGrease 1.0.3 from
> http://www.squeaksource.com/MetacelloRepository' when existing
> project: 'BaselineOfGrease [baseline] from
> github://GsDevKit/Grease:master/repository' is locked. New project
> not loaded. Use #onLock: to intercept. - G/S[Scandella3106:2]
>
>
> I think I had the same issues.
>
> The most robust way I found to load code is the following. For your
> concrete problem, I think the key line is " onLock: [:ex | ex honor];"
> but maybe you want to adapt all that code:
>
> [ [ [ [
>
>
> Metacello image
> configuration: 'XXX';
> version: YYY;
> onLock: [:ex | ex honor];
> load: #(ZZZ).
>
> ]
> on: MetacelloAllowConflictingProjectUpgrade
> do: [ :ex | ex defaultAction ] ]
> on: MetacelloAllowLockedProjectChange
> do: [ :ex | ex disallow ] ]
> on: MetacelloNameNotDefinedError
> do: [ :ex | ex resume ]]
> on: Warning
> do: [ :ex | ex resume ].
>
> The only discussion here is to resume upon all warning. This may not
> be good for all cases. Sometimes the warnings are important.
> I think I will remove that from mine....
>
> Best,
>
>
> I do some proced commands.
>
> At he end the system answer:
>
> linear load :
> linear load : baseline [BaselineOfSIXX]
> linear load : 1.1.8 [ConfigurationOfXMLSupport]
> linear load : baseline [BaselineOfGrease]
> atomic load : 0.243
> [ConfigurationOfGsMisc]
> linear load : 1.1.8
> [ConfigurationOfXMLSupport]
> load : SIXX.310-dkh.183
>
>
> I can consider correct the loading?
>
>
> Thanks,
>
> Dario
>
> P.S. The GLASS 3.1.06 is create with development kit
> createTodeStone command
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com <mailto:Glass at lists.gemtalksystems.com>
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
>
> _______________________________________________
> 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/20141218/7cb7730d/attachment-0001.html>
More information about the Glass
mailing list