[Seaside] Loading stable version broken?
johan at inceptive.be
Thu Mar 20 16:03:32 UTC 2014
I just sent this on the Pharo mailinglist:
I can reproduce the problem.
For some strange reason, first Grease 1.1.5 is loaded and then 1.1.6 is loaded (in the same metacello load of VoyageMongo).
The package becomes dirty because some classes changed from the Pharo20 package in 1.1.5 to the Core package in 1.1.6.
Because Metacello first loads the Core package, the Pharo20 package becomes dirty. When the new version of the Pharo20 package is loaded, Monticello raises the warning.
I have noticed a similar issue when upgrading versions of Zinc in Pharo1.4 because significant package refactorings occurred.
So, this is nothing specific to Grease / Magritte / Seaside / ...
I wonder if this can be simply fixed by changing the load type to #atomic. At least, that is how I fix those issues when loading Yesplan in Gemstone.
But clean builds work perfectly. And I would want to know why first version 1.1.5 is loaded in this load process.
On 20 Mar 2014, at 16:27, Johan Brichau <johan at inceptive.be> wrote:
> Have you tried throwing away your package cache?
> I am suspicious about something.... because I cannot reproduce this and a bunch of people are reporting problems.
> On 20 Mar 2014, at 16:01, Sebastian Sastre <sebastian at flowingconcept.com> wrote:
>> Hi there,
>> I’m loading with:
>> Gofer new
>> package: 'ConfigurationOfSeaside3';
>> ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load.
>> ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load: #('Kom' 'Scriptaculous' 'Email’).
>> And since yesterday my builds started to fail due to a warning about load or merge question
>> What’s the advice?
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
More information about the seaside