- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Released versions in Pharo Bootstrap

by Ben Coman

On 5 March 2018 at 23:51, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > On Mon, Mar 5, 2018 at 4:45 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> > wrote: > >> >> On Mon, Mar 5, 2018 at 4:38 PM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> But, "one single class" does not mean anything. Because it depends from >>> which branch/commitish you are loading it from... >>> >>> Can you explain better what is the problem because I am not getting it... >>> >>> In any case, independently of where is the burden, I want to veto any >>> new integration that may make future builds non-reproducible. Otherwise >>> this is a source of chaos and dead kittens. >>> >>> The problem is that actually if you have a git project with a stable and >> dev branch you will need: >> - One baseline on the stable branch with determined dependencies versions >> - One baseline on the dev branch with less restricted versions (for >> example 3.x.x) >> Then, when you release a new stable version by merging the development >> branch you need to edit the merge by hand to merge everything except the >> baseline. >> I think this is what Denis wants to avoid. >> > But in general, such merges need to be done only for major and minor >> releases. Not for a patch because you can do a hotfix. You create a new >> branch from master, then merge in in master and development when it's done. >> > > I still do not understand... Also I do not understand your usage of the > term "the merge". Can somebody give a **concrete** scenario? > > When you release a version, please do not move that version. You should > then create new versions, with new numbers and new code. But never touch > old versions with old numbers and old code. Like that I can download the > same old code using the same old number to get the old version whenever I > want :). > > You can try to do it with branches, tags, different repositories, or even > with zipfiles in mails. I don't care. Just don't modify releases and I'm > happy with it. > Not branches. Git has is no real difference between branches and tags, except that "by definition" branches move and tags don't. cheers -ben

March 7, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 26 February 2018

by Esteban Lorenzano

> On 7 Mar 2018, at 14:11, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On 5 March 2018 at 15:00, <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hello! > > This is my weekly ChangeLog, from 26 February 2018 to 4 March 2018. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=26/2/2018&to=4/3/2018 <http://log.smallworks.eu/web/search?from=26/2/2018&to=4/3/2018> > > ChangeLog > ========= > > 2 March 2018: > ------------- > > * I've been working on Iceberg UI. > I have first versions of: > > * repositories browser > * individual repository browser > * individual repository management browser > * commit window > * push window > * pull windows > > I'm not woking on fix a couple of problems on refreshing windows and defining how the pull will work (by default, > it will trigger a merge of the changes your are pulling into your image). > > > 1 March 2018: > ------------- > > * I made a new backport for 6.1, [case: 21344](https://pharo.fogbugz.com/f/cases/21344 <https://pharo.fogbugz.com/f/cases/21344>) > > enjoy > > > 28 February 2018: > ----------------- > > * Well... I spent an stupid amount of time to figure out why the latest VM for macOS was not including libgit2. > > Turns out, there was a "deploy filter" problem (two problems, in fact), that was making that all pharo flavours > were being uploaded to the file server and with same name so in fact, one flavour was being copied on top of the > other. And "lowcode VM", for example, does not includes libgi2. > > So, now that's fixed. You can start using latest VM again (which is the one that is signed) ;) > > Just to confirm, you mean downloads from here...? > http://files.pharo.org/vm/pharo-spur64/mac <http://files.pharo.org/vm/pharo-spur64/mac> > http://files.pharo.org/vm/pharo-spur32/mac <http://files.pharo.org/vm/pharo-spur32/mac> > Should we expect to see a lowcode tagged VM there? no :) first, I mean VMs from giles.pharo.org/get-files/70 <http://giles.pharo.org/get-files/70> they *point* to same VMs you refer, but the official download place is the one I said, where there is one stable and one latest. the place you link is the general repository where people can find an specific version, but is not the regular place. also, no about Lowcode. Lowcode VMs are experimental VMs and at the moment we do not distribute them as part of Pharo. If we decide to make them official, we will put them there, but so far people willing to experiment with them can download from the place were they are. cheers, Esteban ps: Iâm just describing our process. This is not wrote in stone (or STON ;) ) and it could change if we find there are good reasons to do it. > > cheers -ben

March 7, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 26 February 2018

by Ben Coman

On 5 March 2018 at 15:00, <estebanlm(a)gmail.com> wrote: > Hello! > > This is my weekly ChangeLog, from 26 February 2018 to 4 March 2018. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=26/2/2018&to=4/3/2018 > > ChangeLog > ========= > > 2 March 2018: > ------------- > > * I've been working on Iceberg UI. > I have first versions of: > > * repositories browser > * individual repository browser > * individual repository management browser > * commit window > * push window > * pull windows > > I'm not woking on fix a couple of problems on refreshing windows and > defining how the pull will work (by default, > it will trigger a merge of the changes your are pulling into your > image). > > > 1 March 2018: > ------------- > > * I made a new backport for 6.1, [case: 21344](https://pharo.fogbugz. > com/f/cases/21344) > > enjoy > > > 28 February 2018: > ----------------- > > * Well... I spent an stupid amount of time to figure out why the latest > VM for macOS was not including libgit2. > > Turns out, there was a "deploy filter" problem (two problems, in > fact), that was making that all pharo flavours > were being uploaded to the file server and with same name so in fact, > one flavour was being copied on top of the > other. And "lowcode VM", for example, does not includes libgi2. > > So, now that's fixed. You can start using latest VM again (which is > the one that is signed) ;) > Just to confirm, you mean downloads from here...? http://files.pharo.org/vm/pharo-spur64/mac http://files.pharo.org/vm/pharo-spur32/mac Should we expect to see a lowcode tagged VM there? cheers -ben

March 7, 2018

[Pharo 7.0-dev] Build #663: 21489 Cleanup TReplacementSequencedTest

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

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

March 7, 2018

Re: [Pharo-dev] PharoDays?

by Esteban Lorenzano

> On 28 Feb 2018, at 18:09, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi guys > > many people are asking when and where there will be PharoDays. > And we do not know. > We are looking for local organisers and else we do it at Lille. > Now what would be a good date? > > What about > 7-8 June? yes, is ok for me :) Esteban > > Stef >

March 7, 2018

[Pharo 7.0-dev] Build #662: 21489 Cleanup TReplacementSequencedTest

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

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

March 7, 2018

[Pharo 7.0-dev] Build #661: 21327-Integrate-the-new-version-of-Modular-Stateful-Traits

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

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

March 7, 2018

Re: [Pharo-dev] Pharo6 with Ubuntu and OSSubprocess/threaded heartbeat crashes and problems

by David T. Lewis

On Tue, Mar 06, 2018 at 11:49:14AM +0100, Sabine Manaa wrote: > Hi, > > I can report the following: > > The problem with the Buffer overflow remains also with OSProcess. > Also with the normal vm (https://get.pharo.org ). > > Summary: I have buffer overflow crashes with my application on Linux. > The same code runs without problems on MacOS and on Windows. > I have the same test data/database and do exactly the same. > > The problem occurs only after calling several times OSProcess/OSSubprocess. > This is the reason why I first had a suspicion that OSSubprocess is > responsible for the crashes. > > Can anyone tell me how to proceed to find the reason for the buffer > overflow? > There is no PharoDebug.log > > Help is very appreciated! > > This is the message when terminating: > > root@Pharo_ubuntu_16:/spf/build# ./pharo Pharo-Productive-SPF.image > --no-quit > > SmalltalkImageInstanceID class>>startUp*** buffer overflow detected ***: > /spf/build/pharo-vm/lib/pharo/5.0-201707201942/pharo terminated > What is class SmalltalkImageInstanceID? I have a Pharo 6.1 image, and I am running on Ubuntu. I loaded OSProcess to check this out, but I am not sure what that #startUp message is doing. Thanks, Dave

March 7, 2018

Re: [Pharo-dev] PharoDays?

by Myroslava Romaniuk

What about sometime mid-May? On 28 February 2018 at 19:10, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Or 24-25 of May > Or 31 - 1 June? > > On Wed, Feb 28, 2018 at 6:09 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > Hi guys > > > > many people are asking when and where there will be PharoDays. > > And we do not know. > > We are looking for local organisers and else we do it at Lille. > > Now what would be a good date? > > > > What about > > 7-8 June? > > > > Stef > > -- Ð Ð¿Ð¾Ð²Ð°Ð³Ð¾Ñ, ÐÐ¸ÑÐ¾ÑÐ»Ð°Ð²Ð° Ð Ð¾Ð¼Ð°Ð½ÑÐº.

March 6, 2018

[Pharo 7.0-dev] Build #660: 21508-Integrate-Calypso-0103

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

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

March 6, 2018