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

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Stephane Ducasse

Hi nicolas May be I'm naive and dull but indeed using branches is the way to go. We used that for Pillar. I can integrate fixes for the current stable in master and we are coding in a dedicated branch. I imagine that you know it, else you would not wish to use it. Git supports branches and usually good processes are - dev in local branches until it is ready and stable to merge in master - master is always the stable version and different builds can trigger and test different branches. So do I guess correctly that the VM code is not managed that way? This is surprising because all complex projects are managed that way with git. In fact good branching is one of the best features of git. Stef On Fri, Dec 22, 2017 at 5:35 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Hi Norbert, > having something integrated into the VM is not necessarily hard. > The pull request of Holger has been accepted fast enough. > So your point is maybe more about delivery of the binary artefacts. > > The pharo builds have been broken for some time but are now fixed, thanks to > Fabio/Christophe/Clement/Esteban! > I wish we can preserve the green status longer this time. > > The question is then about the release cycle which is well too loooonnng... > Continuous integration require GREEN builds, I wish we start using feature > branchs and reject half-ready PR > Then stability of head revision (cog) also matters. > Automated tests don't catch all problems. > Changing the garbage collector for example may trigger rare bugs... > > Maybe some essential (and limited) patch could be back-ported to well known > stable point. > But this can't happen with current ressources... > IOW help is welcome! > > Nicolas > > > 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> the week I return from holidays Iâm planing to get all that done (vm >> stuff). >> >> Esteban >> >> > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: >> > >> > I had that problem when openssl 1.1x library was present and SqueakSSL >> > uses 1.0.2 library. The patch is done by Holger and ready to be integrated. >> > But as always it is close to impossible to having something integrated in >> > the vm. >> > >> > Norbert >> > >> > >> >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: >> >> >> >> Hi, >> >> >> >> I used ZnClient to call an HTTPS URL and while it worked well in the >> >> past >> >> I now receive an "SSL Exception: connect failed [code:-5]". >> >> >> >> I guess the reason is an update of the URLs site to a server with newer >> >> TLS >> >> protocol (TLS 1.2 instead of TLS 1.0). >> >> >> >> Do we support that already in Pharo? >> >> >> >> Thx >> >> T. >> > >> >> >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Sean P. DeNigris

Nicolas Cellier wrote > The pharo builds have been broken for some time but are now fixed, thanks > to Fabio/Christophe/Clement/Esteban! THANK YOU ALL!!!!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Nicolas Cellier

Hi Norbert, having something integrated into the VM is not necessarily hard. The pull request of Holger has been accepted fast enough. So your point is maybe more about delivery of the binary artefacts. The pharo builds have been broken for some time but are now fixed, thanks to Fabio/Christophe/Clement/Esteban! I wish we can preserve the green status longer this time. The question is then about the release cycle which is well too loooonnng... Continuous integration require GREEN builds, I wish we start using feature branchs and reject half-ready PR Then stability of head revision (cog) also matters. Automated tests don't catch all problems. Changing the garbage collector for example may trigger rare bugs... Maybe some essential (and limited) patch could be back-ported to well known stable point. But this can't happen with current ressources... IOW help is welcome! Nicolas 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > the week I return from holidays Iâm planing to get all that done (vm > stuff). > > Esteban > > > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > I had that problem when openssl 1.1x library was present and SqueakSSL > uses 1.0.2 library. The patch is done by Holger and ready to be integrated. > But as always it is close to impossible to having something integrated in > the vm. > > > > Norbert > > > > > >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > >> > >> Hi, > >> > >> I used ZnClient to call an HTTPS URL and while it worked well in the > past > >> I now receive an "SSL Exception: connect failed [code:-5]". > >> > >> I guess the reason is an update of the URLs site to a server with newer > TLS > >> protocol (TLS 1.2 instead of TLS 1.0). > >> > >> Do we support that already in Pharo? > >> > >> Thx > >> T. > > > > >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Esteban Lorenzano

the week I return from holidays Iâm planing to get all that done (vm stuff). Esteban > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > > I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm. > > Norbert > > >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: >> >> Hi, >> >> I used ZnClient to call an HTTPS URL and while it worked well in the past >> I now receive an "SSL Exception: connect failed [code:-5]". >> >> I guess the reason is an update of the URLs site to a server with newer TLS >> protocol (TLS 1.2 instead of TLS 1.0). >> >> Do we support that already in Pharo? >> >> Thx >> T. >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Norbert Hartl

I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm. Norbert > Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > > Hi, > > I used ZnClient to call an HTTPS URL and while it worked well in the past > I now receive an "SSL Exception: connect failed [code:-5]". > > I guess the reason is an update of the URLs site to a server with newer TLS > protocol (TLS 1.2 instead of TLS 1.0). > > Do we support that already in Pharo? > > Thx > T.

Dec. 22, 2017

TLS Version supported by Zinc/Pharo

by Torsten Bergmann

Hi, I used ZnClient to call an HTTPS URL and while it worked well in the past I now receive an "SSL Exception: connect failed [code:-5]". I guess the reason is an update of the URLs site to a server with newer TLS protocol (TLS 1.2 instead of TLS 1.0). Do we support that already in Pharo? Thx T.

Dec. 22, 2017

[Pharo 7.0-dev] Build #396: 20886-Undeclared-RBMethodHasNoTimeStampRule-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #396 was: SUCCESS. The Pull Request #624 was integrated: "20886-Undeclared-RBMethodHasNoTimeStampRule-" Pull request url: https://github.com/pharo-project/pharo/pull/624 Issue Url: https://pharo.fogbugz.com/f/cases/20886 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 22, 2017

[Pharo 7.0-dev] Build #395: 20813-Improve-comments-of-ifNotNil-and-ifNotNilifNil

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #395 was: SUCCESS. The Pull Request #618 was integrated: "20813-Improve-comments-of-ifNotNil-and-ifNotNilifNil" Pull request url: https://github.com/pharo-project/pharo/pull/618 Issue Url: https://pharo.fogbugz.com/f/cases/20813 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 22, 2017

Re: [Pharo-dev] [ANN] Gemtalk Systems upgraded to Gold Membership

by Esteban Lorenzano

thanks! > On 22 Dec 2017, at 08:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The Pharo Consortium is very happy to announce that Gemtalk Systems > has upgraded to Gold Member status. > > About > - Gemtalk Systems: https://gemtalksystems.com > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > http://association.pharo.org >

Dec. 22, 2017

Re: [Pharo-dev] Updating CI plugins

by Guillermo Polito

Jenkins and slaves are up un running. Let's cross fingers hoping everything is ok :) Keep you updated On Fri, Dec 22, 2017 at 10:14 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Christophe is also taking benefit of this to update jenkins from 2.32.3 > LTS to 2.89.2 LTS > > On Fri, Dec 22, 2017 at 10:06 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi all, >> >> I'm updating CI plugins. *This will require a CI restart. *The >> corresponding issue is here: >> >> https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins >> >> The installed versions are the following: >> >> Workspace Cleanup Plugin 0.34 0.33 >> SCM API Plugin 2.2.6 2.2.1 >> Pipeline Utility Steps 1.5.1 1.4.1 >> Pipeline: API 2.24 2.20 >> Pipeline: Build Step 2.6 2.5.1 >> Pipeline: Declarative 1.2.5 1.1.9 >> Pipeline: Declarative Extension Points API 1.2.5 1.1.9 >> Pipeline: Groovy 2.41 2.40 >> Pipeline: Model API 1.2.5 1.1.9 >> Pipeline: Nodes and Processes 2.16 2.15 >> Pipeline: Shared Groovy Libraries 2.9 2.8 >> Pipeline: Stage Step 2.3 2.2 >> Pipeline: Stage Tags Metadata 1.2.5 1.1.9 >> Pipeline: Step API 2.14 2.12 >> Rebuilder 1.27 1.25 >> JUnit Plugin 1.23 1.21 >> Git client plugin 2.7.0 2.5.0 >> Git plugin 3.6.4 3.5.1 >> GitHub API Plugin 1.90 1.86 >> GitHub Branch Source Plugin 2.3.2 2.2.3 >> GitHub plugin 1.28.1 1.28.0 >> Copy Artifact Plugin 1.39 1.38.1 >> Credentials Plugin 2.1.16 2.1.15 >> Build Timeout 1.19 1.18 >> Conditional BuildStep 1.3.6 1.3.5 >> >> I'll keep you updated as soon as the update is finished. >> Guille >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 22, 2017