Amazing :)
I started to migrate part of the update to the installer but never finished.

Stef


I found the problem. Its a quite complex bug, actually, as it is not related to the update #120 but to #116. I inadvertently introduced the problem with the memory clean up script. It resets the update downloader, and this makes the update queue to get into an inconsistent state after consuming 5 more updates. This is why we did not see the problem earlier but only now that we update from 116 through to 120.

I don't have time to fix that now, but I will try this evening.

Adrian


On Nov 6, 2008, at 11:11 , Stéphane Ducasse wrote:

I will try too.
I retried from 10095 during the sprint at my place.
but now I will retry from 107

This was when we got the problem with lukas removal.
and as you see I did not update the log

This is the last time I do update from bern (because of this caching proxy
I could not test directly).

------------------------------------------------------
update10118
- fix script loading broken.
        Issue 294:      VM does not send script files to image
------------------------------------------------------
update10119
- fix script loading broken.
        Issue 294:      VM does not send script files to image
------------------------------------------------------
update10119
- fix script loading broken.
        Issue 294:      VM does not send script files to image
------------------------------------------------------
update10120
- Etoy removal
                TextMorph
                ThumbnailMorph
                TileMorphTest
                TraitDescription
                UndefinedObjectTest
                UpdatingStringMorph
                Vocabulary
------------------------------------------------------


On Nov 6, 2008, at 10:56 AM, Marcus Denker wrote:


On 04.11.2008, at 10:30, Damien Cassou wrote:

Hi,

could you please release an image with the latest changes so that I
can base the new pharo-dev on them?



So... I tried to update the last core image (107) from the gforge. But that one stops after
update 120. (blocked in a semaphore). Very strange.

I have an image that I updated often, I never had problems updating that one.

Very strange.

        Marcus


--
Marcus Denker  --  [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to