Moose default loads an old MorphTreeMorph???
Locked
Moose default loads an old MorphTreeMorph???
 
|
OK, I just had this problem today, not previously during the week, and I can't find the source.
When updating my Moose image I got: Loading default of ConfigurationOfMoose... <connection closed> Fetched -> Famix-ManifestMf-tg.6 --- http://www.squeaksource.com/Moose --- http://www.squeaksource.com/Moose Project: MooseAlgos for Moose default Project: PetitParser for Moose default Project: Glamour for Petit 2.0-beta.7 Fetched -> Morphic-MorphTreeWidget-AlainPlantec.88 --- http://www.squeaksource.com/Momo10 --- (....) Two strange things going on: - PetitParser default requiring Glamour for Petit 2.0-beta.7 (probably a bug when the config was copied to the Moose repo for the 4.0 release. This is now fixed) - Morphic-MorphTreeWidget-AlainPlantec.88 got fetched, I have no idea how/which project required this package which dates back to january 2010 (it's not Glamour 2.0-beta.7) Can anyone reproduce this problem, starting from a 4.1 release then updating to default? Or starting fresh and loading default? Dale, I think I have another use case for the Metacello browser, it's being able to debug such a case, by simulating/resolving which versions of a package would actually be loaded, and which project requested this version (in case there are multiple projects also, whether there was a conflict). -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Moose default loads an old MorphTreeMorph???
|
|
> Dale, I think I have another use case for the Metacello browser, it's being able to debug such a case, by simulating/resolving which versions of a package would actually be loaded, and which project requested this version (in case there are multiple projects also, whether there was a conflict).
I had a similar issue some times ago. You can inspect the stack to see what gets loaded. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Moose default loads an old MorphTreeMorph???
|
|
In reply to this post by Simon Denier-3
Hi Simon: print or inspect the result of something like this:
(ConfigurationOfXXX project version: 'xxx') record loadDirective or if you use groups or packages in the load: ((ConfigurationOfXXX project version: 'xxx') record: 'Tests') loadDirective with that you can notice what you need cheers ps: I learn about #record in our own Metacello talk at ESUG with Dale hahahhaha On Fri, Sep 24, 2010 at 5:44 PM, Simon Denier <[hidden email]> wrote: OK, I just had this problem today, not previously during the week, and I can't find the source. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Moose default loads an old MorphTreeMorph???
|
|
In reply to this post by Simon Denier-3
On 24 sept. 2010, at 23:19, Mariano Martinez Peck wrote: Hi Simon: print or inspect the result of something like this: OK thanks Mariano, I thought there was such a mechanism but I was not sure. However I was not able to find the culprit. And now it loads fine with just the fix for PetitParser config?
Well I was taking pictures in Barcelona at the time, so I don't have a good excuse either :)
-- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Moose default loads an old MorphTreeMorph???
|
|
Hi,
This problem only exists in the ConfigurationOfPetitParser that ended up in the Moose repository. This seems to be related to the release of 4.1 because the 1.0 version was published in the Moose repo by Jannik. Also, version 1.0 depends on the default baseline which is wrong. Anyway, the reason why updating from the 4.1 release does not work is that the 4.1 release depends on the petitparser configuration from the Moose repository while the default depends on the one from the petitparser repository. Cheers, Doru On 25 Sep 2010, at 02:08, Simon Denier wrote: > > On 24 sept. 2010, at 23:19, Mariano Martinez Peck wrote: > >> Hi Simon: print or inspect the result of something like this: >> >> (ConfigurationOfXXX project version: 'xxx') record loadDirective >> >> or if you use groups or packages in the load: >> >> ((ConfigurationOfXXX project version: 'xxx') record: 'Tests') loadDirective >> >> with that you can notice what you need > > > OK thanks Mariano, I thought there was such a mechanism but I was not sure. However I was not able to find the culprit. And now it loads fine with just the fix for PetitParser config? > > >> >> cheers >> >> ps: I learn about #record in our own Metacello talk at ESUG with Dale hahahhaha > > Well I was taking pictures in Barcelona at the time, so I don't have a good excuse either :) > >> >> >> On Fri, Sep 24, 2010 at 5:44 PM, Simon Denier <[hidden email]> wrote: >> OK, I just had this problem today, not previously during the week, and I can't find the source. >> >> When updating my Moose image I got: >> >> Loading default of ConfigurationOfMoose... <connection closed> >> Fetched -> Famix-ManifestMf-tg.6 --- http://www.squeaksource.com/Moose --- http://www.squeaksource.com/Moose >> Project: MooseAlgos for Moose default >> Project: PetitParser for Moose default >> Project: Glamour for Petit 2.0-beta.7 >> Fetched -> Morphic-MorphTreeWidget-AlainPlantec.88 --- http://www.squeaksource.com/Momo10 --- >> (....) >> >> >> Two strange things going on: >> - PetitParser default requiring Glamour for Petit 2.0-beta.7 (probably a bug when the config was copied to the Moose repo for the 4.0 release. This is now fixed) >> - Morphic-MorphTreeWidget-AlainPlantec.88 got fetched, I have no idea how/which project required this package which dates back to january 2010 (it's not Glamour 2.0-beta.7) >> >> >> Can anyone reproduce this problem, starting from a 4.1 release then updating to default? Or starting fresh and loading default? >> >> >> Dale, I think I have another use case for the Metacello browser, it's being able to debug such a case, by simulating/resolving which versions of a package would actually be loaded, and which project requested this version (in case there are multiple projects also, whether there was a conflict). >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Presenting is storytelling." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |