[Pharo-dev] OpenSSL 1.0.2 end of support from 1 Jan 2020
As per https://www.openssl.org/policies/releasestrat.html. My fork has a branch that builds with OpenSSL 1.1.1d with related minor fixes for one or some of the Pharo mvm. FWIW, that branch also updates libssh2 and libgit2 C libraries to newer versions. https://github.com/PierceNg/opensmalltalk-vm/tree/pierce_update3p Pierce
[Pharo-dev] [Pharo 8.0] Build #1074: 5369-stepToSendOrReturn-causes-an-error-on-a-dead-context
There is a new Pharo build available! The status of the build #1074 was: SUCCESS. The Pull Request #5370 was integrated: "5369-stepToSendOrReturn-causes-an-error-on-a-dead-context" Pull request url: https://github.com/pharo-project/pharo/pull/5370 Issue Url: https://github.com/pharo-project/pharo/issues/5369 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1074/
Re: [Pharo-dev] Are people using the Pharo VM builds from BinTray?
David T. Lewis wrote: > Is anyone using the Pharo VMs from BinTray? Otherwise if it's not a problem > for any Pharo users, I think the CI proprietors would like to turn off > some of their unnecessary builds to save resources. My understanding is > that the builds can easily be turned back on as needed in the future. I use them once in a while. Useful when triangulating issues Stephan
[Pharo-dev] [Pharo 8.0] Build #1073: Revert "5223-Remove-blueInk-packages-from-repository"
There is a new Pharo build available! The status of the build #1073 was: SUCCESS. The Pull Request #5377 was integrated: "Revert "5223-Remove-blueInk-packages-from-repository"" Pull request url: https://github.com/pharo-project/pharo/pull/5377 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1073/
[Pharo-dev] [Pharo 8.0] Build #1072: Improving comments of ffiCall: and ffiLibrary.
There is a new Pharo build available! The status of the build #1072 was: FAILURE. The Pull Request #5357 was integrated: "Improving comments of ffiCall: and ffiLibrary." Pull request url: https://github.com/pharo-project/pharo/pull/5357 Issue Url: https://github.com/pharo-project/pharo/issues/5352 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1072/
[Pharo-dev] [Pharo 8.0] Build #1071: Revert "Revert "[Perfs] x10 on method compiling with #deferFlushDuring
There is a new Pharo build available! The status of the build #1071 was: SUCCESS. The Pull Request #5374 was integrated: "Revert "Revert "[Perfs] x10 on method compiling with #deferFlushDuring" Pull request url: https://github.com/pharo-project/pharo/pull/5374 Issue Url: https://github.com/pharo-project/pharo/issues/5292 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1071/
Re: [Pharo-dev] Are people using the Pharo VM builds from BinTray?
On Fri, Dec 13, 2019 at 10:33:29AM +0100, Esteban Lorenzano wrote: > Hi, > > > On 12 Dec 2019, at 23:20, David T. Lewis wrote: > > > > Hi, > > > > There is an automated CI build for opensmalltalk VMs with artifacts for > > Pharo, Squeak, and Newspeak at https://bintray.com/opensmalltalk/vm/cog/. > > I suspect that the Pharo builds may be redundant with the official PharoVM > > distributions. > > Those VMs are also copied into our file sever and we take them from there. > > > Is anyone using the Pharo VMs from BinTray? Otherwise if it's not a problem > > for any Pharo users, I think the CI proprietors would like to turn off > > some of their unnecessary builds to save resources. My understanding is > > that the builds can easily be turned back on as needed in the future. > > I do not think we use the bintray, but we still use the osvm builds as our > standard distribution. > > > > > Fabio asked Marcel who asked me, so I am asking you :-) > > So I???m answering you so you can answer Marcel who can tell Fabio ;) > Thanks Esteban :-) Dave
[Pharo-dev] [ANN] EventRecorder legacy put online
Hi, For those who need the deprecated (and removed) GT-EventRecorder, I have put the original packages in pharo-contributions/EventRecorder (legacy branch). To load it, you just need to execute: Metacello new repository: 'github://pharo-contributions/EventRecorder:legacy'; baseline: 'EventRecorder'; load. This way you may continue loading Roassal2 (or others) until they fix the baseline :) (Btw, installation will still fail because Matrix has been removed… but this one was indeed deprecated in P7 (is replaced by Array2D), a problem you can overcome by executing Array2D subclass: #Matrix Previous to load Roassal2. I hope this solves the problems causes lasts weeks. Cheers, Esteban
Re: [Pharo-dev] Are people using the Pharo VM builds from BinTray?
Hi, > On 12 Dec 2019, at 23:20, David T. Lewis wrote: > > Hi, > > There is an automated CI build for opensmalltalk VMs with artifacts for > Pharo, Squeak, and Newspeak at https://bintray.com/opensmalltalk/vm/cog/. > I suspect that the Pharo builds may be redundant with the official PharoVM > distributions. Those VMs are also copied into our file sever and we take them from there. > Is anyone using the Pharo VMs from BinTray? Otherwise if it's not a problem > for any Pharo users, I think the CI proprietors would like to turn off > some of their unnecessary builds to save resources. My understanding is > that the builds can easily be turned back on as needed in the future. I do not think we use the bintray, but we still use the osvm builds as our standard distribution. > > Fabio asked Marcel who asked me, so I am asking you :-) So I’m answering you so you can answer Marcel who can tell Fabio ;) Esteban > > Thanks, > Dave > >
