June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking

by Pavel Krivanek

On Wed, Jun 29, 2011 at 9:03 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Tue, Jun 28, 2011 at 9:56 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> >> >> On Tue, Jun 28, 2011 at 6:54 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >>> >>> On Jun 28, 2011, at 2:37 PM, Marcus Denker wrote: >>> >>> > >>> >> >>> >> As I see we have the first successfull build of the reloaded core :-) >>> > Very nice!!! >>> > >>> >> Maybe it will be better to have separate project for it and run all >>> >> tests on it (the standard way used for the normal image may be used). >>> >> >>> > >>> > Yes, that is a good idea. I will set it up (slowly). >>> > >>> >>> >>> Ok, 3 failing tests out of 7 911: >>> >>> >>> Â https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%20Reload/lastCompletedBu… >>> >> >> wow. Awesome. >> What a great work. > > It is incredible result. I have only one explanation for such a great > success: Hudson doesn't count tests that raise error ;-) > > -- Pavel Can't belive... it does :-) -- Pavel >>> >>> -- >>> Marcus Denker Â -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >

June 29, 2011

Re: [Pharo-project] 1.3 core and full image

by Marcus Denker

On Jun 29, 2011, at 11:19 AM, Norbert Hartl wrote: > Finally I decided to switch my working environment from 1.2 to 1.3. And I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails. > Doing it by loading > > ConfigurationOfPharo project latestVersion load > > it cannot resolve OB-Standard-lr.541 > > After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way > > "Dev image" > Deprecation raiseWarning: false. > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. > > I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion. > It works on the test server. I never tried it else > The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work? > No pharo full means retiring ConfigurationOfPharo... at least, I can not gurantuee that it works, I tried, I failed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 29, 2011

Re: [Pharo-project] 1.3 core and full image

by Norbert Hartl

Am 29.06.2011 um 11:42 schrieb Damien Cassou: > On Wed, Jun 29, 2011 at 11:19 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> "Dev image" >> Deprecation raiseWarning: false. >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfPharo'; >> load. >> ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: >> #silently: with: true; perform: #load. >> >> I don't know how this can work. In my image there is no lastVersion in >> metacello only latestVersion. > > you are in a dynamic language, anything can happen :-). Try it and > it's getting to work (I guess because Metacello is automatically > updated before). That won't solve your OB problem however. > You don't need a dynamic language to make software behaviour something manitou. Well, I tried it and it doesn't work. I copied the head of the file to my workspace. Ok I ommited to perform silently stuff. Norbert

June 29, 2011

Re: [Pharo-project] 1.3 core and full image

by Damien Cassou

On Wed, Jun 29, 2011 at 11:19 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > "Dev image" > Deprecation raiseWarning: false. > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: > #silently: with: true; perform: #load. > > I don't know how this can work. In my image there is no lastVersion in > metacello only latestVersion. you are in a dynamic language, anything can happen :-). Try it and it's getting to work (I guess because Metacello is automatically updated before). That won't solve your OB problem however. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 29, 2011

[Pharo-project] 1.3 core and full image

by Norbert Hartl

Finally I decided to switch my working environment from 1.2 to 1.3. And I like to it from pharo core because I want to learn how can produce my own image. But I struggle right at the beginning. I could load ocompletion and shout. Loading anything that has a dependency on omnibrowser fails. Doing it by loading ConfigurationOfPharo project latestVersion load it cannot resolve OB-Standard-lr.541 After that I looked on ci.pharo-project.org because there it works. But if I look at Pharo-1.3.st it loads it this way "Dev image" Deprecation raiseWarning: false. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. I don't know how this can work. In my image there is no lastVersion in metacello only latestVersion. The presence of a thread about "not using pharo full" should show that it is rather easy to build up your own image. Unfortunately I'm too stupid to do it. How is it supposed to work? Norbert

June 29, 2011

Re: [Pharo-project] About HTTP proxies, settings and MacOS

by Marcus Denker

> Thanks Sven, that worked :) > Thanks Marcus for pointing us to the right place to fix it. > > Can we integrate it marcus for 1.3? > > Yes! please add something machine readable to the bug tracker issue: http://code.google.com/p/pharo/issues/detail?id=4473 -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

June 29, 2011

Re: [Pharo-project] About HTTP proxies, settings and MacOS

by Mariano Martinez Peck

On Tue, Jun 28, 2011 at 12:13 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 28 Jun 2011, at 11:12, Marcus Denker wrote: > > > InternetConfiguration>>startUp > > OSPlatform isMacOS ifTrue: [ > > self useHTTPProxy ifTrue: [ > > (self getHTTPProxyHost findTokens: ':') > ifNotEmpty: [:p | > > HTTPSocket useProxyServerNamed: p first > port: p second asInteger]]] > > After browsing the code a bit, adding > > NetworkSystemSettings useHTTPProxy: true > inside the ifNotEmpty: as last statement might already help. > > Thanks Sven, that worked :) Thanks Marcus for pointing us to the right place to fix it. Can we integrate it marcus for 1.3? > It would be cleaner to no longer reference HTTPSocket here and add use > NetworkSystemSettings. The silly thing is that currently, > NetworkSystemSettings itself falls back to HTTPSocket for the proxy host and > port, for backwards compatibility reasons no doubt. Still, the > abstraction/indirection would be good. So then it the code would be > > NetworkSystemSettings > httpProxyServer: p first; > httpProxyPort: p second asInteger; > useHTTPProxy: true > > As sole contents of the ifNotEmpty: > > But since I am not behind a proxy, this must still be tested by someone who > is. > > Regards, > > Sven > > > > -- Mariano http://marianopeck.wordpress.com

June 29, 2011

[Pharo-project] [Hudson->Jenkins] slowly stopping 1.2 autobuild

by Marcus Denker

Hi, We should move from https://pharo-ic.lille.inria.fr/hudson to https://ci.lille.inria.fr/pharo/ Now running things in parrallel is messy, as we have only one set of slave machines. So we should move eveything (it's not that difficult, just copy over the config). With 1.3 released soon, we will retire 1.2 from the build server (like we did with 1.1). 1.3 we should move to Jenkins. As a first step, I will remove the following: - Aida Pharo 1.2 - Seaside Pharo 1.2 - XMLRPC Pharo 1.2 - Zinc Pharo 1.2 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 29, 2011

Re: [Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking

by Pavel Krivanek

On Tue, Jun 28, 2011 at 9:56 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Tue, Jun 28, 2011 at 6:54 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: >> >> On Jun 28, 2011, at 2:37 PM, Marcus Denker wrote: >> >> > >> >> >> >> As I see we have the first successfull build of the reloaded core :-) >> > Very nice!!! >> > >> >> Maybe it will be better to have separate project for it and run all >> >> tests on it (the standard way used for the normal image may be used). >> >> >> > >> > Yes, that is a good idea. I will set it up (slowly). >> > >> >> >> Ok, 3 failing tests out of 7 911: >> >> >> Â https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%20Reload/lastCompletedBu… >> > > wow. Awesome. > What a great work. It is incredible result. I have only one explanation for such a great success: Hudson doesn't count tests that raise error ;-) -- Pavel > >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >

June 29, 2011

[Pharo-project] [PBE-Spanish] Status update 2011-06-28

by NicolÃ¡s Paez

Hello everyone, Here is the weekly update of the Spanish translation of Pharo By Example book. *Summary* - We are almost there, just 2 chapter remaining - We are still having problems with the compilation of some chapters - Clara joined the translation team - 2 more people offer to collaborate in the revision process - This week we will publish a new drop *Chapters drill down* Chapter 01: completed, but not published yet Chapter 02: completed, but not published yet Chapter 03: completed, already published Chapter 04: completed, already published Chapter 05: completed, but not published yet and with compilation errors Chapter 06: completed, but not published yet Chapter 07: completed, and with compilation errors Chapter 08: completed, and with compilation errors Chapter 09: completed, and with compilation errors Chapter 10: 28 % Chapter 11: completed, already published Chapter 12: 70% Chapter 13: completed, and with compilation errors Chapter 14: completed Regards, NicoPaez http://nicopaez.wordpress.com

June 29, 2011