December 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1050: 5329-Cleaning-DrTests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2019

Dec. 8, 2019

There is a new Pharo build available! The status of the build #1050 was: SUCCESS. The Pull Request #5331 was integrated: "5329-Cleaning-DrTests" Pull request url: https://github.com/pharo-project/pharo/pull/5331 Issue Url: https://github.com/pharo-project/pharo/issues/5329 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1049: 5311-DrTest-preview-overwrites-TestRunner-menu
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2019

Dec. 8, 2019

There is a new Pharo build available! The status of the build #1049 was: SUCCESS. The Pull Request #5333 was integrated: "5311-DrTest-preview-overwrites-TestRunner-menu" Pull request url: https://github.com/pharo-project/pharo/pull/5333 Issue Url: https://github.com/pharo-project/pharo/issues/5311 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1048: 5323-5320-Code-completion-failure-on-method-name
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2019

Dec. 6, 2019

There is a new Pharo build available! The status of the build #1048 was: SUCCESS. The Pull Request #5330 was integrated: "5323-5320-Code-completion-failure-on-method-name" Pull request url: https://github.com/pharo-project/pharo/pull/5330 Issue Url: https://github.com/pharo-project/pharo/issues/5323 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1047: Fixed issue #5271
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2019

Dec. 6, 2019

There is a new Pharo build available! The status of the build #1047 was: SUCCESS. The Pull Request #5327 was integrated: "Fixed issue #5271" Pull request url: https://github.com/pharo-project/pharo/pull/5327 Issue Url: https://github.com/pharo-project/pharo/issues/fix/ImproveExecutableComments… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About package deprecation
by vincent.blondeau＠lifeware.ch Dec. 6, 2019

Dec. 6, 2019

Hi all, As everyone knows, the BlueInk and GTRecorder packages have been removed from Pharo8.0 quite rapidly https://github.com/pharo-project/pharo/issues/5217. And it breaks the loading of other projects on Pharo8.0, like Roassal2. Some claims that those packages will not be deprecated because they are loadable as it from another repository. Why not? So, I tried. For BlueInk, no repository containing the sources has been indicated. And not repository exists on github. For the GTRecorder, the sources are there: https://github.com/pharo-contributions/EventRecorder, according to https://github.com/pharo-project/pharo/issues/5232. The problem is that the EventRecorder project does not contain exactly the same classes, the prefix has been changed from GT to ER. So, any reference to one of the classes of this project has to be changedâ¦ In particular, we had to make this change to make it load correctly: https://github.com/lifeware-sa/Roassal2/commit/78ce17bba98b89cb21a996cf8acaf 4e053ae082b (and we just have tried to load it so far). I think that not only Roassal is using those dependencies (see there https://github.com/search?o=desc <https://github.com/search?o=desc&q=GTEventCollector&s=indexed&type=Code> &q=GTEventCollector&s=indexed&type=Code and they are just public repos) and migrating them to the latest version of Pharo will be more painful since we need to fix the issue it immediately, or, wait that the maintainer of each project provide a fix to bypass the issues. Therefore, as we have a nice deprecation mechanism in our system, I suggest we use it so we can focus on stuff more important than writing tons of emails. I am then pushing in favor of the integration of this PR: https://github.com/pharo-project/pharo/pull/5257 so that we can have some time to solve the bugs. And I expect that those packages will be removed in Pharo 9.0. Now that everything is exposed, could the maintainers of the Pharo project take a clear decision concerning this topic? Also, we are expecting some justification on the undertaken action. Thanks, Vincent www.lifeware.ch <http://www.lifeware.ch>

1 0

[Pharo 8.0] Build #1040: [easyReview] fixing comment typos
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2019

Dec. 6, 2019

There is a new Pharo build available! The status of the build #1040 was: FAILURE. The Pull Request #5305 was integrated: "[easyReview] fixing comment typos" Pull request url: https://github.com/pharo-project/pharo/pull/5305 Issue Url: https://github.com/pharo-project/pharo/issues/typo Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

4 3

[Pharo 8.0] Build #1046: 5300-Traits-categories-are-not-updated-when-rebuilding-classes
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2019

Dec. 6, 2019

There is a new Pharo build available! The status of the build #1046 was: SUCCESS. The Pull Request #5301 was integrated: "5300-Traits-categories-are-not-updated-when-rebuilding-classes" Pull request url: https://github.com/pharo-project/pharo/pull/5301 Issue Url: https://github.com/pharo-project/pharo/issues/5300 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Building Pharo VM on Alpine Linux within Docker
by Pierce Ng Dec. 5, 2019

Dec. 5, 2019

I've put up a Dockerfile that builds the pharo.cog.spur.minheadless VM on Alpine Linux within Docker. This allows one to build said VM without having to first create an Alpine Linux installation such as through VirtualBox. https://github.com/pharo-contributions/Docker-Alpine/tree/master/vm.build This is a multi-stage Dockerfile. The Pharo VM is built in an Alpine Linux 'build' container. Then the VM files are copied into a fresh Alpine Linux Docker image. The resulting Pharo VM Docker image is ~14 MB. The output Docker image contains the Pharo VM only and is not runnable by itself. It is intended to be used as a base to build your own Docker image containing your application-specific Pharo image. Tested on Ubuntu 18.04 and MacOS Mojave. Pierce

2 2

[Pharo 8.0] Build #1045: [Cleaning] Array of Char is not a String
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2019

Dec. 5, 2019

There is a new Pharo build available! The status of the build #1045 was: FAILURE. The Pull Request #5322 was integrated: "[Cleaning] Array of Char is not a String" Pull request url: https://github.com/pharo-project/pharo/pull/5322 Issue Url: https://github.com/pharo-project/pharo/issues/cleanArrayStringConcat Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1044: 5314-Code-completion-issue-in-methods-with-syntax-error
by ci-pharo-ci-jenkins2＠inria.fr Dec. 5, 2019

Dec. 5, 2019

There is a new Pharo build available! The status of the build #1044 was: SUCCESS. The Pull Request #5318 was integrated: "5314-Code-completion-issue-in-methods-with-syntax-error" Pull request url: https://github.com/pharo-project/pharo/pull/5318 Issue Url: https://github.com/pharo-project/pharo/issues/5314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0