July 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Your vm is too oldâ¦.

by Tudor Girba

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? Cheers, Doru On Thu, Jul 25, 2013 at 9:13 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Jul 25, 2013, at 9:08 AM, Tudor Girba <tudor(a)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 <norbert(a)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 <tudor(a)tudorgirba.com>: >> >> > Use the latest stable VM. It should solve the problem. >> > >> > Doru >> > >> > >> > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> > >> >> >> >> >> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr>: >> >> >> >>> >> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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"

July 25, 2013

What is the project repository for ci build tools

by Norbert Hartl

I try to figure out where is the home project location of HudsonBuildTools20 I can only see it in pharo20/pharoInbox Norbert

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Do you know details of the problem. It is always good to now. Norbert Am 25.07.2013 um 09:08 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > 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 Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)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 <tudor(a)tudorgirba.com>: > > > Use the latest stable VM. It should solve the problem. > > > > Doru > > > > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> > >> > >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> > >>> > >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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"

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by StÃ©phane Ducasse

On Jul 25, 2013, at 9:08 AM, Tudor Girba <tudor(a)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 <norbert(a)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 <tudor(a)tudorgirba.com>: > > > Use the latest stable VM. It should solve the problem. > > > > Doru > > > > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> > >> > >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> > >>> > >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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"

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by 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 months now and the problem did not resurface. That is why I know it is fixed in the latest stable PharoVM. Cheers, Doru On Thu, Jul 25, 2013 at 9:03 AM, Norbert Hartl <norbert(a)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 <tudor(a)tudorgirba.com>: > > > Use the latest stable VM. It should solve the problem. > > > > Doru > > > > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> > >> > >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr>: > >> > >>> > >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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"

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

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 <tudor(a)tudorgirba.com>: > Use the latest stable VM. It should solve the problem. > > Doru > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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." > >

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Doru, that's exactly what I did before. Norbert Am 24.07.2013 um 22:46 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > Use the latest stable VM. It should solve the problem. > > Doru > > > On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> >> Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> >>> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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." > >

July 25, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Igor Stasenko

On 24 July 2013 22:46, Tudor Girba <tudor(a)tudorgirba.com> 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't have reproducible case and that blocks us from fixing it. > Doru > -- Best regards, Igor Stasenko.

July 24, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Tudor Girba

Use the latest stable VM. It should solve the problem. Doru On Jul 24, 2013, at 10:34 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> >> On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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."

July 24, 2013

Re: [Pharo-users] Your vm is too oldâ¦.

by Norbert Hartl

Am 24.07.2013 um 18:21 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Jul 24, 2013, at 5:13 PM, Norbert Hartl <norbert(a)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 > >

July 24, 2013