So apparently if I update from 10281 up to 10293 then this is ok If I save and and continue the update the update works. So I could either let it like that and people use 10296 directly or I can try to squeese in a cs that save and quit the image at 10293. Let me know
Stef On May 2, 2009, at 5:23 PM, Stéphane Ducasse wrote: > or I can publish a 10296 made from 10293 > may be saving the image is an important step. > > Stef > > On May 2, 2009, at 4:43 PM, Stéphane Ducasse wrote: > >> Yes I can reproduce it and it makes the image totally unusable on mac >> So I will cancel all the releases above 10294, 10295, 10296 (cool I >> was stupid to push not working code) and remove 10294. >> >> I will try to see if this is really 10294 which fucked up from 10281. >> >> Stef (bored). >> >> >> >> >> >>> Thanks igor >>> take the published 10281-core and do update. >>> I'm redoing it now to verify it I can reproduce it. >>> >>> Stef >>> >>> >>> On May 2, 2009, at 4:16 PM, Igor Stasenko wrote: >>> >>>> 2009/5/2 Stéphane Ducasse <[email protected]>: >>>>> this is quite strange. >>>>> I wanted to offer a new image so I took 10281 and did an update >>>>> but at the end I got problem with sensor and hand.... >>>>> >>>> >>>> Stef, can you give me a list of doits to repeat teh problems? >>>> I'll try to debug & fix. >>>> >>>>> Stef >>>>> >>>>> On May 2, 2009, at 3:56 PM, Stéphane Ducasse wrote: >>>>> >>>>>> Hi >>>>>> here are some updates: >>>>>> >>>>>> 10294 >>>>>> - not working sensor fixes :( but like that they are in >>>>>> >>>>>> 10295 >>>>>> - http://code.google.com/p/pharo/issues/detail?id=789 >>>>>> (PseudoContext >>>>>> initialize) >>>>>> - http://code.google.com/p/pharo/issues/detail?id=788 (compact >>>>>> classes >>>>>> - http://code.google.com/p/pharo/issues/detail?id=783 Issue >>>>>> 783: >>>>>> Better ContextPart>>errorReportOn: >>>>>> >>>>>> 10296 >>>>>> - http://code.google.com/p/pharo/issues/detail?id=790: >>>>>> bookmorph >>>>>> cleaning >>>>>> - http://code.google.com/p/pharo/issues/detail?id=756 font >>>>>> rendering >>>>>> speed up >>>>>> - http://code.google.com/p/pharo/issues/detail?id=786 >>>>>> (remoteString >>>>>> closing) >>>>>> >>>>>> stef >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>>> _______________________________________________ >>>> 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 > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
