Oops. Sorry for creating confusions.
Doru
On Jul 25, 2013, at 1:55 PM, Igor Stasenko wrote:
> On 25 July 2013 12:05, Tudor Girba 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/
I meant stable, but given that I thought Norbert needs to update his local
copy, I said "latest stable". Confusing :)
Doru
On Jul 25, 2013, at 2:00 PM, Guillermo Polito wrote:
> Something I do not understand: "Latest stable" means latest or stable ? :).
> More specifically, How did you downl
Something I do not understand: "Latest stable" means latest or stable ? :).
More specifically, How did you download it?
Because as far as I knew it was not fixed by Esteban in the VM... But maybe
one of the latest merges with Eliot's branch fixed it...
On Thu, Jul 25, 2013 at 1:55 PM, Igor Stase
On 25 July 2013 12:05, Tudor Girba 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
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. Este
Do you know details of the problem. It is always good to now.
Norbert
Am 25.07.2013 um 09:08 schrieb Tudor Girba :
> 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 m
On Jul 25, 2013, at 9:08 AM, Tudor Girba 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
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.
Cheers,
Doru
On T
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
Doru,
that's exactly what I did before.
Norbert
Am 24.07.2013 um 22:46 schrieb Tudor Girba :
> Use the latest stable VM. It should solve the problem.
>
> Doru
>
>
> On Jul 24, 2013, at 10:34 PM, Norbert Hartl wrote:
>
>>
>>
>> Am 24.07.2013 um 18:21 schrieb Stéphane Ducasse :
>>
>>>
>>
On 24 July 2013 22:46, Tudor Girba wrote:
> Use the latest stable VM. It should solve the problem.
>
Nope. Problem will be solved if we will know exactly what causing it,
write test with can reproduce it with 100% guarantee.
Using latest VM is not recipe from disease.
Unfortunately, we still don
Use the latest stable VM. It should solve the problem.
Doru
On Jul 24, 2013, at 10:34 PM, Norbert Hartl wrote:
>
>
> Am 24.07.2013 um 18:21 schrieb Stéphane Ducasse :
>
>>
>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl wrote:
>>
>>> As I cannot work with the pharo VM right now
>>
>> what
Am 24.07.2013 um 18:21 schrieb Stéphane Ducasse :
>
> On Jul 24, 2013, at 5:13 PM, Norbert Hartl 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
On Jul 24, 2013, at 5:13 PM, Norbert Hartl wrote:
> As I cannot work with the pharo VM right now
what is the problem?
> 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 s
On 24 July 2013 17:13, Norbert Hartl wrote:
> As I cannot work with the pharo VM right now 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 al
15 matches
Mail list logo
