~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadStable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It was installing 1.52 even though the stable version of Roassal was 1.12.
Instead if I used:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gofer new smalltalkhubUser: 'ObjectProfile'
project: 'Roassal2';
package: 'ConfigurationOfRoassal2';
load.
((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I was getting the right version (1.12).
Then looking the commit numbers loaded in 1.51 I realized that it was 1.5.1, but was never fixed and fixing it solves the problem.
I was hoping to do more experiments before reporting it to the mailing list, but I was in a hurry because Roassal was being loaded incorrectly for everyone that tried to load the stable version in a Pharo4.0 image.
About the people that was relying of 1.51 and 1.52 version name, I���m deeply apologized for the troubles I may have caused, but the Roassal versions were inconsistently defined and I did not found any way to solve that cleanly. Even though I do not know how this can affect the loading of Roassal stable version now (that was 2 weeks ago) and considering that Roassal does not depends directly on Rubric.
Cheers,
Alejandro
PS: I would appreciate if someone can point a better way to handle the issue with version 1.51 and 1.52 of Roassal2 and hope nobody face any problem with it, because we have not received any complains about it (yet).