Latest Voyage for Pharo4

> Hi Dale,
>
> At first I was more thinking of a problem in the dependencies of Voyage,
> but then it seems not as with unload Seaside, Voyage get load. It did
> not help anyway becasue Seaside can't be reinstalled (Obsolete class
> syndrom hit there)
>
> Voyage is installed as:
>
> "VoyageMongo EstebanLorenzano.47"
> ConfigurationOfVoyageMongo load
>
> The transcript output in the attached document
>
> Thanks
>
> Le 17/02/2017 à 18:54, Dale Henrichs a écrit :
>> You don't mention how you are loading Voyage. If I had the load
>> expression and Transcript output from the load, I'd pretty much be able
>> to tell pretty much what is going on.
>>
>> I have a couple of theories about what could be going wrong, but without
>> the load expression and Transcript output, I'd only be guessing and of
>> course there is the possibility that you've discovered a bug in Metacello:)
>>
>> If you'd like to get to the bottom of this, send me the load expression
>> and Transcript output and we'll go from there ...
>>

> Hi Dale,
>
> Thanks for your detailed suggestions. I follow instructions, here the
> report bellow.
>
> Installed newest Metacello, then Voyage with new style:
>
> Metacello new
>    baseline: 'Metacello';
>    repository: 'github://dalehenrich/metacello-work:master/repository';
>    get.
> Metacello new
>    baseline: 'Metacello';
>    repository: 'github://dalehenrich/metacello-work:master/repository';
>    onConflict: [:ex | ex allow];
>    load.
>
> "Fetch from voyage repo at github"
> Metacello new
>      repository: 'github://pharo-nosql/voyage/mc';
>      baseline: 'Voyage';
>      load: 'mongo tests'.
>
> It still have the same error, do an upgrade of Seaside.
> Enclosed is the transcript for both Metacello and Voyage install.
>
> Seaside installed was 3.1.x. I don't know the x digit, it is not
> documented in an obvious way :(
>
> Hope it helps
>
> Thanks
>
> Hilaire
>

> Dale,
>
> May be you don't want to waste anymore time on that. Thanks for your
> effort. I got a way to get Voyage installed in my development image.
>
> Not sure what wrong, because something is wrong[1], but I got the things
> installed, first update to Seaside, which break when upgrading  the
> Seaside installed from the configuration browser, fix the seaside broken
> installation, then install Voyage which went fine. Did not test Voyage
> is working though.
>
> Hilaire
>
> [1]The Pharo4 configuration browser's Magritte3 is installing Seaside
> update, this should NOT happen.
> Now image comes with a Configuration Browser, if I understand correctly
> its intend, an user is expected those configurations to work happily
> together, but it looks like not, some configurations will request update
> breaking package previously installed from this configuration browser.
> May be it is more a policy problem on the quality of the configuration
> than a tool problem, a lot can be learn from Debian packaging. For
> example Debian stable is released only when quality is ok, don't know
> the details but they don't like to rush for release and people complain
> new stable release take too much time to emerge, the price for quality?
> For me Pharo fells too fuzzy, and it makes me very sceptical for
> reliability; may be not nice to write and to read but it is how I fell.
> I may be biased and I don't mean bad to anyone writing this, I know how
> quality is hard to achieve and Pharo teams did great endeavour in many
> aspects.
>
>
>
>
> Le 17/02/2017 à 22:15, Dale Henrichs a écrit :
>> Again, thanks for detailed info ...
>>
>> The fact that you loaded Seaside3.1.x  is good enough for my purposes
>> .. the fact that Seaside3.2 is getting installed implies that there is a
>> hard dependency on Seaside in one of the projects (Magritte3 perhaps?)
>> ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around
>> --- Can you get the package version of ConfigurationOfSeaside3 that's in
>> the image after the `Metacello new` loads?... I'll have to dive into the
>> configurations now ...
>

> Hilaire
>
> [1]The Pharo4 configuration browser's Magritte3 is installing Seaside
> update, this should NOT happen.
> Now image comes with a Configuration Browser, if I understand correctly
> its intend, an user is expected those configurations to work happily
> together, but it looks like not, some configurations will request update
> breaking package previously installed from this configuration browser.
> May be it is more a policy problem on the quality of the configuration
> than a tool problem, a lot can be learn from Debian packaging. For
> example Debian stable is released only when quality is ok, don't know
> the details but they don't like to rush for release and people complain
> new stable release take too much time to emerge, the price for quality?
> For me Pharo fells too fuzzy, and it makes me very sceptical for
> reliability; may be not nice to write and to read but it is how I fell.
> I may be biased and I don't mean bad to anyone writing this, I know how
> quality is hard to achieve and Pharo teams did great endeavour in many
> aspects.
>
>
>
>
> Le 17/02/2017 à 22:15, Dale Henrichs a écrit :
>> Again, thanks for detailed info ...
>>
>> The fact that you loaded Seaside3.1.x  is good enough for my purposes
>> .. the fact that Seaside3.2 is getting installed implies that there is a
>> hard dependency on Seaside in one of the projects (Magritte3 perhaps?)
>> ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around
>> --- Can you get the package version of ConfigurationOfSeaside3 that's in
>> the image after the `Metacello new` loads?... I'll have to dive into the
>> configurations now ...

> Dale,
>
> May be you don't want to waste anymore time on that. Thanks for your
> effort. I got a way to get Voyage installed in my development image.
>
> Not sure what wrong, because something is wrong[1], but I got the things
> installed, first update to Seaside, which break when upgrading  the
> Seaside installed from the configuration browser, fix the seaside broken
> installation, then install Voyage which went fine. Did not test Voyage
> is working though.
>
> Hilaire
>
> [1]The Pharo4 configuration browser's Magritte3 is installing Seaside
> update, this should NOT happen.
> Now image comes with a Configuration Browser, if I understand correctly
> its intend, an user is expected those configurations to work happily
> together, but it looks like not, some configurations will request update
> breaking package previously installed from this configuration browser.
> May be it is more a policy problem on the quality of the configuration
> than a tool problem, a lot can be learn from Debian packaging. For
> example Debian stable is released only when quality is ok, don't know
> the details but they don't like to rush for release and people complain
> new stable release take too much time to emerge, the price for quality?
> For me Pharo fells too fuzzy, and it makes me very sceptical for
> reliability; may be not nice to write and to read but it is how I fell.
> I may be biased and I don't mean bad to anyone writing this, I know how
> quality is hard to achieve and Pharo teams did great endeavour in many
> aspects.
>
>
>
>
> Le 17/02/2017 à 22:15, Dale Henrichs a écrit :
>> Again, thanks for detailed info ...
>>
>> The fact that you loaded Seaside3.1.x  is good enough for my purposes
>> .. the fact that Seaside3.2 is getting installed implies that there is a
>> hard dependency on Seaside in one of the projects (Magritte3 perhaps?)
>> ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around
>> --- Can you get the package version of ConfigurationOfSeaside3 that's in
>> the image after the `Metacello new` loads?... I'll have to dive into the
>> configurations now ...

> Hilaire,
>
> I mentioned last night that I thought that there was a better solution
> to your problem and I think that if you load the latest Metacello and
> then lock Seaside3:
>
>   Metacello image
>     configuration: 'Seaside3';
>     version: '3.1.5'; "most recent 3.1.x version"
>     lock.
>
> Then load Voyage, you shouldn't have the problem with Seaside being
> updated to 3.2.

> I mentioned last night that I thought that there was a better solution
> to your problem and I think that if you load the latest Metacello and
> then lock Seaside3:
>
>   Metacello image
>     configuration: 'Seaside3';
>     version: '3.1.5'; "most recent 3.1.x version"
>     lock.
>
> Then load Voyage, you shouldn't have the problem with Seaside being
> updated to 3.2. Seaside does not support upgrade across minor version
> numbers like 3.1 to 3.2 ... if the upgrade to 3.2 was allowed, you
> wouldn't have this particular problem.

> On 19/02/17 18:50, Dale Henrichs wrote:
>> Hilaire,
>>
>> I mentioned last night that I thought that there was a better solution
>> to your problem and I think that if you load the latest Metacello and
>> then lock Seaside3:
>>
>>   Metacello image
>>     configuration: 'Seaside3';
>>     version: '3.1.5'; "most recent 3.1.x version"
>>     lock.
>>
>> Then load Voyage, you shouldn't have the problem with Seaside being
>> updated to 3.2.
>
> Voyage needs a newer Grease, is that backwards compatible (I forgot)?
>

>
> I updated this image with latest Metacello, then I locked it as:
>
>    Metacello image
>      configuration: 'Seaside3';
>      version: '3.1.4.2'; "most recent 3.1.x version"
>      lock.
>
> It was the version returned by this command:
> ConfigurationOfSeaside3 new project currentVersion
>
> By the way it will make sense, and will be easily discoverable to have a
> short cut as "ConfigurationOfSeaside3 currentVersion"