Guillermo Polito wrote:
On Mon, Sep 4, 2017 at 1:01 PM, Herby VojÄÃk <herby@mailbox.sk <mailto:herby@mailbox.sk>> wrote:
Hello!
As I need to load specific version of Glorp with my fix, and I did not find out how to force-override it in my baseline, I tried to load it post-the-baseline via Gofer:
(Gofer new smalltalkhubUser: 'DBXTalk' project: 'Glorp') package: 'Glorp'; version: 'Glorp-HerbyVojcik.127'; load.
But it actually looks like this: [see attached bogusgofer.png].
OTOH, after the image loads the tests pass and monticello browser looks like this: [see attached mbloaded127.png].
Am I doing something wrong? I am a bit afraid what is actually loaded / if it won't break b/c of inconsistent state.
From my understanding, loading was right: - underlined in monticello means loaded - bold means not loaded - normal (not bold nor underlined) means ancestor of loaded version
So I'd say you have effectively loaded Glorp-HerbyVojcik.127 in your system.
Now, why in the progress bar somebody is loading the version 129? I'm not sure, maybe that's the metacello configuration? Or monticello needs that to calculate something with ancestors? Dunno...
Epicea item has something like "loading versions 127 and 129" in its title, so it probably means it actually loaded both (as they are the only ones being there, it seems it loaded all versions that it found). :-/ Now is it a bug in M*cello or is it me who is doing something wrong?