March 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #646: 21472 Fulfil subclass responsibilities in DecoratorStream

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

There is a new Pharo build available! The status of the build #646 was: SUCCESS. The Pull Request #1007 was integrated: "21472 Fulfil subclass responsibilities in DecoratorStream" Pull request url: https://github.com/pharo-project/pharo/pull/1007 Issue Url: https://pharo.fogbugz.com/f/cases/21472 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 3, 2018

Re: [Pharo-dev] Integration deadlock?

by Denis Kudriashov

Ok. I always use instanceSide and classSide. So no problem in Calypso 2018-03-02 19:18 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I did a file out because the PR was totally literally broken. > I change theMetaClass and theNonMetaClass to classSide instanceSide > > On Fri, Mar 2, 2018 at 4:52 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > Did you really saw that Calypso was affected? > > I do not know how to review this changes now. The pull request is closed. > > And I doubt that I will be able to merge changes back (I do not know how > to > > do it). > > > > 2018-03-01 16:39 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> > >> I have a change that crosscuts calypso and iceberg. > >> I will produce a PR and each project should check because else I will > get > >> stuck > >> waiting in an integration deadlock. > >> > >> > >> https://pharo.fogbugz.com/f/cases/21459/Fixing-last-users- > of-theNonMetaclass > >> > > > >

March 3, 2018

[Pharo 7.0-dev] Build #645: 21329-PointrotateByabout-

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

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

March 3, 2018

[Pharo 7.0-dev] Build #644: 21468 Remove invalid comment in parseCompositionMappingFrom:

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

There is a new Pharo build available! The status of the build #644 was: SUCCESS. The Pull Request #1003 was integrated: "21468 Remove invalid comment in parseCompositionMappingFrom:" Pull request url: https://github.com/pharo-project/pharo/pull/1003 Issue Url: https://pharo.fogbugz.com/f/cases/21468 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 3, 2018

[Pharo 7.0-dev] Build #643: 21470 Fix lint issue in AnnouncementSet

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

There is a new Pharo build available! The status of the build #643 was: SUCCESS. The Pull Request #1005 was integrated: "21470 Fix lint issue in AnnouncementSet" Pull request url: https://github.com/pharo-project/pharo/pull/1005 Issue Url: https://pharo.fogbugz.com/f/cases/21470 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 3, 2018

[Pharo 7.0-dev] Build #642: 21463-reduce-unimplemented-messages-send-by-removing-dead-code

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

There is a new Pharo build available! The status of the build #642 was: SUCCESS. The Pull Request #998 was integrated: "21463-reduce-unimplemented-messages-send-by-removing-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/998 Issue Url: https://pharo.fogbugz.com/f/cases/21463 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 2, 2018

Re: [Pharo-dev] How to use git with gitfiletree

by Dale Henrichs

On 03/02/2018 10:14 AM, Sean P. DeNigris wrote: > Peter UhnÃ¡k wrote >> you mean that gitFILETREE:// would somehow use TONEL? > No, I mean a configuration file specifying tonel, like we currently have > .filetree files in every directory with filetree things in it. Embedding the > serialization format in a domain spec seems like a really bad idea. > Sean, You are right ... the plan is to have a file in the root of the tonel repository that specifies (at a minimum) the format of the repository ... similar to the .filetree file in FileTree repositories ... then we will have a format neutral url that can be used for tonel or filetree format repositories on disk and we will have an url inspired by gitfiletree:// that will be used to replace github:// in Metacello specs (github:// will continue to be supported) bu can be used with github, bitbucket, etc. So this is the plan, and now Esteban and I have to find the time to execute the plan:) Dale

March 2, 2018

Re: [Pharo-dev] Integration deadlock?

by Stephane Ducasse

I did a file out because the PR was totally literally broken. I change theMetaClass and theNonMetaClass to classSide instanceSide On Fri, Mar 2, 2018 at 4:52 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Did you really saw that Calypso was affected? > I do not know how to review this changes now. The pull request is closed. > And I doubt that I will be able to merge changes back (I do not know how to > do it). > > 2018-03-01 16:39 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> I have a change that crosscuts calypso and iceberg. >> I will produce a PR and each project should check because else I will get >> stuck >> waiting in an integration deadlock. >> >> >> https://pharo.fogbugz.com/f/cases/21459/Fixing-last-users-of-theNonMetaclass >> >

March 2, 2018

Re: [Pharo-dev] How to use git with gitfiletree

by Sean P. DeNigris

Peter UhnÃ¡k wrote > you mean that gitFILETREE:// would somehow use TONEL? No, I mean a configuration file specifying tonel, like we currently have .filetree files in every directory with filetree things in it. Embedding the serialization format in a domain spec seems like a really bad idea. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 2, 2018

[Isssue tracker] Name change: Manuscript

by Marcus Denker

Hello, Many of you are already wondering why you get spammed by âmanuscript.comâ. The reason is that Fog Creek Software changed the name of FogBugz to âManuscriptâ. The old URLs are still valid, *but* they started to send all emails with the manuscript name instead some time ago. We have started to change all websites that mention the domain, too, but for sure there will be cases where the old name will be used for quite some timeâ¦ Marcus

March 2, 2018