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

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

by Mariano Martinez Peck

> ConfigurationOfOmnibrowse DOES exist and has existed since more than one > year already. If you need an specific version, tell us which one exactly. > > I didn't tell the ConfigurationOf is missing. It is the file > OB-Standard-lr.541 that is in the ConfigurationOf > > I guess squeaksource lost again that verison. I have just publish it again. > > >> The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay >> happy with 1.2!" >> >> > No. The best thing you can do is to help the process. Nothing happens with > magic. Just keep asking and try to make it work. Report problems. And try to > test it before the release. > > Yep, that is true if I would try an esoteric use case. But I don't. Taking > a pharo 1.3 core from the CI server and doing > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfMetacello'; > load > ConfigurationOfMetacello project updateProject > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load > > 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. > > Norbert > -- Mariano http://marianopeck.wordpress.com

June 29, 2011

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

by Mariano Martinez Peck

On Wed, Jun 29, 2011 at 4:05 PM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > Hi Stefan, > > Thanks a lot, your script fails upon trying to load > ConfigurationOfOmniBrowser, ConfigurationOfShout > and ConfigurationOfOCompletion though, I tried using the metacello repo but > loading fails as follows: > > 'Could not resolve: OB-Standard [OB-Standard-lr.541] in > /home/nabax/Downloads/PharoCore-1.3/package-cache > http://www.squeaksource.com/PharoOB' > > Of cource it couldn't resolve it cos it's not there, why is it looking at > my local cache instead of squeaksource? o_O > > I guess squeaksource lost again that verison. I have just publish it again. > Cheers! > > 2011/6/28 Stefan Schmiedl <s(a)xss.de> > >> On Tue, 28 Jun 2011 17:15:52 +0200 >> Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: >> >> > Hi lists, >> > >> > I don't know whether this issue is Pharo's or Iliad's, so I'm writing to >> > both lists. >> > >> > I've just tried to pull Iliad 0.9.1 from the repos into a fresh Pharo >> 1.3 >> > image and I keep getting the error "receiver of session is nil" every >> time I >> > execute an action. If I click proceed in the debugger and manually >> refresh >> > the page, it works as it should. >> >> There were a few messages about that on the iliad list recently. >> >> >> > So I tried to install 0.9.2 instead, and now no actions work and nothing >> > happens when clicking an anchor. I tried the examples (counter, todo, >> etc) >> > and they're not working either. ILErrorHandler is in debugMode but I'm >> not >> > getting any error walkbacks either. >> >> When I tried this, I noticed that anchor URLS were missing a value >> for some parameter in their key. I followed the advice in Comment #2 >> of http://code.google.com/p/iliadproject/issues/detail?id=19 >> >> It took me a while to find out some nitty-gritty details on what >> goes with what, but here is what I _just now_ ended up as a reliable >> load script starting from PharoCore 1.3: >> >> >> >> Gofer new >> squeaksource: 'rb'; >> package: 'AST-Core'; >> package: 'AST-Semantic'; >> package: 'Refactoring-Core'; >> package: 'Refactoring-Environment'; >> package: 'Refactoring-Changes'; >> package: 'Refactoring-Critics'; >> package: 'Refactoring-Spelling'; >> package: 'Refactoring-Tests-Environment'; >> load. >> Gofer new >> squeaksource: 'PharoOB'; >> package: 'ConfigurationOfOmniBrowser'; >> package: 'ConfigurationOfShout'; >> package: 'ConfigurationOfOCompletion'; >> load. >> ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: #stable) >> load. >> ((Smalltalk at: #ConfigurationOfShout) project version: #stable) load. >> ((Smalltalk at: #ConfigurationOfOCompletion) project version: #stable) >> load. >> >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSandstoneDb'; >> load. >> (Smalltalk at: #ConfigurationOfSandstoneDb) project latestVersion load. >> Gofer new >> squeaksource: 'Fuel'; >> package: 'Fuel'; >> package: 'FuelTests'; >> package: 'FuelBenchmarks'; >> load. >> Gofer new >> squeaksource: 'SandstoneDb'; >> package: 'SandstoneDb'; >> package: 'SandstoneDbFuel'; >> package: 'SandstoneDbTests'; >> load. >> >> (Smalltalk at: #SDFileStore) serializer: (Smalltalk at: #SDFuelSerializer) >> new. >> >> >> Gofer new >> squeaksource: 'XMLSupport'; >> package: 'ConfigurationOfXMLSupport'; >> load. >> (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault. >> Gofer new >> squeaksource: 'IliadDev'; >> package: 'ConfigurationOfIliad'; >> load. >> ((Smalltalk at: #ConfigurationOfIliad) project version: '0.9.1.2') load. >> >> >> Gofer new >> directory: '/home/stefan/work/agweb/repo'; >> package: 'AgWeb'; >> package: 'Sport'; >> load. >> >> Workspace openFile: '/home/stefan/work/agweb/PharoCore-1.3/scratch.ws' >> >> >> >> >> In case you wonder about my local Sport package, it just contains a patch >> enabling Swazoo to run only on 127.0.0.1 instead on 0.0.0.0. The only >> thing >> that is missing here to make it perfect, is a patch in >> >> ILJsonHandler>>updateHead >> >> where you need to replace >> >> headElement := ILElement new. >> >> with >> >> headElement := ILHeadElement new. >> >> HTH, >> s. >> > > > > -- > Bernat Romagosa. > -- Mariano http://marianopeck.wordpress.com

June 29, 2011

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

by Bernat Romagosa

Hi Stefan, Thanks a lot, your script fails upon trying to load ConfigurationOfOmniBrowser, ConfigurationOfShout and ConfigurationOfOCompletion though, I tried using the metacello repo but loading fails as follows: 'Could not resolve: OB-Standard [OB-Standard-lr.541] in /home/nabax/Downloads/PharoCore-1.3/package-cache http://www.squeaksource.com/PharoOB' Of cource it couldn't resolve it cos it's not there, why is it looking at my local cache instead of squeaksource? o_O Cheers! 2011/6/28 Stefan Schmiedl <s(a)xss.de> > On Tue, 28 Jun 2011 17:15:52 +0200 > Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > > > Hi lists, > > > > I don't know whether this issue is Pharo's or Iliad's, so I'm writing to > > both lists. > > > > I've just tried to pull Iliad 0.9.1 from the repos into a fresh Pharo 1.3 > > image and I keep getting the error "receiver of session is nil" every > time I > > execute an action. If I click proceed in the debugger and manually > refresh > > the page, it works as it should. > > There were a few messages about that on the iliad list recently. > > > So I tried to install 0.9.2 instead, and now no actions work and nothing > > happens when clicking an anchor. I tried the examples (counter, todo, > etc) > > and they're not working either. ILErrorHandler is in debugMode but I'm > not > > getting any error walkbacks either. > > When I tried this, I noticed that anchor URLS were missing a value > for some parameter in their key. I followed the advice in Comment #2 > of http://code.google.com/p/iliadproject/issues/detail?id=19 > > It took me a while to find out some nitty-gritty details on what > goes with what, but here is what I _just now_ ended up as a reliable > load script starting from PharoCore 1.3: > > > > Gofer new > squeaksource: 'rb'; > package: 'AST-Core'; > package: 'AST-Semantic'; > package: 'Refactoring-Core'; > package: 'Refactoring-Environment'; > package: 'Refactoring-Changes'; > package: 'Refactoring-Critics'; > package: 'Refactoring-Spelling'; > package: 'Refactoring-Tests-Environment'; > load. > Gofer new > squeaksource: 'PharoOB'; > package: 'ConfigurationOfOmniBrowser'; > package: 'ConfigurationOfShout'; > package: 'ConfigurationOfOCompletion'; > load. > ((Smalltalk at: #ConfigurationOfOmniBrowser) project version: #stable) > load. > ((Smalltalk at: #ConfigurationOfShout) project version: #stable) load. > ((Smalltalk at: #ConfigurationOfOCompletion) project version: #stable) > load. > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSandstoneDb'; > load. > (Smalltalk at: #ConfigurationOfSandstoneDb) project latestVersion load. > Gofer new > squeaksource: 'Fuel'; > package: 'Fuel'; > package: 'FuelTests'; > package: 'FuelBenchmarks'; > load. > Gofer new > squeaksource: 'SandstoneDb'; > package: 'SandstoneDb'; > package: 'SandstoneDbFuel'; > package: 'SandstoneDbTests'; > load. > > (Smalltalk at: #SDFileStore) serializer: (Smalltalk at: #SDFuelSerializer) > new. > > > Gofer new > squeaksource: 'XMLSupport'; > package: 'ConfigurationOfXMLSupport'; > load. > (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault. > Gofer new > squeaksource: 'IliadDev'; > package: 'ConfigurationOfIliad'; > load. > ((Smalltalk at: #ConfigurationOfIliad) project version: '0.9.1.2') load. > > > Gofer new > directory: '/home/stefan/work/agweb/repo'; > package: 'AgWeb'; > package: 'Sport'; > load. > > Workspace openFile: '/home/stefan/work/agweb/PharoCore-1.3/scratch.ws' > > > > > In case you wonder about my local Sport package, it just contains a patch > enabling Swazoo to run only on 127.0.0.1 instead on 0.0.0.0. The only thing > that is missing here to make it perfect, is a patch in > > ILJsonHandler>>updateHead > > where you need to replace > > headElement := ILElement new. > > with > > headElement := ILHeadElement new. > > HTH, > s. > -- Bernat Romagosa.

June 29, 2011

Re: [Pharo-project] Silly tweet

by Schwab,Wilhelm K

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. ________________________________________ 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.

June 29, 2011

Re: [Pharo-project] [GS/SS Beta] zinc incompatibilities with gemstone

by Norbert Hartl

Am 29.06.2011 um 15:10 schrieb Philippe Marschall: > 2011/6/28 Paul DeBruicker <pdebruic(a)gmail.com>: >> ... >> symbol asSymbol > > <troll> > Every time you do this you admit that dynamic typing is a failure and > suggested types don't work for large scale development. > </troll> > It is not good but that's what you get if you develop in a system where #foo = 'foo' resolves to true and you try to deploy this in an environment where the same expressions resolves to false. It still means it needs to be fixed at the right place but I like to express that I can understand doing this. This striked me to death several times already. And zinc is still in the "make it work" phase. Norbert

June 29, 2011

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

by Norbert Hartl

Am 29.06.2011 um 15:28 schrieb Mariano Martinez Peck: > > On Wed, Jun 29, 2011 at 3:01 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 29.06.2011 um 12:19 schrieb 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. > > > > > Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get behind the first step using 1.3. There is a version in the ConfigurationOfOmnibrowser that does not exist or probably got lost in one of the many breadowns of squeaksource. Who is able to recover the file or upload it again? Eeverything I need to load depends somehow on omnibrowser. Probably you have a package cache on the ci server containing the package in request. Good for the test server. And finally everyone else does not seem to have a problem here. > > > Hi Norbert. #lastVersion MUST exist when loading Metacello. If it doesn't exist after loading it, then there is a problem. In such case, please report it. > I don't know it very well. I only know latestVersion to be present for sure. > ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly. > I didn't tell the ConfigurationOf is missing. It is the file OB-Standard-lr.541 that is in the ConfigurationOf > > The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!" > > > No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release. > Yep, that is true if I would try an esoteric use case. But I don't. Taking a pharo 1.3 core from the CI server and doing Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load ConfigurationOfMetacello project updateProject Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load 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. Norbert

June 29, 2011

Re: [Pharo-project] [GS/SS Beta] zinc incompatibilities with gemstone

by Esteban Lorenzano

Hi, I'm loading ConfigurationOfZincHTTPComponents from MetacelloRepository, and I'm loading #bleedingEdge version of zinc, but 1.0 is not loading either. Cheers, Esteban El 28/06/2011, a las 3:50p.m., Paul DeBruicker escribiÃ³: > Hi Esteban - > > > How are you loading Zinc into Gemstone? Were you using the metacello configuration on Squeaksource or something else? > > The reason I ask is all three issues you report were fixed/working at the start of June when I updated the port to what was current at the time. The Gemstone port is current up to Zinc-HTTP-SvenVanCaekenberghe.162 which is from May 19th. > > Let me know if loading via the metacello config is flawed and I'll update everything. Also check that you are loading version 1.1 of the project. It is the version referenced in #stable: > > I pasted the specific fixes below > > Thanks > Paul > > > > ZnUrl>>scheme: symbol > symbol isNil > ifTrue: [ scheme := nil ] > ifFalse: [ > (#(http https) includes: symbol asSymbol) > ifTrue: [ scheme := symbol asSymbol ] > ifFalse: [ (ZnUnknowScheme scheme: symbol) signal ] ] > > > ZnNetworkingUtils>>isProxySet > ^ HTTPSocket httpProxyServer isEmptyOrNil not > > > ZnNetworkingUtils class>> socketStreamTimeout > "Timeout in seconds for SocketStream IO" > > ^ 10

June 29, 2011

Re: [Pharo-project] Silly tweet

by Marcus Denker

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.

June 29, 2011

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

by Mariano Martinez Peck

On Wed, Jun 29, 2011 at 3:01 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 29.06.2011 um 12:19 schrieb 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. > > > > > Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get > behind the first step using 1.3. There is a version in the > ConfigurationOfOmnibrowser that does not exist or probably got lost in one > of the many breadowns of squeaksource. Who is able to recover the file or > upload it again? Eeverything I need to load depends somehow on omnibrowser. > Probably you have a package cache on the ci server containing the package in > request. Good for the test server. And finally everyone else does not seem > to have a problem here. > > Hi Norbert. #lastVersion MUST exist when loading Metacello. If it doesn't exist after loading it, then there is a problem. In such case, please report it. ConfigurationOfOmnibrowse DOES exist and has existed since more than one year already. If you need an specific version, tell us which one exactly. > The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay > happy with 1.2!" > > No. The best thing you can do is to help the process. Nothing happens with magic. Just keep asking and try to make it work. Report problems. And try to test it before the release. -- Mariano http://marianopeck.wordpress.com

June 29, 2011

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

by Norbert Hartl

Am 29.06.2011 um 12:19 schrieb 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. > Yes, but what is the plan after retiring ConfigurationOfPharo? I cannot get behind the first step using 1.3. There is a version in the ConfigurationOfOmnibrowser that does not exist or probably got lost in one of the many breadowns of squeaksource. Who is able to recover the file or upload it again? Eeverything I need to load depends somehow on omnibrowser. Probably you have a package cache on the ci server containing the package in request. Good for the test server. And finally everyone else does not seem to have a problem here. The best thing I can do is print myself a t-shirt "Too dumb for 1.3? stay happy with 1.2!" Norbert

June 29, 2011