[Pharo-dev] Sign Windows VMs

Hi! I am using Pharo in a company network under a firewall, an antivirus, and windows, and each day I have an issue with some parts of the Pharo application that are recognized as a threat. So, I cannot download it or execute it straightforwardly. Today was this one:

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 15:15 GMT+02:00 Marcus Denker : > > > On 14 May 2018, at 15:09, Nicolas Cellier gmail.com> wrote: > > > > 2018-05-14 14:44 GMT+02:00 Marcus Denker : > >> > >> > >> > For ByteArray, I didn't check recently in

[Pharo-dev] [Pharo 7.0-dev] Build #897: 21900-GTExamplesBrowser-uses-old-Compiler-API

There is a new Pharo build available! The status of the build #897 was: FAILURE. The Pull Request #1353 was integrated: "21900-GTExamplesBrowser-uses-old-Compiler-API" Pull request url: https://github.com/pharo-project/pharo/pull/1353 Issue Url: https://pharo.fogbugz.com/f/cases/21900

[Pharo-dev] [Pharo 7.0-dev] Build #896: 21903-GT-tools-still-uses-old-compiler-API-evaluateforlogged

There is a new Pharo build available! The status of the build #896 was: FAILURE. The Pull Request #1354 was integrated: "21903-GT-tools-still-uses-old-compiler-API-evaluateforlogged" Pull request url: https://github.com/pharo-project/pharo/pull/1354 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #895: 21904-TextDoIt-TextPrintIt-uses-old-compiler-API

There is a new Pharo build available! The status of the build #895 was: SUCCESS. The Pull Request #1352 was integrated: "21904-TextDoIt-TextPrintIt-uses-old-compiler-API" Pull request url: https://github.com/pharo-project/pharo/pull/1352 Issue Url:

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

> On 14 May 2018, at 15:09, Nicolas Cellier > wrote: > > > > 2018-05-14 14:44 GMT+02:00 Marcus Denker >: > > > > > > For ByteArray, I didn't check recently in Pharo, but I know that it's quite >

[Pharo-dev] [Pharo 7.0-dev] Build #894: 21888 Tagging in CodeImportCommandLineHandlers

There is a new Pharo build available! The status of the build #894 was: SUCCESS. The Pull Request #1343 was integrated: "21888 Tagging in CodeImportCommandLineHandlers" Pull request url: https://github.com/pharo-project/pharo/pull/1343 Issue Url: https://pharo.fogbugz.com/f/cases/21888

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 14:44 GMT+02:00 Marcus Denker : > > > > > > For ByteArray, I didn't check recently in Pharo, but I know that it's > quite a mess in Squeak because some methods are in Alien, other in FFI, > other in base Squeak... > > IMO all methods should be in core

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

> > > For ByteArray, I didn't check recently in Pharo, but I know that it's quite a > mess in Squeak because some methods are in Alien, other in FFI, other in base > Squeak... > IMO all methods should be in core Squeak/Pharo because of general usage (like > decoding binary data). > I want to

[Pharo-dev] [Pharo 7.0-dev] Build #893: 21885-Simplify-ProcessList-classdumpPigStackOnandClose

There is a new Pharo build available! The status of the build #893 was: FAILURE. The Pull Request #1351 was integrated: "21885-Simplify-ProcessList-classdumpPigStackOnandClose" Pull request url: https://github.com/pharo-project/pharo/pull/1351 Issue Url:

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

2018-05-14 13:22 GMT+02:00 Guillermo Polito : > > > On Fri, Apr 20, 2018 at 5:24 PM, Sven Van Caekenberghe > wrote: > >> Hi, >> >> After the File and Stream changes in Pharo 7, a binary read, resp. write >> stream from/to a file is actually a

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

On Fri, Apr 20, 2018 at 5:24 PM, Sven Van Caekenberghe wrote: > Hi, > > After the File and Stream changes in Pharo 7, a binary read, resp. write > stream from/to a file is actually a ZnBuffered(Read|Write)Stream on a > BinaryFileStream. You access these using

[Pharo-dev] [Pharo 7.0-dev] Build #892: 21890 Cleanup Collections-Sequenceable

There is a new Pharo build available! The status of the build #892 was: SUCCESS. The Pull Request #1345 was integrated: "21890 Cleanup Collections-Sequenceable" Pull request url: https://github.com/pharo-project/pharo/pull/1345 Issue Url: https://pharo.fogbugz.com/f/cases/21890 Build

[Pharo-dev] [Pharo 7.0-dev] Build #891: 21738 Fix inconsistent method classifications (lint) in Collections

There is a new Pharo build available! The status of the build #891 was: SUCCESS. The Pull Request #1222 was integrated: "21738 Fix inconsistent method classifications (lint) in Collections" Pull request url: https://github.com/pharo-project/pharo/pull/1222 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #890: 21896-Cleanup-Shout

Builds are failing du to CI problems…. e.g this one missing workspace /builds/workspace/branch_Pipeline_development-CMOUMEH7DVLJPL2EIJ6VPEHUQRS3W4AK3FD4ESTKJ3YGKZERQFUQ on pharo-ci-jenkins2-bootstrap-unix-2 But the granularity of PRs are very small (and they are tested on the PR level, too),

[Pharo-dev] [Pharo 7.0-dev] Build #890: 21896-Cleanup-Shout

There is a new Pharo build available! The status of the build #890 was: FAILURE. The Pull Request #1350 was integrated: "21896-Cleanup-Shout" Pull request url: https://github.com/pharo-project/pharo/pull/1350 Issue Url: https://pharo.fogbugz.com/f/cases/21896 Build Url:

Re: [Pharo-dev] Easy way to browse Hermes packages?

Hi Pablo, Thanks! I'll take a look (my Pharo time is very limited at the moment, unfortunately). Cheers, Alistair On 12 May 2018 at 20:19, teso...@gmail.com wrote: > Hello, >having the Hermes files and any Pharo7 image it is easy to inspect the > Hermes package. > It

[Pharo-dev] [Pharo 7.0-dev] Build #889: 21889 Tag manifest in Collections-Arithmetic

There is a new Pharo build available! The status of the build #889 was: FAILURE. The Pull Request #1344 was integrated: "21889 Tag manifest in Collections-Arithmetic" Pull request url: https://github.com/pharo-project/pharo/pull/1344 Issue Url: https://pharo.fogbugz.com/f/cases/21889

Re: [Pharo-dev] Problems with the removal of Nautilus

Cool, Thanks! On Fri, May 4, 2018 at 3:24 PM, Pavel Krivanek wrote: > createPackageNamed: - solved by you > browse - adds an ability for RBBrowserEnvironment to be browsed by > Nautilus, no action needed > asRingDefinition - for UndefinedObject, solved by Nautilus

[Pharo-dev] [Pharo 7.0-dev] Build #888: 21891-PluggableButtonMorph-in-dark-theme-does-not-take-the-theme-into-account-for-the-border

There is a new Pharo build available! The status of the build #888 was: FAILURE. The Pull Request #1348 was integrated: "21891-PluggableButtonMorph-in-dark-theme-does-not-take-the-theme-into-account-for-the-border" Pull request url: https://github.com/pharo-project/pharo/pull/1348

[Pharo-dev] [Pharo 7.0-dev] Build #887: 21892 Tag and comment Multilingual packages

There is a new Pharo build available! The status of the build #887 was: FAILURE. The Pull Request #1346 was integrated: "21892 Tag and comment Multilingual packages" Pull request url: https://github.com/pharo-project/pharo/pull/1346 Issue Url: https://pharo.fogbugz.com/f/cases/21892

Re: [Pharo-dev] ASK FOR TEST: latest vm

is promoted to 7.0. 6.1 cycle takes a lot more since is kind of “backporting”. remember : changes happens in “development branch”, not in “stable”. Then, changes in stable are backports we believe are necessary. cheers, Esteban > On 14 May 2018, at 03:56, Sean P. DeNigris

[Pharo-dev] Esteban's ChangeLog week of 7 May 2018

Hello! This is my weekly ChangeLog, from 7 May 2018 to 13 May 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=7/5/2018=13/5/2018 ChangeLog = 9 May 2018: --- *I promoted a new stable vm (3rd or 4th attempt, I do not remember).