March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Installing Voyage ??

by Hilaire

Indeed, as I wrote in a previous email, this is how I got Voyage installed too in my Pharo4 devel environment, and it went fine too. Therefore the configuration should be ok. So this is weird. It should not be package cache related because I build image with a completely emptied build directory environment. So I am lost. As A matter of fact, I ran the installation script with a Pharo5 image, and now I get another error during the installation process. See bug log. The repo config is the git one, as described in the first email of this thread. Hilaire Le 25/03/2017 Ã 20:32, Esteban Lorenzano a Ã©crit : > I just did this: > > Gofer new > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60'; > configurationOf: 'VoyageMongo'; > loadStable. > > (which is the same to the one you did) > > in a fresh Pharo4 and it loaded fine. No UnQLite (which is correct). > Now, I guess Metacello looks for all packages in baseline even if after it will not download themâ¦ maybe you are seeing this lookup, but it shouldnât affect you. > > So, I guess there is a problem somewhere, but not in the config or the installation. Maybe a package cache problem? > > Esteban -- Dr. Geo http://drgeo.eu

March 25, 2017

Re: [Pharo-users] Installing Voyage ??

by Esteban Lorenzano

I just did this: Gofer new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60'; configurationOf: 'VoyageMongo'; loadStable. (which is the same to the one you did) in a fresh Pharo4 and it loaded fine. No UnQLite (which is correct). Now, I guess Metacello looks for all packages in baseline even if after it will not download themâ¦ maybe you are seeing this lookup, but it shouldnât affect you. So, I guess there is a problem somewhere, but not in the config or the installation. Maybe a package cache problem? Esteban > On 25 Mar 2017, at 19:51, Hilaire <hilaire(a)drgeo.eu> wrote: > > Ok I try this configuration, looks like he wants to install UnQLite. See > debug log. > > Hilaire > > > Le 25/03/2017 Ã 18:08, Esteban Lorenzano a Ã©crit : >> >> spec project: 'voyage' with: [ >> spec >> className: 'ConfigurationOfVoyageMongo'; >> repository: 'http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/mainâ >> <http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main%E2%80%99> ]. >> >> why this one is not fully functional? >> > > -- > Dr. Geo > http://drgeo.eu > <PharoDebug.log>

March 25, 2017

Re: [Pharo-users] Smalltalk on Stack Overflow Developers Survey 2017

by Stephane Ducasse

guille and santiago have a worker pool that is planned to serialize test running locally before commit based on taskIt. On Sat, Mar 25, 2017 at 7:56 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 25/03/17 18:29, serge.stinckwich(a)gmail.com wrote: > >> Nice ! But do you have a way to automatize this process ? ;-) >> > > How difficult can it be? We did it 18 years ago in java & delphi :) > > Stephan > > > >

March 25, 2017

Re: [Pharo-users] Installing Voyage ??

by Stephane Ducasse

Hilaire Yes you can load and old version and it should behave with the old behavior and potentially old bugs. You have the right. This is what a configuration gives you. Now esteban has the right to only add features and fix bugs in the maintained versions. And he could also consider that he does not want to help people using old versions because he is spending a lot of time improving the new ones. Apple, M$ and plenty of others do it this way and they have a lot more money than us. Stef On Sat, Mar 25, 2017 at 7:46 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > It is not a new project. It started with Pharo3. Then I see no reason > why I can't load the Voyage code of the time of Pharo4, with the > matching code version. It should be still there, is not the purpose of > Configuration? Or may be I misunderstand how version is working and its > purpose. > > Hilaire > > > Le 25/03/2017 Ã 18:08, Esteban Lorenzano a Ã©crit : > > then aside thatâ¦ one thing I do not understand is why you are develop a > > new project with an old (and not maintained anymore) Pharo version? > > Currently supported version is Pharo5, and even if Voyage is an external > > project, usually development follows Pharo stable versionâ¦ > > > > -- > Dr. Geo > http://drgeo.eu > > >

March 25, 2017

Re: [Pharo-users] Installing Voyage ??

by Esteban Lorenzano

> On 25 Mar 2017, at 19:46, Hilaire <hilaire(a)drgeo.eu> wrote: > > It is not a new project. It started with Pharo3. Then I see no reason > why I can't load the Voyage code of the time of Pharo4, with the > matching code version. It should be still there, is not the purpose of > Configuration? Or may be I misunderstand how version is working and its > purpose. Voyage works on Pharo 4, I was just wondering why you are still using 4 :) > > Hilaire > > > Le 25/03/2017 Ã 18:08, Esteban Lorenzano a Ã©crit : >> then aside thatâ¦ one thing I do not understand is why you are develop a >> new project with an old (and not maintained anymore) Pharo version? >> Currently supported version is Pharo5, and even if Voyage is an external >> project, usually development follows Pharo stable versionâ¦ >> > > -- > Dr. Geo > http://drgeo.eu > >

March 25, 2017

Re: [Pharo-users] Smalltalk on Stack Overflow Developers Survey 2017

by Stephan Eggermont

On 25/03/17 18:29, serge.stinckwich(a)gmail.com wrote: > Nice ! But do you have a way to automatize this process ? ;-) How difficult can it be? We did it 18 years ago in java & delphi :) Stephan

March 25, 2017

Re: [Pharo-users] Installing Voyage ??

by Hilaire

Ok I try this configuration, looks like he wants to install UnQLite. See debug log. Hilaire Le 25/03/2017 Ã 18:08, Esteban Lorenzano a Ã©crit : > > spec project: 'voyage' with: [ > spec > className: 'ConfigurationOfVoyageMongo'; > repository: 'http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/mainâ > <http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main%E2%80%99> ]. > > why this one is not fully functional? > -- Dr. Geo http://drgeo.eu

March 25, 2017

Re: [Pharo-users] Installing Voyage ??

by Hilaire

It is not a new project. It started with Pharo3. Then I see no reason why I can't load the Voyage code of the time of Pharo4, with the matching code version. It should be still there, is not the purpose of Configuration? Or may be I misunderstand how version is working and its purpose. Hilaire Le 25/03/2017 Ã 18:08, Esteban Lorenzano a Ã©crit : > then aside thatâ¦ one thing I do not understand is why you are develop a > new project with an old (and not maintained anymore) Pharo version? > Currently supported version is Pharo5, and even if Voyage is an external > project, usually development follows Pharo stable versionâ¦ > -- Dr. Geo http://drgeo.eu

March 25, 2017

Re: [Pharo-users] Build instructions for building threaded 6.0 VM on linux

by Alistair Grant

Hi Esteban & Ben, Thanks very much for your quick replies. Both versions are failing trying to build libssl.so, see error messages below. The build output is huge, so I've only included the final few lines (a but more in Ben's build). My familiarity with makefiles is bad enough, and have never touched cmake, so hopefully this is an easy fix... Any suggestions? Thanks again, Alistair Trying to build using Esteban's instructions: make[3]: *** No rule to make target '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'. Stop. make[3]: Leaving directory '/data/pharo-snap/akg-try/pharo-vm/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/git2.dir/all' failed make[2]: *** [CMakeFiles/git2.dir/all] Error 2 make[2]: Leaving directory '/data/pharo-snap/akg-try/pharo-vm/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' Makefile:127: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/data/pharo-snap/akg-try/pharo-vm/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' Makefile.libgit2:28: recipe for target '/data/pharo-snap/akg-try/pharo-vm/opensmalltalk-vm/.thirdparty-cache/linux/i386/lib/libgit2.so.0.23.0' failed make: *** [/data/pharo-snap/akg-try/pharo-vm/opensmalltalk-vm/.thirdparty-cache/linux/i386/lib/libgit2.so.0.23.0] Error 2 Trying to build using Ben's instructions: [ 96%] Building C object CMakeFiles/git2.dir/deps/zlib/infback.c.o [ 97%] Building C object CMakeFiles/git2.dir/deps/zlib/trees.c.o [ 97%] Building C object CMakeFiles/git2.dir/deps/zlib/adler32.c.o /data/pharo-snap/akg-try/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0/deps/zlib/adler32.c:173:15: warning: function declaration isn't a prototype [-Wstrict-prototypes] uLong ZEXPORT adler32_combine64(adler1, adler2, len2) ^ [ 98%] Building C object CMakeFiles/git2.dir/deps/zlib/inftrees.c.o [ 99%] Building C object CMakeFiles/git2.dir/deps/http-parser/http_parser.c.o make[3]: *** No rule to make target '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'. Stop. make[3]: Leaving directory '/data/pharo-snap/akg-try/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/git2.dir/all' failed make[2]: *** [CMakeFiles/git2.dir/all] Error 2 make[2]: Leaving directory '/data/pharo-snap/akg-try/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' Makefile:127: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/data/pharo-snap/akg-try/opensmalltalk-vm/build.linux32x86/third-party/libgit2-0.23.0' Makefile.libgit2:28: recipe for target '/data/pharo-snap/akg-try/opensmalltalk-vm/.thirdparty-cache/linux/i386/lib/libgit2.so.0.23.0' failed make: *** [/data/pharo-snap/akg-try/opensmalltalk-vm/.thirdparty-cache/linux/i386/lib/libgit2.so.0.23.0] Error 2 On 25 March 2017 at 18:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > something like this: > > $ git clone https://github.com/pharo-project/pharo-vm.git > $ cd pharo-vm/opensmalltalk-vm/build.linux32x86/pharo.cog.spur/build > $ ./mvm > > you will be ok as long as you provide the requirements (taken from travis): > > addons: > apt: > packages: > - debhelper > - devscripts > - libasound2-dev > - libssl-dev > - libfreetype6-dev > - libx11-dev > - libxext-dev > - gcc-multilib > - uuid-dev > - zip > # next ones are required for compiling libgit2 > - cmake > - libssh2-1-dev > - openssh-client > - openssh-server > - libtool > - automake > - autoconf > > > btw, I think we do not need anymore to provide libssh2 and openssh (because > we are building them too), but is not bad to have them :) > > cheers! > Esteban > > > On 25 Mar 2017, at 18:13, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Everyone, > > Would someone please point me to instructions on how to build the 6.0 > threaded VM for linux (Ubuntu). > > Thanks! > Alistair > >

March 25, 2017

Re: [Pharo-users] Voyage Timeout

by Stephane Ducasse

Hilaire you should think to move to Pharo 50. We closed around 1500 issues between pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60. Pharo 50 is really stable and working well Stef On Sat, Mar 25, 2017 at 8:58 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Sabine, > > Thanks to share your experience. > > My process is in 3 folds: > > 1. I build from bash and smalltalk scripts an application archive for > deployment, as I do for Dr.Geo (with configured image, VM, bootstart > data and bash scripts) > > 2. On the target host, the archive is deployed (unarchived), then bash > script launches the image for application installation (Mongo repo build > up and filled with data). The image is not saved. > > 3. The image is launched again with a configured smalltalk script, then > saved at the end. It should result in image to run the application, > hopefully for multiple running instance with load balancing (not there > yet). > > The 3. does not get well. As you suggested from your response, I will > try to use the 'eval' command handler instead of the 'st' command > handler and see how it goes. > > Thanks > > Hilaire > > > Le 25/03/2017 Ã 07:55, Sabine Manaa a Ã©crit : > > Hi Hilaire, > > > > I also use a command line handler for start in a new image with voyage . > > I start it like this on windows: > > > > .\...\Pharo5.0.image --no-default-preferences eval --save " > > MCRepositoryGroup default addRepository: (MCHttpRepository location: > > 'http://smalltalkhub.com/mc/Sabine/RKA24/main' user: 'Sabine' > > password: 'xxx').Metacello new smalltalkhubUser: 'Sabine' project: > > 'RKA24'; configuration: 'RKA24'; version: #development; load". > > > > Are you sure that the code in the file is executed? I had similar > > problems and asked in slack. Unfortunately the discussion is gone. It > > came out that some combinations of file configuration and command line > > commands do not work. I currently don't remember which (save?) but > > perhaps this brings you to an idea. > > > > Regards > > Sabine > > -- > Dr. Geo > http://drgeo.eu > > >

March 25, 2017