March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] moose job on jenkins

by Tudor Girba

Hi Camillo, Something happened with the execution rights of the scripts because in the meantime: wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash do not have execution rights. Cheers, Doru On Mar 18, 2013, at 7:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Camillo, > > Thanks for the remarks. > > We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM. > > Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability. > > If it will really not work, we will use the stable one, but at the moment, it works :) > > Cheers, > Doru > > > On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> Nice! good to see ;) >> >> Some little remarks: >> >> - `wget --quiet -qO` can be simplified as `wget --quiet -O -` >> since -q is just the short form for --quiet ;) >> - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh >> since Latest might break unexpectedly whereas ciPharoVM.sh points to >> latest stable release >> >> best cami >> >> On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: >>> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Be rather willing to give than demanding to get." >>> >>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by Tudor Girba

Hi Camillo, Thanks for the remarks. We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM. Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability. If it will really not work, we will use the stable one, but at the moment, it works :) Cheers, Doru On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Nice! good to see ;) > > Some little remarks: > > - `wget --quiet -qO` can be simplified as `wget --quiet -O -` > since -q is just the short form for --quiet ;) > - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh > since Latest might break unexpectedly whereas ciPharoVM.sh points to > latest stable release > > best cami > > On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: >> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> > > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by Camillo Bruni

Nice! good to see ;) Some little remarks: - `wget --quiet -qO` can be simplified as `wget --quiet -O -` since -q is just the short form for --quiet ;) - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh since Latest might break unexpectedly whereas ciPharoVM.sh points to latest stable release best cami On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: > http://www.tudorgirba.com/blog/moose-4-8-on-jenkins > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > >

March 17, 2013

[Pharo-project] moose job on jenkins

by Tudor Girba

Hi, I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: http://www.tudorgirba.com/blog/moose-4-8-on-jenkins Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

March 17, 2013

Re: [Pharo-project] Bug with drag and drop

by Benjamin

https://pharo.fogbugz.com And I am adding you right now (still waiting for Penelope) Ben On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > ok, where is it ? > > Jannik > > On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> fogz bugs :) >> >> On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> Hi all, >>> >>> I have a bug with drag and dropping windows inside Pharo. >>> For example, take Nautilus and drag-drop the browser outside pharo. >>> It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: >>> >>> Another question: should I use GoogleCode issue tracking or fogbugs ? >>> >>> Cheers, >>> Jannik >> >> > >

March 17, 2013

Re: [Pharo-project] Bug with drag and drop

by jannik.laval

ok, where is it ? Jannik On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > fogz bugs :) > > On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> Hi all, >> >> I have a bug with drag and dropping windows inside Pharo. >> For example, take Nautilus and drag-drop the browser outside pharo. >> It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: >> >> Another question: should I use GoogleCode issue tracking or fogbugs ? >> >> Cheers, >> Jannik > >

March 17, 2013

Re: [Pharo-project] Bug with drag and drop

by stephane ducasse

fogz bugs :) On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi all, > > I have a bug with drag and dropping windows inside Pharo. > For example, take Nautilus and drag-drop the browser outside pharo. > It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: > > Another question: should I use GoogleCode issue tracking or fogbugs ? > > Cheers, > Jannik

March 17, 2013

[Pharo-project] pharoconf | mooseday | 2013 - call for participation

by Tudor Girba

(please distribute) We are happy to invite you to the PharoConf | MooseDay | 2013: http://scg.unibe.ch/wiki/events/pharoconf-mooseday-2013 The conference will take place at the University of Bern during April 2-4: - PharoConf (April 2,3) - MooseDay (April 4) The conference will be free and will even include a free lunch. Yes, free lunch. No trick. We only kindly ask you to register online for each event as soon as possible. STUDENT SPONSORSHIPS: ESUG will sponsor the travel of up to 10 students with 150 EUR / person. Please apply for sponsorship by mail at esug-info(a)esug.org. First-come, first-served. The conference sponsors will sponsor the travel of up to 10 students with up to 200 CHF / person. Please apply for sponsorship before the conference by mail at tudor(a)tudorgirba.com. First-come, first-served. IMPORTANT If you are a student, please bring your student cards with you to help us limit the lunch costs. Cheers, The organizers

March 17, 2013

[Pharo-project] Bug with drag and drop

by jannik.laval

Hi all, I have a bug with drag and dropping windows inside Pharo. For example, take Nautilus and drag-drop the browser outside pharo. It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: Another question: should I use GoogleCode issue tracking or fogbugs ? Cheers, Jannik

March 17, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by stephane ducasse

thanks damien :) On Mar 17, 2013, at 4:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > Okâ¦ apparently the day-of-month and day-of-week fields in a crontab do not act as AND but as OR. Now the email should get sent on 1st and 3rd mondays only. > > > On 17 March 2013 07:00, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > > ### What's next, until 2013-03-24 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) > > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet

March 17, 2013