Re: [Pharo-dev] How to update currently used VM for PharoLauncher?

Stephan Eggermont-3 wrote > way to update my PharoLauncher to use > a non-stable version? On the Mac, I delete Launcher's VM for that Pharo image version and let Launcher DL a new one. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] SqueakSSL on Pharo 64bit/Win

Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm distribution. I guess this has to do with problems in building it. Anybody knows where the difficulties lie? Greetings Raffaello

[Pharo-dev] [Pharo 7.0-dev] Build #258: 20623-Tests-in-the-CI-should-say-the-Architecture-and-the-OS

There is a new Pharo build available! The status of the build #258 was: SUCCESS. The Pull Request #424 was integrated: "20623-Tests-in-the-CI-should-say-the-Architecture-and-the-OS" Pull request url: https://github.com/pharo-project/pharo/pull/424 Issue Url:

[Pharo-dev] How to update currently used VM for PharoLauncher?

I've noticed a few VM updates I want to use with PharoLauncher. What is the currently recommended way to update my PharoLauncher to use a non-stable version? Stephan

[Pharo-dev] [Pharo 7.0-dev] Build #257: 20632-Rename-PluggableSortFunction-to-CollatorBlockFunction

There is a new Pharo build available! The status of the build #257 was: SUCCESS. The Pull Request #430 was integrated: "20632-Rename-PluggableSortFunction-to-CollatorBlockFunction" Pull request url: https://github.com/pharo-project/pharo/pull/430 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #256: 20633-Update-Tonel-version

There is a new Pharo build available! The status of the build #256 was: SUCCESS. The Pull Request #431 was integrated: "20633-Update-Tonel-version" Pull request url: https://github.com/pharo-project/pharo/pull/431 Issue Url: https://pharo.fogbugz.com/f/cases/20633 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #255: 20629-wrong-FuelPlatform-Pharo-Core-package-loading

There is a new Pharo build available! The status of the build #255 was: SUCCESS. The Pull Request #429 was integrated: "20629-wrong-FuelPlatform-Pharo-Core-package-loading" Pull request url: https://github.com/pharo-project/pharo/pull/429 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #254: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

There is a new Pharo build available! The status of the build #254 was: FAILURE. The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" Pull request url: https://github.com/pharo-project/pharo/pull/426 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

It was a strange failure during the image cleanup, I guess it was related to the FuelPlatform-Pharo-Core package issue which is now fixed. -- Pavel 2017-11-03 13:48 GMT+01:00 Norbert Hartl : > Maybe that is the reason the status is considered a FAILURE? > > Norbert > > > Am

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

Maybe that is the reason the status is considered a FAILURE? Norbert > Am 03.11.2017 um 13:44 schrieb Torsten Bergmann : > > This build number is red: > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/ > >

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

This build number is red: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/ > Gesendet: Freitag, 03. November 2017 um 13:16 Uhr > Von: ci-pharo-ci-jenki...@inria.fr > An: pharo-dev@lists.pharo.org > Betreff: [Pharo-dev] [Pharo

[Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

There is a new Pharo build available! The status of the build #253 was: FAILURE. The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" Pull request url: https://github.com/pharo-project/pharo/pull/426 Issue Url:

Re: [Pharo-dev] Debugger "reporting" feature

cool. done. https://pharo.fogbugz.com/f/cases/20631/debugger-copy-stack-to-clipboard cheers -ben On Fri, Nov 3, 2017 at 1:03 AM, Stephane Ducasse wrote: > Can you open a bug entry? > > On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman wrote: > > sounds

[Pharo-dev] STOP THE WORLD FINISHED

Hi, Yesterday we finish the conversion to tonel, but I announced it just replying to the build that realises it. So I announce here officially and in his own mail :) You can resume contributions. This change should improve everybody's life but in particular windows users. I would like to

Re: [Pharo-dev] [update 6.0] #60519

That is so cool. I think everyone that uses pharo in production appreciates this very much! Norbert > Am 03.11.2017 um 09:57 schrieb Marcus Denker : > > > >> On 3 Nov 2017, at 09:50, Norbert Hartl wrote: >> >> Wow! Is there an explanation for

Re: [Pharo-dev] Tonel questions

I went too fast I removed everything and reforked recloned :) let us if it is working. On Fri, Nov 3, 2017 at 9:49 AM, Pavel Krivanek wrote: > > > 2017-11-03 9:39 GMT+01:00 Stephane Ducasse : >> >> Hi >> >> >> Should I download the latest Pharo

Re: [Pharo-dev] [update 6.0] #60519

> On 3 Nov 2017, at 09:50, Norbert Hartl wrote: > > Wow! Is there an explanation for that? If this is the pharo6 maintenance I > would be very lucky! > Yes, Pharo6 maintenance. The idea is to back port what makes sense and especially things that people find and need

Re: [Pharo-dev] [update 6.0] #60519

Wow! Is there an explanation for that? If this is the pharo6 maintenance I would be very lucky! Too many good things happening here, too less time to spent! Norbert > Am 03.11.2017 um 09:46 schrieb Stephane Ducasse : > > Super cool! > > > On Fri, Nov 3, 2017 at 9:43

Re: [Pharo-dev] Tonel questions

2017-11-03 9:39 GMT+01:00 Stephane Ducasse : > Hi > > > Should I download the latest Pharo 7 image? > Yes > > Should I fork again the Pharo-project? > no, just fetch and pull the latest version from the pharo-project/pharo repository, the development branch. Then

Re: [Pharo-dev] Tonel questions

On ven. 3 nov. 2017 at 09:40, Stephane Ducasse wrote: > Hi > > > Should I download the latest Pharo 7 image? > Yes > > Should I fork again the Pharo-project? > > Should I clone again the Pharo-project? > > Stef > > Hi, You should get a new Pharo 7 image and sync

Re: [Pharo-dev] [update 6.0] #60519

Super cool! On Fri, Nov 3, 2017 at 9:43 AM, Marcus Denker wrote: > In the build queue for Pharo6: > > 60519 > - > > 20622 Pharo 6.1 Cannot use FFIExternalStructures out of the box > https://pharo.fogbugz.com/f/cases/20622 > > 20611 leftover #logCr debug

[Pharo-dev] [update 6.0] #60519

In the build queue for Pharo6: 60519 - 20622 Pharo 6.1 Cannot use FFIExternalStructures out of the box https://pharo.fogbugz.com/f/cases/20622 20611 leftover #logCr debug logging in GLEmptyBrick>>#area https://pharo.fogbugz.com/f/cases/20611

[Pharo-dev] [Pharo 7.0-dev] Build #252: 20626-Fixing-Tests-in-CI

There is a new Pharo build available! The status of the build #252 was: SUCCESS. The Pull Request #425 was integrated: "20626-Fixing-Tests-in-CI" Pull request url: https://github.com/pharo-project/pharo/pull/425 Issue Url: https://pharo.fogbugz.com/f/cases/20626 Build Url:

[Pharo-dev] Tonel questions

Hi Should I download the latest Pharo 7 image? Yes Should I fork again the Pharo-project? Should I clone again the Pharo-project? Stef