[Pharo-dev] [Pharo 7.0-dev] Build #1153: 22284-Freeze-during-startup

There is a new Pharo build available! The status of the build #1153 was: SUCCESS. The Pull Request #1659 was integrated: "22284-Freeze-during-startup" Pull request url: https://github.com/pharo-project/pharo/pull/1659 Issue Url: https://pharo.fogbugz.com/f/cases/22284 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #1152: 22291-Deprecation-of-OSEnvironment-default-should-have-a-rewrite-tool

There is a new Pharo build available! The status of the build #1152 was: SUCCESS. The Pull Request #1665 was integrated: "22291-Deprecation-of-OSEnvironment-default-should-have-a-rewrite-tool" Pull request url: https://github.com/pharo-project/pharo/pull/1665 Issue Url:

Re: [Pharo-dev] Problem with Iceberg and Working Branches

Guillermo has found a bug in Iceberg that is slotted to be fixed at the next update, and has provided a temporary workaround. I have to final notes about the "merge" method: 1. After the merge, you must explore the packages and reload any that you've been working on in order to have classes of

[Pharo-dev] [Pharo 7.0-dev] Build #1151: 22289-Pharo-bootstrap-stopped-to-be-repository-agnostic

There is a new Pharo build available! The status of the build #1151 was: SUCCESS. The Pull Request #1664 was integrated: "22289-Pharo-bootstrap-stopped-to-be-repository-agnostic" Pull request url: https://github.com/pharo-project/pharo/pull/1664 Issue Url:

Re: [Pharo-dev] Problem with Iceberg and Working Branches

> On 1 Aug 2018, at 14:10, Guillermo Polito wrote: > > > > On Wed, Aug 1, 2018 at 2:02 PM Eric Gade > wrote: > Every week some tenths of pull requests are integrated in Pharo, so loading > the Pharo7 image of today will give you an image compleeetely different

Re: [Pharo-dev] Problem with Iceberg and Working Branches

On Wed, Aug 1, 2018 at 2:02 PM Eric Gade wrote: > Every week some tenths of pull requests are integrated in Pharo, so >> loading the Pharo7 image of today will give you an image compleeetely >> different from the one you worked with one week ago. >> > > This is something I'm used to from the

Re: [Pharo-dev] Problem with Iceberg and Working Branches

> > Every week some tenths of pull requests are integrated in Pharo, so > loading the Pharo7 image of today will give you an image compleeetely > different from the one you worked with one week ago. > This is something I'm used to from the non-Pharo Git world. Normally I would do what it called

Re: [Pharo-dev] Problem with Iceberg and Working Branches

Ah, just in case I add to what I say: this particular tricky scenario is specific for Pharo and contributing to Pharo. Any third party project/library will not have the constraints described in my previous email. On Wed, Aug 1, 2018 at 1:48 PM Guillermo Polito wrote: > Hi! > > On Wed, Aug 1,

Re: [Pharo-dev] Problem with Iceberg and Working Branches

Hi! On Wed, Aug 1, 2018 at 1:30 PM Eric Gade wrote: > I have already mentioned some of this on Discord so forgive me for being > redundant if you've seen it. > > I'm having problems loading into the latest P7 images from Launcher a > working branch of Pharo that I have forked. I perform the

[Pharo-dev] [Pharo 7.0-dev] Build #1150: 21852-Should-add-a-nice-comment-to-FileStream-to-help-migration

There is a new Pharo build available! The status of the build #1150 was: SUCCESS. The Pull Request #1654 was integrated: "21852-Should-add-a-nice-comment-to-FileStream-to-help-migration" Pull request url: https://github.com/pharo-project/pharo/pull/1654 Issue Url:

[Pharo-dev] Problem with Iceberg and Working Branches

I have already mentioned some of this on Discord so forgive me for being redundant if you've seen it. I'm having problems loading into the latest P7 images from Launcher a working branch of Pharo that I have forked. I perform the following steps: 1. "Repair" the missing local repository for Pharo

[Pharo-dev] [Pharo 7.0-dev] Build #1149: 22288-The-changes-in-21855-affect-old-extension-methods-that-are-not-case-equals

There is a new Pharo build available! The status of the build #1149 was: SUCCESS. The Pull Request #1663 was integrated: "22288-The-changes-in-21855-affect-old-extension-methods-that-are-not-case-equals" Pull request url: https://github.com/pharo-project/pharo/pull/1663 Issue Url:

Re: [Pharo-dev] CI Issue on PR

Just FYI, Pablo has answered in the PR. In short, adding new packages means adding them also in the baselines, otherwise metacello does not load them. On Wed, Aug 1, 2018 at 6:48 AM Eric Gade wrote: > Hello all, > > I'm having a strange issue with CI on my recent pull request. See >

[Pharo-dev] [Pharo 7.0-dev] Build #1148: 22287-size-t-type-does-not-have-right-size-in-windows-64bit

There is a new Pharo build available! The status of the build #1148 was: SUCCESS. The Pull Request #1660 was integrated: "22287-size-t-type-does-not-have-right-size-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/1660 Issue Url: