About MC for managing the image

[stéphane ducasse]

I redid the experienc using another vm and it worked.
Now I got an error when I pressed allNewer since I want all the new  
changes. fullTimeStamp not understood
because

isLocalNewer
     ....self remoteDefinition fullTimeStamp

is nil

By the way what is source same but rev changed.....

What is rev?
revision?
What is a revision?
....uhhhhh


Stef



On 21 sept. 05, at 12:10, stéphane ducasse wrote:



> Now I did the following:
>
> Loaded morphic splitters
> added all the packages as required packages of Sqeuak and saved
>
> then took back a new image, loaded MC274 and loaded the squeak.mcz  
> file obtained previously
> and it froze squeak.
>
> I'm redoing the experiment
>
> Stef
>
>
>
> On 21 sept. 05, at 08:20, Daniel Vainsencher wrote:
>
>
>
>
>> I had a bit of that when I was doing it, in my case because some  
>> packages were needed from source.sqf.org which was inaccessible at  
>> the time.
>>
>> Discover what packages/versions it wants, and make sure you have  
>> repositories with those in the relevant repository group (this was  
>> the quick solution for me, switched to source2), or do like Avi  
>> says and get everything before hand.
>>
>> Daniel
>>
>> Avi Bryant wrote:
>>
>>
>>
>>
>>> On Sep 20, 2005, at 10:53 PM, stéphane ducasse wrote:
>>>
>>>
>>>
>>>
>>>> Hi
>>>>
>>>> yesterday I loaded the new version of MC and selected my old  
>>>> squeak. 2.mcz that was not loading previously and
>>>> I did merge....
>>>>
>>>> It works until I got an error like cannot find files....and I  
>>>> could  not understand why.
>>>> So I wanted to redo the complete experiement today but kilana  
>>>> was  out of reach.
>>>> I will retry locally and if it works I will publish that on 39a
>>>>
>>>>
>>>> should I use your script instead of clicking on the merge button?
>>>> Setf
>>>>
>>>>
>>>>
>>>>
>>> The merge button should work - but it sounds like there was some   
>>> problem with your repository configuration.  Simplest would be  
>>> to  make sure that all the relevant .mcz files are in your  
>>> package-cache  directory before you start the merge.
>>> Avi
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
>