issues with configurationofmagritte3 on pharo 6
Locked
issues with configurationofmagritte3 on pharo 6
 
|
Hi,
I would need a bit of help with understanding why ConfigurationOfMagritte3 #stable does not load in Pharo 6 from the command line. The story is that until recently, the SmalltalkImage>>metacelloPlatformAttributes included pharo5.x and now it only correctly includes pharo6.x. This means that configurations that were defined only for pharo5.x do not work anymore in Pharo 6, as it should be. Magritte3 had this problem and now I fixed it by manually adding pharo6.x to: - ConfigurationOfMagritte3>>version351: - ConfigurationOfMagritte3>>baseline330ForPharo: When I load the code from a Playground inside the latest Pharo 6 image it works fine. I use this: Metacello new smalltalkhubUser: 'Moose' project: 'Moose'; configuration: 'Moose'; version: #development; load However, when I run what to my eyes looks like a similar script from the command line it does not work anymore: wget --quiet -O - http://get.pharo.org/60+vm | bash ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development I think I miss something obvious that I cannot see right now. Could someone help with this? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Beauty is where we see it." -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Re: issues with configurationofmagritte3 on pharo 6
|
|
Doru,
It looks like --install does not use 'Metacello new' to load the configuration. Instead it is using the old way. This roughly what the command line handler dows:: ( [(ConfigurationOfMoose version: 'development') ] on: MetacelloVersionDoesNotExistError do: [ :error | (ConfigurationOfMoose version: 'development' asSymbol)) load I didn't see a 'development' version in Moose, so the likely explanation is that when Metacello is trying to guess which version of one of the dependent projects is loaded it guesses wrong and you are off to the races down the wrong path. The new way using 'Metacello new' keeps a registry of loaded projects and Metacello knows exactly which versions of projects are loaded ... Problems like these are why I moved to the new way of loading ... Presumably the command line loader in 6.0 should start using the new way? Did you run the original 'Metacello new' in a freshly downloaded Pharo6.0? Alternate explanations would involve odd package cache monkey business, but if in both tests you started with an empty package and the same image, then it has to be that the old way of loading is letting you down ... Dale On 10/23/16 5:24 AM, Tudor Girba wrote: > Hi, > > I would need a bit of help with understanding why ConfigurationOfMagritte3 #stable does not load in Pharo 6 from the command line. > > The story is that until recently, the SmalltalkImage>>metacelloPlatformAttributes included pharo5.x and now it only correctly includes pharo6.x. This means that configurations that were defined only for pharo5.x do not work anymore in Pharo 6, as it should be. Magritte3 had this problem and now I fixed it by manually adding pharo6.x to: > - ConfigurationOfMagritte3>>version351: > - ConfigurationOfMagritte3>>baseline330ForPharo: > > When I load the code from a Playground inside the latest Pharo 6 image it works fine. I use this: > > Metacello new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration: 'Moose'; > version: #development; > load > > However, when I run what to my eyes looks like a similar script from the command line it does not work anymore: > > wget --quiet -O - http://get.pharo.org/60+vm | bash > ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development > > > I think I miss something obvious that I cannot see right now. Could someone help with this? > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Re: issues with configurationofmagritte3 on pharo 6
|
|
Hi Dale,
I forgot to follow up on this. Thanks for looking this up. I solved the problem for now by using the explicit eval command line to use Metacello new …. However, I still have a follow up problem that I cannot figure out. I can load Moose once on top of the latest Pharo 6.0. Among other things, this loads PetitParser and this in turn depends on Glamour which depends on Magritte. The problem is that I cannot seem to be able to reload PetitParser again. It says that: Name not found: Magritte-Pharo-Model It’s getting me crazy that I cannot find a way to debug this. If you have a bit of time, I could use your input. Here is how to reproduce: 1. Download: https://ci.inria.fr/moose/job/moose-6.1/310/artifact/moose-6.1.zip (Alternatively, you can load in a fresh Pharo 6.0 Metacello new smalltalkhubUser: 'Moose' project: 'Moose'; configuration: 'Moose'; version: #development; load ) 2. Execute: (ConfigurationOfPetitParser project version: #development) record And you get the error. Cheers, Doru > On Oct 23, 2016, at 5:28 PM, Dale Henrichs <[hidden email]> wrote: > > Doru, > > It looks like --install does not use 'Metacello new' to load the configuration. Instead it is using the old way. This roughly what the command line handler dows:: > > ( [(ConfigurationOfMoose version: 'development') ] > on: MetacelloVersionDoesNotExistError do: [ :error | (ConfigurationOfMoose version: 'development' asSymbol)) load > > I didn't see a 'development' version in Moose, so the likely explanation is that when Metacello is trying to guess which version of one of the dependent projects is loaded it guesses wrong and you are off to the races down the wrong path. > > The new way using 'Metacello new' keeps a registry of loaded projects and Metacello knows exactly which versions of projects are loaded ... Problems like these are why I moved to the new way of loading ... > > Presumably the command line loader in 6.0 should start using the new way? > > Did you run the original 'Metacello new' in a freshly downloaded Pharo6.0? Alternate explanations would involve odd package cache monkey business, but if in both tests you started with an empty package and the same image, then it has to be that the old way of loading is letting you down ... > > Dale > > On 10/23/16 5:24 AM, Tudor Girba wrote: >> Hi, >> >> I would need a bit of help with understanding why ConfigurationOfMagritte3 #stable does not load in Pharo 6 from the command line. >> >> The story is that until recently, the SmalltalkImage>>metacelloPlatformAttributes included pharo5.x and now it only correctly includes pharo6.x. This means that configurations that were defined only for pharo5.x do not work anymore in Pharo 6, as it should be. Magritte3 had this problem and now I fixed it by manually adding pharo6.x to: >> - ConfigurationOfMagritte3>>version351: >> - ConfigurationOfMagritte3>>baseline330ForPharo: >> >> When I load the code from a Playground inside the latest Pharo 6 image it works fine. I use this: >> >> Metacello new >> smalltalkhubUser: 'Moose' project: 'Moose'; >> configuration: 'Moose'; >> version: #development; >> load >> >> However, when I run what to my eyes looks like a similar script from the command line it does not work anymore: >> >> wget --quiet -O - http://get.pharo.org/60+vm | bash >> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development >> >> >> I think I miss something obvious that I cannot see right now. Could someone help with this? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> > > -- > You received this message because you are subscribed to the Google Groups "Metacello" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. > For more options, visit https://groups.google.com/d/optout. -- www.tudorgirba.com www.feenk.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower." -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Re: issues with configurationofmagritte3 on pharo 6
|
|
On 11/7/16 3:27 AM, Tudor Girba wrote: > Hi Dale, > > I forgot to follow up on this. > > Thanks for looking this up. I solved the problem for now by using the explicit eval command line to use Metacello new …. > > However, I still have a follow up problem that I cannot figure out. > > I can load Moose once on top of the latest Pharo 6.0. Among other things, this loads PetitParser and this in turn depends on Glamour which depends on Magritte. The problem is that I cannot seem to be able to reload PetitParser again. It says that: > Name not found: Magritte-Pharo-Model > > It’s getting me crazy that I cannot find a way to debug this. If you have a bit of time, I could use your input. Here is how to reproduce: > > 1. Download: > https://ci.inria.fr/moose/job/moose-6.1/310/artifact/moose-6.1.zip > (Alternatively, you can load in a fresh Pharo 6.0 > Metacello new > smalltalkhubUser: 'Moose' project: 'Moose'; > configuration: 'Moose'; > version: #development; > load > ) > 2. Execute: > (ConfigurationOfPetitParser project version: #development) record the old Metacello api .. the new way of doing this would be: Metacello image configuration: 'PetitParser'; version: #development; record You might need to use new and a repository: in the above ... the above should work if you've already got PetitParser loaded in your image ... Dale -- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Re: issues with configurationofmagritte3 on pharo 6
|
|
Record? Le 7 nov. 2016 12:28, "Dale Henrichs" <[hidden email]> a écrit :
You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Re: issues with configurationofmagritte3 on pharo 6
|
|
Sorry for the late reply ..
#record returns the load directives (used to do the load) allowing one to see what would be loaded without doing the load ... Dale On 11/07/2016 05:41 AM,
[hidden email] wrote:
-- You received this message because you are subscribed to the Google Groups "Metacello" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
«
Return to Metacello
|
1 view|%1 views
| Free forum by Nabble | Edit this page |