May 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] please test download for Pharo 6.0

by Alexandre Bergel

> as I wrote: Windows. > So 32 bits, there is no 64 bits Pharo VM for Windows yet (maybe with Pharo 7). Sorry, I did not checked... > BTW: thanks for the tech-talk. Was to late to join but I liked the video and PDF. Thanks :-) Alexandre > > Thanks > T. > > Gesendet: Mittwoch, 31. Mai 2017 um 23:19 Uhr > Von: "Alexandre Bergel" <alexandre.bergel(a)me.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] please test download for Pharo 6.0 > > Have you tried Pharo 32 or 64 bits? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 31, 2017, at 1:56 PM, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> wrote: > > Hi Esteban, > > I tried on a fresh Windows setup. What I tried: > - general image browsing, mousing around > - loading OS-Windows and run all my test to verify UFFI works fine > - loading Roassal and checked some examples > - switching FreeType on and using some non-standard TTF fonts > - retrieved contents from an HTTPS location using ZnEasy to verify SSL connections > - loaded and verified some packages like Teapot, WebBrowser, ... > > > anything worked fine. > > But using the console version > > PharoConsole.exe Pharo60.image --list > > or other command line options did not work in a shell. It opens the UI always instead of printing > something to stdout. Dont know if command line/stdout is now already supposed to work in Pharo 6 > (if not the PharoConsole.exe would not make sense to include yet). > > Also when git is not installed and one creates a repository it gives an error due to directory > creation - but this is a specific issue for Iceberg. > > Thanks > T. > > > > > Gesendet: Mittwoch, 31. Mai 2017 um 16:18 Uhr > Von: "Esteban Lorenzano" <estebanlm@gmail.com[mailto:estebanlm@gmail.com]> > An: "Pharo Development List" <pharo-dev@lists.pharo.org[mailto:pharo-dev@lists.pharo.org]> > Betreff: [Pharo-dev] please test download for Pharo 6.0 > > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download[http://pharo.org/STAGE.download] > > (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) > > cheers, > Esteban >

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Torsten Bergmann

Hi Alexandre, as I wrote: Windows. So 32 bits, there is no 64 bits Pharo VM for Windows yet (maybe with Pharo 7). Â BTW: thanks for the tech-talk. Was to late to join but I liked the video and PDF. Thanks T. Gesendet:Â Mittwoch, 31. Mai 2017 um 23:19 Uhr Von:Â "Alexandre Bergel" <alexandre.bergel(a)me.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] please test download for Pharo 6.0 Have you tried Pharo 32 or 64 bits? Â Alexandre --Â _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel Â http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. Â Â On May 31, 2017, at 1:56 PM, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> wrote:Â Hi Esteban, Â I tried on a fresh Windows setup. What I tried: Â - general image browsing, mousing around Â - loading OS-Windows and run all my test to verify UFFI works fine Â - loading Roassal and checked some examples Â - switching FreeType on and using some non-standard TTF fonts Â - retrieved contents from an HTTPS location using ZnEasy to verify SSL connections Â - loaded and verified some packages like Teapot, WebBrowser, ... Â anything worked fine. But using the console version Â Â PharoConsole.exe Pharo60.image --list Â or other command line options did not work in a shell. It opens the UI always instead of printing something to stdout. Dont know if command line/stdout is now already supposed to work in Pharo 6 (if not the PharoConsole.exe would not make sense to include yet). Also when git is not installed and one creates a repository it gives an error due to directory creation - but this is a specific issue for Iceberg. Thanks T. Â Â Gesendet:Â Mittwoch, 31. Mai 2017 um 16:18 Uhr Von:Â "Esteban Lorenzano" <estebanlm@gmail.com[mailto:estebanlm@gmail.com]> An:Â "Pharo Development List" <pharo-dev@lists.pharo.org[mailto:pharo-dev@lists.pharo.org]> Betreff:Â [Pharo-dev] please test download for Pharo 6.0 Hello,Â Â we are getting ready for release. please take a minute to review: Â http://pharo.org/STAGE.download[http://pharo.org/STAGE.download] Â (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) Â cheers, Esteban

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Alexandre Bergel

Have you tried Pharo 32 or 64 bits? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 31, 2017, at 1:56 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Esteban, > > I tried on a fresh Windows setup. What I tried: > - general image browsing, mousing around > - loading OS-Windows and run all my test to verify UFFI works fine > - loading Roassal and checked some examples > - switching FreeType on and using some non-standard TTF fonts > - retrieved contents from an HTTPS location using ZnEasy to verify SSL connections > - loaded and verified some packages like Teapot, WebBrowser, ... > > anything worked fine. > > But using the console version > > PharoConsole.exe Pharo60.image --list > > or other command line options did not work in a shell. It opens the UI always instead of printing > something to stdout. Dont know if command line/stdout is now already supposed to work in Pharo 6 > (if not the PharoConsole.exe would not make sense to include yet). > > Also when git is not installed and one creates a repository it gives an error due to directory > creation - but this is a specific issue for Iceberg. > > Thanks > T. > > > > Gesendet: Mittwoch, 31. Mai 2017 um 16:18 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] please test download for Pharo 6.0 > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> > > (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) > > cheers, > Esteban

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by phil＠highoctane.be

The default pharo-ui scripts are running PharoConsole.exe which is annoying because there is no filedialog allowing one to select an image. This is disrupting expectations. Furthermore PharoConsole is not really a console, it displays a dialog box instead of printing the usage to the console. Phil On Wed, May 31, 2017 at 7:56 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Esteban, > > I tried on a fresh Windows setup. What I tried: > - general image browsing, mousing around > - loading OS-Windows and run all my test to verify UFFI works fine > - loading Roassal and checked some examples > - switching FreeType on and using some non-standard TTF fonts > - retrieved contents from an HTTPS location using ZnEasy to verify SSL > connections > - loaded and verified some packages like Teapot, WebBrowser, ... > > anything worked fine. > > But using the console version > > PharoConsole.exe Pharo60.image --list > > or other command line options did not work in a shell. It opens the UI > always instead of printing > something to stdout. Dont know if command line/stdout is now already > supposed to work in Pharo 6 > (if not the PharoConsole.exe would not make sense to include yet). > > Also when git is not installed and one creates a repository it gives an > error due to directory > creation - but this is a specific issue for Iceberg. > > Thanks > T. > > > > *Gesendet:* Mittwoch, 31. Mai 2017 um 16:18 Uhr > *Von:* "Esteban Lorenzano" <estebanlm(a)gmail.com> > *An:* "Pharo Development List" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] please test download for Pharo 6.0 > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download > > (notice that zerconf download will not work because it is not yet movedâ¦ > so #stable will download current stable version which is 5.0) > > cheers, > Esteban >

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Alexandre Bergel

I was never aware that Athens was working on 64 bits. Yes, it is crashing... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 31, 2017, at 3:07 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 31 May 2017, at 18:39, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> But I tested Roassal (and Athens) in 64bits and they were working. >> What changed? > > I see that it is crashing. > But it was working, I swear it :) > > So I need to dig what changed to make it crash now :( > > Esteban > >> >> On 31 May 2017, at 18:33, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >>> Hi Volkert, >>> >>> Roassal does not work on Pharo 64-bits. The issue here is Athens. >>> >>> When Pharo 6 will be released, we will evaluate the options to make Roassal run on 64 bits. The option I see, is using Pompeii, the backend by Ronie that uses directly OpenGL. This works well on Pharo 64 bits. >>> >>> Someone see another option? >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On May 31, 2017, at 12:24 PM, volkert <volkert(a)nivoba.de <mailto:volkert@nivoba.de>> wrote: >>>> >>>> Downloaded Linux 64 Bit. >>>> Installed Roassal. >>>> Run Examples. >>>> VM crashed :-( >>>> BW, Volkert >>>> >>>> Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: >>>>>> On 31 May 2017, at 17:46, Peter Uhnak <i.uhnak(a)gmail.com> <mailto:i.uhnak@gmail.com> wrote: >>>>>> >>>>>> I find the Windows distribution a bit chaotic as all the files (vm, vm libs, image, sources) are in the same folder. Maybe there were issues with using shortcuts? Because then launching the image will also create pharo-local in the folder (and any other file that image writes to imageDirectory), so it could be more chaos for a new user. >>>>> yes, it has been like that since some time and we need to change itâ¦ but not now for release :) >>>>> >>>>>> The linux distro contains sources twice >>>>>> 1) pharo6.0/shared/PharoV60.sources >>>>>> 2) pharo6.0/bin/PharoV60.sources >>>>> yeah, thatâs also a problem from one-click daysâ¦ maybe I can fix that/ >>>>> >>>>> Esteban >>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: >>>>>>> Hello, >>>>>>> >>>>>>> we are getting ready for release. >>>>>>> please take a minute to review: >>>>>>> >>>>>>> http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> <http://pharo.org/STAGE.download> <http://pharo.org/STAGE.download> >>>>>>> >>>>>>> (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) >>>>>>> >>>>>>> cheers, >>>>>>> Esteban >>>> >>> >

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Esteban Lorenzano

> On 31 May 2017, at 18:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > But I tested Roassal (and Athens) in 64bits and they were working. > What changed? I see that it is crashing. But it was working, I swear it :) So I need to dig what changed to make it crash now :( Esteban > > On 31 May 2017, at 18:33, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > >> Hi Volkert, >> >> Roassal does not work on Pharo 64-bits. The issue here is Athens. >> >> When Pharo 6 will be released, we will evaluate the options to make Roassal run on 64 bits. The option I see, is using Pompeii, the backend by Ronie that uses directly OpenGL. This works well on Pharo 64 bits. >> >> Someone see another option? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On May 31, 2017, at 12:24 PM, volkert <volkert(a)nivoba.de <mailto:volkert@nivoba.de>> wrote: >>> >>> Downloaded Linux 64 Bit. >>> Installed Roassal. >>> Run Examples. >>> VM crashed :-( >>> BW, Volkert >>> >>> Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: >>>>> On 31 May 2017, at 17:46, Peter Uhnak <i.uhnak(a)gmail.com> <mailto:i.uhnak@gmail.com> wrote: >>>>> >>>>> I find the Windows distribution a bit chaotic as all the files (vm, vm libs, image, sources) are in the same folder. Maybe there were issues with using shortcuts? Because then launching the image will also create pharo-local in the folder (and any other file that image writes to imageDirectory), so it could be more chaos for a new user. >>>> yes, it has been like that since some time and we need to change itâ¦ but not now for release :) >>>> >>>>> The linux distro contains sources twice >>>>> 1) pharo6.0/shared/PharoV60.sources >>>>> 2) pharo6.0/bin/PharoV60.sources >>>> yeah, thatâs also a problem from one-click daysâ¦ maybe I can fix that/ >>>> >>>> Esteban >>>> >>>>> Peter >>>>> >>>>> >>>>> On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: >>>>>> Hello, >>>>>> >>>>>> we are getting ready for release. >>>>>> please take a minute to review: >>>>>> >>>>>> http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> <http://pharo.org/STAGE.download> <http://pharo.org/STAGE.download> >>>>>> >>>>>> (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) >>>>>> >>>>>> cheers, >>>>>> Esteban >>> >>

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Torsten Bergmann

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Esteban A. Maringolo

I downloaded Windows (32 bit only). Played around and had no visible issues so I ran the tests and got some errors and failures (I don't know whether they're expected): 14425 run, 14342 passes, 29 skipped, 57 expected failures, 17 failures, 9 errors, 0 unexpected passes Failures: MCSnapshotBrowserTest>>#testNoSelection MCWorkingCopyTest>>#testSimpleMerge MCStWriterTest>>#testInitializerDefinition MetacelloRepositorySqueakCommonTestCase>>#testDirectoryRepository MetacelloRepositorySqueakCommonTestCase>>#testAsRepositorySpecFor MCSnapshotTest>>#testCreation MCWorkingCopyTest>>#testOptimizedLoad MCSnapshotBrowserTest>>#testClassSelected ReleaseTest>>#testMethodsWithUnboundGlobals MCSnapshotBrowserTest>>#testCategorySelected MCWorkingCopyTest>>#testRepeatedMerge MCSnapshotBrowserTest>>#testClassSideClassSelected MCPatchTest>>#testPatchContents ZnClientTests>>#testIfFailNotFound MCWorkingCopyTest>>#testSelectiveBackport MCWorkingCopyTest>>#testSnapshotAndLoad GLMRubricTextMorphicTest>>#testPastingUpdatesTextPort Errors: MCPackageTest>>#testUnloadWithAdditionalTracking MCSnapshotBrowserTest>>#testMethodIsCleared MCSnapshotBrowserTest>>#testMethodSelected MCSnapshotBrowserTest>>#testProtocolIsCleared MCSnapshotBrowserTest>>#testProtocolSelected MCStWriterTest>>#testClassMethodDefinition MCStWriterTest>>#testMethodDefinition MCWorkingCopyTest>>#testBackport MCFileInTest>>#testStWriter Best regards! Esteban A. Maringolo 2017-05-31 13:39 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > But I tested Roassal (and Athens) in 64bits and they were working. > What changed? > > On 31 May 2017, at 18:33, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Volkert, > > Roassal does not work on Pharo 64-bits. The issue here is Athens. > > When Pharo 6 will be released, we will evaluate the options to make Roassal > run on 64 bits. The option I see, is using Pompeii, the backend by Ronie > that uses directly OpenGL. This works well on Pharo 64 bits. > > Someone see another option? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 31, 2017, at 12:24 PM, volkert <volkert(a)nivoba.de> wrote: > > Downloaded Linux 64 Bit. > Installed Roassal. > Run Examples. > VM crashed :-( > > BW, Volkert > > Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: > > On 31 May 2017, at 17:46, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > I find the Windows distribution a bit chaotic as all the files (vm, vm libs, > image, sources) are in the same folder. Maybe there were issues with using > shortcuts? Because then launching the image will also create pharo-local in > the folder (and any other file that image writes to imageDirectory), so it > could be more chaos for a new user. > > yes, it has been like that since some time and we need to change itâ¦ but not > now for release :) > > The linux distro contains sources twice > 1) pharo6.0/shared/PharoV60.sources > 2) pharo6.0/bin/PharoV60.sources > > yeah, thatâs also a problem from one-click daysâ¦ maybe I can fix that/ > > Esteban > > Peter > > > On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: > > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> > > (notice that zerconf download will not work because it is not yet movedâ¦ so > #stable will download current stable version which is 5.0) > > cheers, > Esteban > > >

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Esteban Lorenzano

But I tested Roassal (and Athens) in 64bits and they were working. What changed? > On 31 May 2017, at 18:33, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Volkert, > > Roassal does not work on Pharo 64-bits. The issue here is Athens. > > When Pharo 6 will be released, we will evaluate the options to make Roassal run on 64 bits. The option I see, is using Pompeii, the backend by Ronie that uses directly OpenGL. This works well on Pharo 64 bits. > > Someone see another option? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On May 31, 2017, at 12:24 PM, volkert <volkert(a)nivoba.de> wrote: >> >> Downloaded Linux 64 Bit. >> Installed Roassal. >> Run Examples. >> VM crashed :-( >> BW, Volkert >> >>> Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: >>>>> On 31 May 2017, at 17:46, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>>>> >>>>> I find the Windows distribution a bit chaotic as all the files (vm, vm libs, image, sources) are in the same folder. Maybe there were issues with using shortcuts? Because then launching the image will also create pharo-local in the folder (and any other file that image writes to imageDirectory), so it could be more chaos for a new user. >>>> yes, it has been like that since some time and we need to change itâ¦ but not now for release :) >>>> >>>> The linux distro contains sources twice >>>> 1) pharo6.0/shared/PharoV60.sources >>>> 2) pharo6.0/bin/PharoV60.sources >>> yeah, thatâs also a problem from one-click daysâ¦ maybe I can fix that/ >>> >>> Esteban >>> >>>> Peter >>>> >>>> >>>> On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: >>>>> Hello, >>>>> >>>>> we are getting ready for release. >>>>> please take a minute to review: >>>>> >>>>> http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> >>>>> >>>>> (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) >>>>> >>>>> cheers, >>>>> Esteban >> >

May 31, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Blondeau Vincent

My review: - For Pharo x64: Version 6.0 for OS X, GNU/Linux, and Windows -> Version 6.0 for OS X and GNU/Linux. - The VM and .sources are the same as for Pharo5. -> The VM and .sources are the same as for Pharo 6. - http://files.pharo.org/image/70/latest.zip -> dead link (but this is expected ;)) Thanks Esteban! Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de volkert EnvoyÃ© : mercredi 31 mai 2017 18:25 Ã : pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] please test download for Pharo 6.0 * Downloaded Linux 64 Bit. * Installed Roassal. * Run Examples. * VM crashed :-( BW, Volkert Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: On 31 May 2017, at 17:46, Peter Uhnak <i.uhnak(a)gmail.com><mailto:i.uhnak@gmail.com> wrote: I find the Windows distribution a bit chaotic as all the files (vm, vm libs, image, sources) are in the same folder. Maybe there were issues with using shortcuts? Because then launching the image will also create pharo-local in the folder (and any other file that image writes to imageDirectory), so it could be more chaos for a new user. yes, it has been like that since some time and we need to change itâ¦ but not now for release :) The linux distro contains sources twice 1) pharo6.0/shared/PharoV60.sources 2) pharo6.0/bin/PharoV60.sources yeah, thatâs also a problem from one-click daysâ¦ maybe I can fix that/ Esteban Peter On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: Hello, we are getting ready for release. please take a minute to review: http://pharo.org/STAGE.download <http://pharo.org/STAGE.download><http://pharo.org/STAGE.download> (notice that zerconf download will not work because it is not yet movedâ¦ so #stable will download current stable version which is 5.0) cheers, Esteban !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

May 31, 2017