- Pharo-dev - lists.pharo.org

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

by Norbert Hartl

Am 29.06.2011 um 20:34 schrieb Yanni Chiu: > I see that you've got your build going now. Anyhow, here's the reply that I started before lunch... > > On 29/06/11 9:50 AM, Norbert Hartl wrote: >> >> ConfigurationOfSeaside30 project lastVersion load >> >> isn't that strange, right? ConfigurationOfSeaside30 references >> OmniBrowser stable. OmniBrowser stable is 1.3 which references the file >> OmniBrowser-Standard-lr.541 which can not be found in the repository >> specified for omnibrowser. >> >> So I'm trying to understand this. Either I'm doing something wrong or >> the CI stuff is broken. And I don't have a glue how others solve this. > > My build script is at: > http://hudson.jooshr.org/view/Pharo1.3/job/Pharo1.3-Seaside3.0/ws/p13-seasi… > I'll take a look. > I've not looked at it in a while. It seems that I load Seaside using Gofer, without going through Metacello. It's done this way, because the ConfigurationOfSeaside30 did not exist, when this build was set up. > I don't use Metacello for most of the stuff in jenkins, too. I thought it might be a good idea to test this in my development image. > I also do not load Omnibrowser because it was not loading properly, at the time I was setting up my build. I had to adjust the Seaside packages that were loaded, to avoid the need for Omnibrowser. > I figured out the problem but didn't find the file. So this was a dead end. > In some downstream jobs, I do use Monticello configs, because they were available, when I was setting up those build jobs. > > Your guess that the missing package is in the build cache is likely correct. That missing package is available at: > http://source.lukas-renggli.ch/omnibrowser.html > That should get you past that hurdle in your build, so you can start to customize it. Hmmm, I though I looked at this location but couldn't find the particular file. The package in the package-cache is a two fold thing. I understand it is a big hussle for developers if they have problems because loading of a package fails. With the package-cache you lose to test a setup that is reproducible by others. That's not good but then it is a rare case (or should be) that might not need to be covered. thanks for your help, Norbert

June 29, 2011

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

by Marcus Denker

On Jun 29, 2011, at 8:25 PM, Chris Cunningham wrote: > On Wed, Jun 29, 2011 at 5:17 AM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> So...now if I save the image in a place where I have a proxy (my work) and >> then I try to open it in another place that has no proxy (my home), it >> doesn't work. To solve that I did: >> >> startUp >> OSPlatform isMacOS ifTrue: [ >> self useHTTPProxy ifTrue: [ >> (self getHTTPProxyHost findTokens: ':') ifNotEmpty: [:p | >> NetworkSystemSettings useHTTPProxy: true. >> HTTPSocket useProxyServerNamed: p first port: p second >> asInteger]] >> ifFalse: [HTTPSocket stopUsingProxyServer. >> NetworkSystemSettings useHTTPProxy: false]] >> > > Am I reading this right? If I was on, say, Windows behind a proxy, > this would disable proxy use on startup? So, every time I started an > image, I would have to manually re-enable proxy use? > This is not good. InternetConfiguration has a method called on image save that removes the proxy on the mac: shutDown OSPlatform isMacOS ifTrue: [ HTTPSocket stopUsingProxyServer ] startUp should not mess with the proxy on other systems. > Would there be a way to detect if the proxy still exists on startUp, > and if it doesn't, then temporarily disable the proxy instead? It's the duty of the OS to provide proxy info, and the duty of the VM to provide this to the Image. Till today, this exists only on the Mac. 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 Yanni Chiu

I see that you've got your build going now. Anyhow, here's the reply that I started before lunch... On 29/06/11 9:50 AM, Norbert Hartl wrote: > > ConfigurationOfSeaside30 project lastVersion load > > isn't that strange, right? ConfigurationOfSeaside30 references > OmniBrowser stable. OmniBrowser stable is 1.3 which references the file > OmniBrowser-Standard-lr.541 which can not be found in the repository > specified for omnibrowser. > > So I'm trying to understand this. Either I'm doing something wrong or > the CI stuff is broken. And I don't have a glue how others solve this. My build script is at: http://hudson.jooshr.org/view/Pharo1.3/job/Pharo1.3-Seaside3.0/ws/p13-seasi… I've not looked at it in a while. It seems that I load Seaside using Gofer, without going through Metacello. It's done this way, because the ConfigurationOfSeaside30 did not exist, when this build was set up. I also do not load Omnibrowser because it was not loading properly, at the time I was setting up my build. I had to adjust the Seaside packages that were loaded, to avoid the need for Omnibrowser. In some downstream jobs, I do use Monticello configs, because they were available, when I was setting up those build jobs. Your guess that the missing package is in the build cache is likely correct. That missing package is available at: http://source.lukas-renggli.ch/omnibrowser.html That should get you past that hurdle in your build, so you can start to customize it.

June 29, 2011

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

by Chris Cunningham

On Wed, Jun 29, 2011 at 5:17 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > So...now if I save the image in a place where I have a proxy (my work) and > then I try to open it in another place that has no proxy (my home), it > doesn't work. To solve that I did: > > startUp > Â Â Â OSPlatform isMacOS ifTrue: [ > Â Â Â Â Â Â self useHTTPProxy ifTrue: [ > Â Â Â Â Â Â Â Â Â Â (self getHTTPProxyHost findTokens: ':') ifNotEmpty: [:p | > Â Â Â Â Â Â Â Â Â Â Â Â NetworkSystemSettings useHTTPProxy: true. > Â Â Â Â Â Â Â Â Â Â Â Â Â HTTPSocket useProxyServerNamed: p first port: p second > asInteger]] > Â Â Â Â Â Â ifFalse: [HTTPSocket stopUsingProxyServer. > Â Â Â Â Â Â Â Â Â NetworkSystemSettings useHTTPProxy: false]] > Am I reading this right? If I was on, say, Windows behind a proxy, this would disable proxy use on startup? So, every time I started an image, I would have to manually re-enable proxy use? Would there be a way to detect if the proxy still exists on startUp, and if it doesn't, then temporarily disable the proxy instead? -Chris

June 29, 2011

[Pharo-project] Checking password entropy

by John Toohey

Hi, Does anyone know of a package for Pharo that can calculate password strength based on its entropy? I know the formula based on the size of the symbol set and length of password, but would like to see some smalltalk code that fully implements this. -- ~JT

June 29, 2011

Re: [Pharo-project] Need help with ConfigurationOfCog

by Igor Stasenko

okay, problem is fixed. Thanks, Esteban -- Best regards, Igor Stasenko AKA sig.

June 29, 2011

Re: [Pharo-project] Silly tweet

by Igor Stasenko

On 29 June 2011 15:56, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Having an archive seems sufficient - those who need old versions for use or research can get them; they don't have to be clogging up the build server. Â Sounds great. > Indeed. If people would like to use older releases, they should look for another place, not for build server. Since build server are there to build & test bleeding-edge (under development) versions, but not ones which already released and years old. > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] > Sent: Wednesday, June 29, 2011 9:37 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Silly tweet > > On Jun 29, 2011, at 2:36 PM, Stephan Eggermont wrote: > >>> Starting to retire 1.2 builds from ci server now that 1.3 is getting ready: http://t.co/fC6w9EQ >> >> seem a bit silly. I assume (from Marcus' earlier post) that the retiring takes place sometime after the >> release of 1.3? > > We did it with 1.1... the problem is that the build server is getting really full if we keep everything. > And e.g. 1.2 did not change in weeks, so building it (unchanged) and running the tests (unchanged), > does that make sense? > > We can keep it if people need... but this time we switch servers in addition, so links will change anyway. > >> Providing these builds might lead to people using them, and in commercial >> development we mostly use released versions to base on. Within much time are we expected to migrate after >> a new release? >> > > Nobody removed the release from the archive... just the build server. > > Â Â Â Â Marcus > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > > -- Best regards, Igor Stasenko AKA sig.

June 29, 2011

Re: [Pharo-project] [Iliad] Iliad in Pharo 1.3

by Bernat Romagosa

Did it all but Iliad's still not behaving as it was in 1.2.1 or 1.1.1, still getting the "receiver of session is nil" error... Here's the stack trace: http://pastie.org/2140294 2011/6/29 Darius Clarke <socinian(a)gmail.com> > >ConfigurationOfShout and >ConfigurationOfOCompletion > > I just skipped those two lines (commented them out) and the rest > proceeded as expected. > > - Darius > -- Bernat Romagosa.

June 29, 2011

Re: [Pharo-project] Need help with ConfigurationOfCog

by Igor Stasenko

and i got same error when trying to load it. apparently there is a problem with spec 1.5. Here the version which i want to produce: version22: spec <version: '2.2' imports: #('1.5-baseline' )> spec for: #'common' do: [ spec blessing: #'development'. spec description: 'Merge with oscog-eem.88'. spec author: 'IgorStasenko'. spec timestamp: '6/29/2011 17:27'. spec package: 'FFI-Pools' with: 'FFI-Pools-eem.3'; package: 'SharedPool-Speech' with: 'SharedPool-Speech-dtl.2'; package: 'Balloon-Engine-Pools' with: 'Balloon-Engine-Pools-JB.2'; package: 'Alien-Core' with: 'Alien-Core-IgorStasenko.68'; package: 'Sound' with: 'Sound-StephaneDucasse.62'; package: 'VMConstruction-Plugins-OSProcessPlugin' with: 'VMConstruction-Plugins-OSProcessPlugin-dtl.27'; package: 'Cog' with: 'Cog-eem.44'; package: 'VMMaker-oscog' with: 'VMMaker-oscog-IgorStasenko.90'; package: 'Qwaq-VMProfiling-Plugins' with: 'Qwaq-VMProfiling-Plugins-JB.5'; package: 'CMakeVMMaker' with: 'CMakeVMMaker-sig.110'. ]. i don't see why it doesn't works. do you? -- Best regards, Igor Stasenko AKA sig.

June 29, 2011

Re: [Pharo-project] Need help with ConfigurationOfCog

by Igor Stasenko

On 29 June 2011 17:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Igor, you need to merge with my version of ConfigurationOfCog, that was already fixed. > But for cog we should use different version of osprocess plugin, see http://code.google.com/p/cog/issues/detail?id=6 > El 29/06/2011, a las 12:17p.m., Igor Stasenko escribiÃ³: > >> I updated the configuration to load new specs (ver 2.1), >> and everything worked before, but looks like after update of >> metacello, it does some checks and barks with error: >> Apparent loop in before/after dependency definitions >> >> any advice, what is wrong with it? >> >> The script to load stuff is following: >> >> Gofer new >> Â Â Â squeaksource: 'MetacelloRepository'; >> Â Â Â package: 'ConfigurationOfCog'; >> Â Â Â load. >> >> ((Smalltalk at: #ConfigurationOfCog) project >> Â Â Â version: '2.1') load. >> >> (Smalltalk saveAs: 'generator.image') ifFalse: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Smalltalk snapshot: false andQuit: true] >> >> its used on hudson server to build VMs, and apparently worked before. >> And i'm clueless what exactly wrong (not expert with metacello). >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

June 29, 2011