- Pharo-dev - lists.pharo.org

[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

[Issue Tracker] lots of "auto close" happening

by Marcus Denker

Hello, As you might now, we automatically close issue tracker entries after 1 year of in-activity. Due to two factors (the job doing it not working since 1 month *and* now being 1 year after we started to sort issues for âhas to be fixed for pharo6 yes or noâ, we enter a period where *a lot* of issue get auto-closed. Everyone subscribed to the issue gets a mail and (of course!!) you should re-opne the issue tracker entry if the case still is relevant. Marcus

March 2, 2018

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

by Dale Henrichs

Esteban and I have agreed on some new url patterns (and changes to Tonel)Â that should make things easier, however, neither of us has had the time to implement the features ... so I guess I can only say that you need to be patient (and use whatever workarounds that apply) until these new features make it into production Dale On 03/02/2018 06:12 AM, Peter UhnÃ¡k wrote: > you mean that gitFILETREE:// would somehow use TONEL? That hardly > seems like a good idea. > > However there's gitlocal:// ... (which iirc handles both) but I think > that's iceberg specific. > > > Peter > > On Fri, Mar 2, 2018 at 3:08 PM, Sean P. DeNigris > <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > > Peter UhnÃ¡k wrote > > you would need something like gittonel://, which doesn't exist > > Shouldn't this be done via configuration (e.g. .filetree) to cover > cases > like `github://` where tonel/FT cannot be embedded in the URL? > > > > ----- > Cheers, > Sean > -- > Sent from: > http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> > >

March 2, 2018

[Pharo 7.0-dev] Build #641: 21460-ShiftClassInstaller-do-not-correctly-add-class-side-variables-into-the-hierarchy

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

There is a new Pharo build available! The status of the build #641 was: SUCCESS. The Pull Request #999 was integrated: "21460-ShiftClassInstaller-do-not-correctly-add-class-side-variables-into-the-hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/999 Issue Url: https://pharo.fogbugz.com/f/cases/21460 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 2, 2018

Re: [Pharo-dev] Integration deadlock?

by Denis Kudriashov

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