- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #260: 3316-Slots-more-tests-improve-comments-improve-Initialized-slots
by ci-pharo-ci-jenkins2＠inria.fr May 8, 2019

May 8, 2019

There is a new Pharo build available! The status of the build #260 was: SUCCESS. The Pull Request #3317 was integrated: "3316-Slots-more-tests-improve-comments-improve-Initialized-slots" Pull request url: https://github.com/pharo-project/pharo/pull/3317 Issue Url: https://github.com/pharo-project/pharo/issues/3316 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Problems trying to install pharo in centos 5.11
by Juan May 8, 2019

May 8, 2019

Hi all Today I was trying to install pharo, in a Centos release 5.11 (Final), but without success. the error message is with curl curl https://get.pharo.org/64 | bash curl: (51) SSL: certificate subject name 'cluster023.hosting.ovh.net' does not match target host name 'get.pharo.org' with wget, wget -O- https://get.pharo.org/64 | bash --2019-05-07 12:49:11 - https://get.pharo.org/64 Resolving get.pharo.org ... 164.132.235.17, 2001: 41d0: 301 :: 23 Connecting to get.pharo.org | 164.132.235.17 |: 443 ... connected. ERROR: certificate common name `cluster023.hosting.ovh.net 'does not match requested host name` get.pharo.org'. To connect to get.pharo.org insecurely, use `--no-check-certificate '. The SSL connection could not be established. I wonder if this is a known error, or is it a problem with my internet provider. One last question, for 5.xx centos there are prerequisites for installation ?. Any link or reference to install it? best regards Juan M. Diaz Cortez

4 5

IceCredentialsProvider sshCredentials ?
by Sven Van Caekenberghe May 8, 2019

May 8, 2019

I am trying to deploy on a server by building a Pharo image there. I want to use a readonly 'deploy user', using a specific certificate. I have been trying lots of things, but I cannot get where I want. So the user account is arbitrary, it just contains a key pair. If I add the key pair to the ssh-agent, I can clone my repository on the command line. Now I want to script this from Pharo. The script starts as follows: | remote location | remote := IceGitRemote url: 'ssh://git@bitbucket.myhost.be:1234/tthree/t3-pharo.git'. location := FileLocator localDirectory / 'iceberg' / remote projectName. IceRepositoryCreator new remote: remote; location: location; createRepository. On my development machine (macOS), this works fine. But this does not work on the Linux server, it says IceAuthenticationError: There was an authentication error while trying to execute the operation: . This happens usually because you didn't provide a valid set of credentials. You may fix this problem in different ways: 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line. 2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and add your public and private keys). 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) It does not matter if the ssh-agent has the certificate listed (ssh-add). Adding IceCredentialsProvider useCustomSsh: true. IceCredentialsProvider sshCredentials publicKey: '/home/t3/.ssh/id_deploy_pharo_ed25519.pub'; privateKey: '/home/t3/.ssh/id_deploy_pharo_ed25519' Does not make a difference. Is this supposed to work ? Maybe there is some other problem ? Sven

3 2

Dependencies between git projects ?
by Sven Van Caekenberghe May 7, 2019

May 7, 2019

I normally specify my dependencies between git projects like this: BaselineOfP3 >> baselineOf: spec <baseline> spec for: #common do: [ spec baseline: 'NeoJSON' with: [ spec repository: 'github://svenvc/NeoJSON:master/repository' ]. baseline: 'ZTimestamp' with: [ spec repository: 'github://svenvc/ztimestamp:master/repository' ]. spec baseline: 'Glorp' with: [ spec repository: 'github://pharo-rdbms/glorp:master/']. spec package: 'P3' with: [ spec requires: #('NeoJSON' 'ZTimestamp') ]. spec package: 'P3-Tests' with: [ spec requires: #('P3') ]. spec package: 'P3-Glorp' with: [ spec requires: #('P3' 'Glorp') ]. spec group: 'default' with: #('P3' 'P3-Tests'). spec group: 'core' with: #('P3'). spec group: 'glorp' with: #('P3-Glorp') ] Today I (finally, duh) realised that the github:// syntax actually requires a valid GitHub user. Since I do this with all my (public) projects, it obviously works (for others too), but still, is it actually 'wrong' ? Sven

3 3

[Pharo 8.0] Build #259: Typo RParseTreeSearcher -> RBParseTreeSearcher
by ci-pharo-ci-jenkins2＠inria.fr May 7, 2019

May 7, 2019

There is a new Pharo build available! The status of the build #259 was: SUCCESS. The Pull Request #3314 was integrated: "Typo RParseTreeSearcher -> RBParseTreeSearcher" Pull request url: https://github.com/pharo-project/pharo/pull/3314 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #258: 3300-Could-we-have-better-comment-for-SlotemitStore-
by ci-pharo-ci-jenkins2＠inria.fr May 7, 2019

May 7, 2019

There is a new Pharo build available! The status of the build #258 was: SUCCESS. The Pull Request #3309 was integrated: "3300-Could-we-have-better-comment-for-SlotemitStore-" Pull request url: https://github.com/pharo-project/pharo/pull/3309 Issue Url: https://github.com/pharo-project/pharo/issues/3300 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #257: update Calypso 0.16.4 which fixes broken tab selection
by ci-pharo-ci-jenkins2＠inria.fr May 7, 2019

May 7, 2019

There is a new Pharo build available! The status of the build #257 was: SUCCESS. The Pull Request #3308 was integrated: "update Calypso 0.16.4 which fixes broken tab selection" Pull request url: https://github.com/pharo-project/pharo/pull/3308 Issue Url: https://github.com/pharo-project/pharo/issues/updateCalypso0164 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #256: Use Calypso 0.16.3
by ci-pharo-ci-jenkins2＠inria.fr May 6, 2019

May 6, 2019

There is a new Pharo build available! The status of the build #256 was: FAILURE. The Pull Request #3298 was integrated: "Use Calypso 0.16.3" Pull request url: https://github.com/pharo-project/pharo/pull/3298 Issue Url: https://github.com/pharo-project/pharo/issues/updateCalypso0163 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Explaining Spec2 and why Bloc is on the roadmap
by ducasse May 4, 2019

May 4, 2019

Dear Pharoers We would like to explain what is Spec 2.0 and how Bloc is on the Pharo roadmap. Spec is a way to support a way to express and reuse application interaction logic. Spec was first developed by Benjamin van Ryseghem and others while supervised by StÃ©phane Ducasse. Over the years we cleaned Spec, but we never took the time to really revisit it, and Spec was never stressed outside the scope of Pharo tools (even if there is some people who used it in their projects, this was not the general case). There was a need to deeply rethink the way we express and reuse interaction application logic. Spec 2.0 revisits fundamentally Spec. The consortium wants to acknowledge the strong financial support of Schmidt in this new development. Here is a list of points we are working on to support companies to build modern applications with Pharo. - adding support for many widgets and at the same time improving existing widgets such as fasttable - adds much better layouts (we will deprecate the interpreter design) - introducing a new way to architecture an application: Spec20 introduces the notion of application to better handle resources and window flow - revisiting the internal logic of Spec (to remove useless parts and enhance the ones that works) - adding many tests In addition we want that Spec 2.0 is not tight anymore with Morphic. Why? Because we want to make sure that: - companies can deploy desktop applications - we can reuse all the tools logic of Pharo with new widgets sets such as Brick (widgets on top of Bloc) without having to rewrite everything. This is why Spec2.0 can optionally render using Gtk3.0. It also means that in the future we can have native widgets. Now that Bloc/Brick is finally reaching a point where it can be tried and eventually adopted, we want to make sure the transition to it will not force us to throw away the tools we developed last ten years. We think that Bloc needs some effort to clean and structure it and Spec2.0 gives the time to let Bloc and Brick mature. Also, we want to make sure that in the future we will be able to adopt other backends in case we decide it (Remember new now is old tomorrow and while Bloc/Brick is new and modern, it will not remain new and modern forever). Brick needs to be ready for Pharo consumption, and to make it possible we need to move the image to converge. With Spec 2.0, in future versions we will just need to define a new backend to get all our tools working. The Pharo Board

4 3

[Pharo 8.0] Build #255: add example: LazySlot
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2019

May 4, 2019

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

1 0