On 25 July 2013 12:05, Tudor Girba <tu...@tudorgirba.com> wrote: > The workaround at the image level was needed only until we got the VM > working. The details about the workaround are here: > https://pharo.fogbugz.com/f/cases/10395/ > > I was sure that in the meantime, the problem was solved in the VM as well, > but I cannot trace that information. Perhaps it is not. Esteban? >
Last time i discussed with Esteban about it, he said that he don't knows where the problem in VM, neither me. > Cheers, > Doru > > > On Thu, Jul 25, 2013 at 9:13 AM, Stéphane Ducasse > <stephane.duca...@inria.fr> wrote: >> >> >> On Jul 25, 2013, at 9:08 AM, Tudor Girba <tu...@tudorgirba.com> wrote: >> >> This was a problem that we also had (when working in Moose), and Esteban >> fixed it (first the workaround in the image, and then in the VM). We are >> using this VM since some months now and the problem did not resurface. >> >> That is why I know it is fixed in the latest stable PharoVM. >> >> >> Ok what igor is probably meaning is that we would prefer to get the system >> running without having to have a workaround at the image level. >> >> >> Cheers, >> Doru >> >> >> On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norb...@hartl.name> wrote: >>> >>> Doru, >>> >>> I'm sorry but I was mistaken somehow. I tried always to use the newest >>> VM. I just downloaded a new vm a few minutes ago and now I cannot reproduce >>> the problem anymore. That doesn't mean it won't appear anymore but I'll work >>> with the pharo vm and see if it comes back. >>> >>> thanks, >>> >>> Norbert >>> >>> Am 24.07.2013 um 22:46 schrieb Tudor Girba <tu...@tudorgirba.com>: >>> >>> > Use the latest stable VM. It should solve the problem. >>> > >>> > Doru >>> > >>> > >>> > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norb...@hartl.name> wrote: >>> > >>> >> >>> >> >>> >> Am 24.07.2013 um 18:21 schrieb Stéphane Ducasse >>> >> <stephane.duca...@inria.fr>: >>> >> >>> >>> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norb...@hartl.name> >>> >>> wrote: >>> >>> >>> >>>> As I cannot work with the pharo VM right now >>> >>> >>> >>> what is the problem? >>> >> >>> >> I get the DNU SmallInteger>>add: all the time especially when using >>> >> metacello (Using Versionner I get it nearly every attempt to validate the >>> >> configuration). This occurred already a few times on the list. >>> >> >>> >> >>> >>> >>> >>>> I'm back to use Eliots Cog. But If I open a more recent image it >>> >>>> complains about my vm being to old. What does it really check in order >>> >>>> to >>> >>>> complain? Some just version string/number parsing? Is it always sever? >>> >>>> >>> >>>> Norbert >>> >>> >>> >>> >>> >> >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Quality cannot be an afterthought." >>> > >>> > >>> >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- Best regards, Igor Stasenko.
