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 Simon.Denier@inria.fr 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev