23 Jan
2015
23 Jan
'15
12:34 a.m.
The loadStable is supposed to work in Pharo3. Development might only
work with Pharo 4,
which is mostly perfectly fine and sometimes undergoing major surgery.
If you ever find yourself having to fix these issues, this is where I
would start:
- download the latest green builds of moose5.1 and 5.0 to see if the
problems are there too.
- take a look at the configuration of the ci build of moose to see what
is supposed to happen.
- try to do a loadStable and check the package cache for multiple
versions of the same
package.
- compare the current ConfigurationOfMoose (364) with that at release
and look at the
different package versions (Moose-Finder 515 vs 516, PetitJava 158 vs
160)
- take a look at the configurations of the dependencies to see which
ones changed their stable
since the moose50 release (2014-12-23)
That is at top-level:
spec
project: 'Metanool' with: #stable;
project: 'Fame' with: #stable;
project: 'RoelTyper' with: #stable;
project: 'MooseAlgos' with: #stable;
project: 'PetitParser' with: #stable;
project: 'SmallDude for Moose' with: #stable;
project: 'PetitSQL' with: #stable;
project: 'Glamour' with: #stable;
project: 'Roassal2' with: #stable;
project: 'XMLParser' with: #stable;
project: 'Pastell' with: #stable;
project: 'Merlin' with: #stable;
project: 'GToolkit' with: #stable;
project: 'OSProcess' with: #stable.
Of those, Glamour changed: 197 -> 202, Roassal2 15 -> 25,
XMLParser 102 -> 109, GToolkit 64 -> 69
I'm happy to see that fixing the #stable definition
in ConfigurationOfGlamour should be enough to make things work again.
Stephan