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

Re: [Pharo-users] I can't install Dataframe on Pharo 6.1

by Cyril Ferlicot

On jeu. 8 mars 2018 at 13:13, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Please your question on PolyMath mailing-list > > https://groups.google.com/forum/#!forum/scismalltalk > > or PolyMath Discord channel. > Hi Serge. This might be related to Iceberg, so it might concerne Pharo. > > On Thu, Mar 8, 2018 at 12:30 PM, hayatou via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > > >> >> ---------- Forwarded message ---------- >> From: hayatou <hayaty55(a)yahoo.fr> >> To: pharo-users(a)lists.pharo.org >> Cc: >> Bcc: >> Date: Thu, 8 Mar 2018 04:30:09 -0700 (MST) >> Subject: I can't install Dataframe on Pharo 6.1 >> Hi All, >> I've got an SSL Exception : connect failed [code:-5] when installing >> DataFrame >> (Metacello new >> baseline: 'DataFrame'; >> repository: 'github://PolyMathOrg/DataFrame'; >> load.) >> on pharo 6.1 on windows system >> What am I missing? >> hayatou >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

March 8, 2018

Re: [Pharo-users] I can't install Dataframe on Pharo 6.1

by Serge Stinckwich

Please your question on PolyMath mailing-list https://groups.google.com/forum/#!forum/scismalltalk or PolyMath Discord channel. On Thu, Mar 8, 2018 at 12:30 PM, hayatou via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: hayatou <hayaty55(a)yahoo.fr> > To: pharo-users(a)lists.pharo.org > Cc: > Bcc: > Date: Thu, 8 Mar 2018 04:30:09 -0700 (MST) > Subject: I can't install Dataframe on Pharo 6.1 > Hi All, > I've got an SSL Exception : connect failed [code:-5] when installing > DataFrame > (Metacello new > baseline: 'DataFrame'; > repository: 'github://PolyMathOrg/DataFrame'; > load.) > on pharo 6.1 on windows system > What am I missing? > hayatou > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

March 8, 2018

SSL Exception when installing DataFrame

by Hayatou Oumarou

Hi All,I've got an SSL Exception : connect failed [code:-5] when installing DataFrame (Metacello newÂ baseline: 'DataFrame';Â repository: 'github://PolyMathOrg/DataFrame';Â load.) on pharo 6.1 on windows systemWhat am I missing?cheers

March 8, 2018

Re: [Pharo-users] Bootstrap how to

by Hilaire

Le 08/03/2018 Ã 12:25, Stephane Ducasse a Ã©critÂ : > Thanks for sharing that with us. > Can you do a pull resquest for the changes you suggest? No I prefer to just paste it here, it is easier for me. Moreover those suggestions may need to be adjusted by whoever knows better. For example, "mkdir -p .." may be better replaced by something like "rm -rf toto; mkdir toto". I don't know > > I think that for the bootstrap we have to recreate the source each > time so we should recreate because it is depend on what > is in the boostrap. > Now this bootstrap is slow and you can reuse the result of our builds. It is ok, I just try to see at large how it is going on. Hilaire -- Dr. Geo http://drgeo.eu

March 8, 2018

I can't install Dataframe on Pharo 6.1

by hayatou

Hi All, I've got an SSL Exception : connect failed [code:-5] when installing DataFrame (Metacello new baseline: 'DataFrame'; repository: 'github://PolyMathOrg/DataFrame'; load.) on pharo 6.1 on windows system What am I missing? hayatou -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 8, 2018

Re: [Pharo-users] Bootstrap how to

by Hilaire

Le 08/03/2018 Ã 11:34, Hilaire a Ã©critÂ : > Now the image is building, will see next. The build process ended with this output, don't know if it is right: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: [ self Â Â Â handleArgument: Â Â Â Â Â Â (self arguments Â Â Â Â Â Â Â Â Â ifEmpty: [ '' ] Â Â Â Â Â Â Â Â Â ifNotEmpty: [ :arguments | arguments first ]) ] in [ [ self Â Â Â handleArgument: Â Â Â Â Â Â (self arguments Â Â Â Â Â Â Â Â Â ifEmpty: [ '' ] Â Â Â Â Â Â Â Â Â ifNotEmpty: [ :arguments | arguments first ]) ] Â Â Â on: Exit Â Â Â do: [ :exit | Â Â Â Â Â Â "If the command line is protected by password, we just exit the image because in non-headless mode the handleExit will let the image open. If the password protection is enabled, it is to avoid to let the access to the image." Â Â Â Â Â Â self class commandLinePasswordManager hasPasswordSet Â Â Â Â Â Â Â Â Â ifTrue: [ Smalltalk snapshot: false andQuit: true ]. Â Â Â Â Â Â ^ self handleExit: exit ] ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self... BlockClosure>>on:do: [ [ self Â Â Â handleArgument: Â Â Â Â Â Â (self arguments Â Â Â Â Â Â Â Â Â ifEmpty: [ '' ] Â Â Â Â Â Â Â Â Â ifNotEmpty: [ :arguments | arguments first ]) ] Â Â Â on: Exit Â Â Â do: [ :exit | Â Â Â Â Â Â "If the command line is protected by password, we just exit the image because in non-headless mode the handleExit will let the image open. If the password protection is enabled, it is to avoid to let the access to the image." Â Â Â Â Â Â self class commandLinePasswordManager hasPasswordSet Â Â Â Â Â Â Â Â Â ifTrue: [ Smalltalk snapshot: false andQuit: true ]. Â Â Â Â Â Â ^ self handleExit: exit ] ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ [ self... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... -- Dr. Geo http://drgeo.eu

March 8, 2018

Re: [Pharo-users] Bootstrap how to

by Stephane Ducasse

Thanks for sharing that with us. Can you do a pull resquest for the changes you suggest? I think that for the bootstrap we have to recreate the source each time so we should recreate because it is depend on what is in the boostrap. Now this bootstrap is slow and you can reuse the result of our builds. Stef On Thu, Mar 8, 2018 at 11:34 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > I give again a try to bootstrap (after my last summer fail). Here how far I > went: > > 1. Fetched the repo https://github.com/pharo-project/pharo. I have to fetch > a fresh one as updating my repo failed with the git command > pull/fetch/merge/reset hard does not work. Incredible how simple thinks does > not work simply with git. Do people really like git or pretend to because > everyone is using it. > > 2. Followed instructions to build a bootstrap. > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh > > The resulting image bootstrap-cache/bootstrap.image is built after 1 or 2 > hours. Its size is 3,4MB, when started there is only blank screen, I guess > it is the expected outcome. > > 3. Followed instructions to load pharo environment: > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 ./bootstrap/scripts/build.sh > > Several attempts were needed and the build.sh script is fragile and fail > when at the repeated attempts, some cleaning were needed. > > I suggest two things : > > 1. you add -p to your mkdir commands (in build.sh and get-vm.sh > scripts) as it make your script less fragile ! > 2. Also checking for the existence of the Pharo.source will avoid to > have duplicted uncessary downloaded source file version. > (Pharo.source1, Pharo.source2): > > if test ! -e PharoV60.sources > then > wget http://files.pharo.org/sources/PharoV60.sources > fi > > Now the image is building, will see next. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

March 8, 2018

Bootstrap how to

by Hilaire

I give again a try to bootstrap (after my last summer fail). Here how far I went: 1. Fetched the repo https://github.com/pharo-project/pharo. I have to fetch a fresh one as updating my repo failed with the git command pull/fetch/merge/reset hard does not work. Incredible how simple thinks does not work simply with git. Do people really like git or pretend to because everyone is using it. 2. Followed instructions to build a bootstrap. BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh The resulting image bootstrap-cache/bootstrap.image is built after 1 or 2 hours. Its size is 3,4MB, when started there is only blank screen, I guess it is the expected outcome. 3. Followed instructions to load pharo environment: Â BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 ./bootstrap/scripts/build.sh Several attempts were needed and the build.sh script is fragile and fail when at the repeated attempts, some cleaning were needed. I suggest two things : 1. you add -p to your mkdir commands (in build.sh and get-vm.sh scripts) as it make your script less fragile ! 2. Also checking for the existence of the Pharo.source will avoid to have duplicted uncessary downloaded source file version. (Pharo.source1, Pharo.source2): if test ! -e PharoV60.sources Â Â then Â Â Â Â Â Â wget http://files.pharo.org/sources/PharoV60.sources fi Now the image is building, will see next. Hilaire -- Dr. Geo http://drgeo.eu

March 8, 2018

Re: [Pharo-users] Pharo for MacOs 10.6.8?

by Esteban Lorenzano

> On 7 Mar 2018, at 22:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> get.pharo.org/30+vm <http://get.pharo.org/30+vm> > > And if you prefer a GUI over the command line, Launcher automatically > downloads images pretty far back (I just confirmed that 1.4 works on a MBP > 2017) and matches them up to the correct VM. One caveat: if the image is > very old (e.g. the 1.4 above), Launcher will hang when you try to run the > DLed image with a "determining correct VM for imageâ¦" dialog. The solution > is simple: create a `pharo.version` text file in the image folder with > `majorVersionNumber asString, minorVersionNumber asString` (e.g. for Pharo > 1.4 -> '14'). That will tell Launcher which VM to use. I happily use > Launcher for all my development images. HTH just... launcher itself will not work on those machines since is based in Pharo 6.1 ;) Esteban > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

March 8, 2018

Re: [Pharo-users] Pharo for MacOs 10.6.8?

by john pfersich

+1 Sent from my iPhone Encrypted email at jgpfersich(a)protonmail.com > On Mar 7, 2018, at 07:14, stefano franchi <stefano.franchi(a)gmail.com> wrote: > > Dear Marcus, > > thanks for the detailed answer. > > Let me say that my question did not in any ways imply that Pharo should assume the burden of maintaining current images and VMs on old machines. My goal was (is) simply to find out whether it was possible to repurpose a number old machines I have laying around by installing *old* versions of Pharo. And I now have a positive answer, having installed vm30 and verified that it works perfectly. > > In fact, I think adding a few lines to the website listing the last supported version for the major MacOs releases would be a valuable addition and nicely complement your commendable policy of keeping everything. > > All the best, > > Stefano > > >> On Tue, Mar 6, 2018 at 1:47 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 5 Mar 2018, at 20:16, stefano franchi <stefano.franchi(a)gmail.com> wrote: >>> >>> >>> >>> On Mon, Mar 5, 2018 at 11:28 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> Did you check >>>> >>>> http://get.pharo.org >>>> >>>> because we keep everything. >>>> >>> >>> >>> Apologies for not having stated my question more precisely. Indeed, I started from get.pharo.org, but the zeroconf script did not guess right. The app it downloaded crashes at startup. Then I saw the *long* list of versions available and had no idea where to begin. So my real question is: >>> >>> Does anyone know which among the many VMs available on http://get.pharo.org would work on a MacOs Powerbook Pro running 10.6.9? It was the latest 32 bit only machine Apple made, based on the Intel Core Duo (NOT the Intel Core 2 Duo that came out a few months later). >>> >> you could look for old VMs and downloads here: http://files.pharo.org/ >> >> But it is quite hard to for us (with our limited man power) to support old machines foreverâ¦ e.g the vm from that time should run, >> but at some point the VM gets improved and newer images require a newer VM as we want to actually use the features that >> new VMs provide. >> >> Keeping everything compatible in all possible directions (old images on new VMs, new image on old VMs â¦) puts quite some >> constraints on what you can do in futureâ¦ an maintaining new VMs for all possible old MacOS versions could soon just >> use up all our manpower. >> >> So this is not a simple problem to solve. Even very financially capable projects (like Mozilla) can not support old MacOS >> versions. And they spend 150K per *month* just on CI infrastructureâ¦ imagine if they decide to not support anything older >> then MaOS 10.9â¦ can we? should we? >> >> There are things to do on this front, but if I would spend effort the first thing I would work on is running *old* images on >> *new* VMs and explore what kind of abstraction would be needed to to that nicely and in a way that it can be maintained >> and in a way that all the needed code ( e.g. translation byte code from old to new) would be not part of the VM but >> part of the image. >> >> Making sure to run *current* images on old Machines can only be done by backporting the current VM to the old OS. >> This should be not that hard, worst case is that you need to combine some old OS related code with the rest of the new VM, >> but that should not be much. >> >> But one question: Considering what developer time costsâ¦ I am quite sure that it is cheaper to just buy a current Mac. >> >> Marcus >> > > > > -- > __________________________________________________ > Stefano Franchi > > stefano.franchi(a)gmail.com > http://stefano.cleinias.org

March 8, 2018