Thanks,
I remembered about recent discussion, but wrongly assumed I could
guess by myself crawling into the image...
I followed the path you indicated and published again
http://source.squeak.org/trunk/update-nice.33.mcm .

Nicolas

2009/10/5 Bert Freudenberg <bert at freudenbergs.de>:
>
> On 05.10.2009, at 14:19, Nicolas Cellier wrote:
>
>> Sorry Edgar, this is my first .mcm, I'm still learning.
>> I removed the line corresponding to OB in update-nice.33.mcm
>> Would you try again ?
>
> You normally should not make a new MCM but update a previous one. Your new
> one does not have the right load order.
>
> See forwarded message below. I also added this to
>
>        http://source.squeak.org/trunk.html
>
> Does someone want to expand on this?
>
>> Another question: is there a way to upload a .mcm via web interface
>> rather than thru squeak iface?
>> source.squeak.org insist on the uploaded file to be a .mcz ...
>
> I don't think there is a web interface.
>
>> Last, I think I uploaded a update.mcm by mistake (I thought programmer
>> and version would be automatic like for any .mcz). How can I delete
>> it?
>
> You need to ask an admin (listed on the trunk page). I just deleted it.
>
> - Bert -
>
>
>
> Begin forwarded message:
>
>> From: Bert Freudenberg <bert at freudenbergs.de>
>> Date: 30. September 2009 13:01:19 MESZ
>> To: The general-purpose Squeak developers list
>> <squeak-dev at lists.squeakfoundation.org>
>> Subject: Re: [squeak-dev] How do I use Monticello Configurations?
>>
>>
>> On 30.09.2009, at 10:49, Joshua Gargus wrote:
>>
>>> I've never used Monticello Configurations before, and would like some
>>> guidance before I screw up the trunk (there's your motivation to answer
>>> quickly, hah!  :-).  Here are my questions:
>>>
>>> I don't feel like adding each package individually, since this seems
>>> error-prone and is definitely tedious.  Is it safe to add packages using
>>> match '*'?  This seems a bit dangerous, because I might inadvertently add a
>>> package that doesn't belong (eg: if I'm also working on a package that isn't
>>> in trunk/).  Is there a way to start from a previous configuration?
>>
>> Yes. It's *the* way.
>>
>>> In other words, can I populate a new configuration using the latest
>>> versions of all packages in a previous configuration?
>>
>> Yes. Open the previous configuration (select it in the repo, click
>> browse). Then update it (click Update / from image).
>>
>>> Can you specify multiple version of the same package in a single
>>> configuration?  For example, if I want to load Compiler-jcg.85 before
>>> Compiler-jcg.86, can I add them in that order to a Configuration, or do I
>>> need to create two Configurations?
>>
>> I never tried the former, but the latter is the canonical way.
>>
>> Typically you only need to provide conf maps for the intermediate steps.
>> After the last explicit configuration is loaded, the updater proceeds to
>> load the latest version of all packages it can find.
>>
>> - Bert -
>>
>>
>
>
>