- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #815: 21803 Cleanups in Tool-CriticBrowser
by ci-pharo-ci-jenkins2＠inria.fr April 30, 2018

April 30, 2018

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

1 0

Esteban's ChangeLog week of 23 April 2018
by estebanlm＠gmail.com April 30, 2018

April 30, 2018

Hello! This is my weekly ChangeLog, from 23 April 2018 to 29 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/4/2018&to=29/4/2018 ChangeLog ========= 24 April 2018: -------------- * I released [v0.7.3 of iceberg](https://github.com/pharo-vcs/iceberg/releases/tag/v0.7.3) List of changes is big, as this are the first stabilisation releases after the huge refactor we did... * I just released libgit [v1.3.1](https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v1… which simplifies initialisation mechanism. 23 April 2018: -------------- * Lots of meetings, but I managed to work today in [https://github.com/pharo-vcs/iceberg/issues/667](https://github.com/pharo-v… . Guille needs to finish it but that means 0.7.3 is almost ready. cheers! Esteban

1 0

[Pharo 7.0-dev] Build #814: 21807-Integrate-Iceberg-0.7.4
by ci-pharo-ci-jenkins2＠inria.fr April 28, 2018

April 28, 2018

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

1 0

[Ann] Iceberg 0.7.4
by Guillermo Polito April 28, 2018

April 28, 2018

Hi all, Time for the weekly Iceberg update. The next pharo build will include Iceberg 0.7.4, with many improvements done during this last week. Documentation wise, all documentation/workflow valid for 0.7.3 is still valid for 0.7.4. Thanks to all brave users, issue reporters and contributors :). Key changes: - Several improvements in merging (mostly UI) - Optimize Pharo workflow (less fetches and unnecessary diffs) - Lots of new automated tests to cover merging, reverting and some git interactions that are difficult to capture manually Infrastructure changes: - Since 0.7.2 was released, we made the resolution of making an enhancement in the infrastructure per release - In 0.7.3 we fixed travis CI so builds are run on every commit and on pull requests - In this relese (0.7.4) we introduced in the build tests againt pharo 6.1 and 64 bits * The idea is to prepare the field for a future backport to Pharo 6.1 * And have good 64 bit support * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 In the next version our idea is to put the focus on enhancing - metacello integration - Pharo6.1 compatibility working smoothly - add a couple of more videos on scenarios like: * how to upgrade and contribute to iceberg * how to review a pharo fix * how to reuse your image for other fixes * handling merges * how to update a fork Here is the detailed changelog with all closed issues during this week: #729 Update .travis.yml to test Pharo 6 and 64 bits #689 Creating a repository in an existing location shows a debugger UI enhancement #556 Removed packages are not removed from git Model bug #727 Adapt properties reading of Tonel projects for Pharo 6.1. #728 Ask confirmation on fetch all action #543 In merge window removed methods are not taken into account Model bug #695 Specifying that Clone GitHub repository only deals with ssh mode Github plugin UI #690 Revert all does not behave correctly in detached working copy Model bug important #720 Commit panel should be selected by default when opening the commit window UI enhancement #724 Change focus order of commit window UI enhancement #719 Typing just after entering commit windows throw an error UI bug #721 Repository creation error not handled Github plugin bug #722 Typo in email git properties Libgit bug #716 "#pathString was sent to nil" if Pharo repository is not resolved Metacello Integration bug important #709 Cannot see the arrow in merge view #701 Merge view shows extra things UI enhancement merge #710 Merge does not apply changes right bug merge #711 The merge lose some changes bug merge #694 Extra diffs happen Model enhancement important #705 Clone repair action does extra actions Model enhancement #647 Following script for Pharo6.1 leads to unusable Iceberg (>>#binaryWriteStream) Pharo6-backport bug important Enjoy, Guille

1 0

[Pharo 7.0-dev] Build #813: 21796 Clean Compiler-Tests
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2018

April 27, 2018

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

1 0

[Pharo 7.0-dev] Build #812: 21789 Better tagging in Collections-Native
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2018

April 27, 2018

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

1 0

libfreetype6 missing in the dependencies of ubuntu Pharo distribution
by Peter UhnÃ¡k April 27, 2018

April 27, 2018

Hi, I've just tried installing pharo from package manager on Elementary OS, which is a ubuntu derivative. All went well, except fonts weren't working in 32 bit version, and I had to install by hand "libfreetype6:i386" ... is it missing in the dependencies? Thanks, Peter

2 4

[Pharo 7.0-dev] Build #811: 21788 Cleanup Athens-Examples
by ci-pharo-ci-jenkins2＠inria.fr April 27, 2018

April 27, 2018

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

1 0

Fwd: ByteArray>>at:put:
by Sean P. DeNigris April 26, 2018

April 26, 2018

Relevant to Pharo? >From http://forum.world.st/ByteArray-at-put-tp4955848.html : Bert Freudenberg wrote > On 26 April 2018 at 11:28, marcel.taeumel < > Marcel.Taeumel@ > > wrote: > >> Hi, there. >> >> I cannot put a ByteString into a ByteArray via a WriteStream anymore: >> >> | s | >> s := WriteStream on: ByteArray new. >> s nextPutAll: 'hello'. >> >> You need to do: >> >> | s | >> s := WriteStream on: ByteArray new. >> s nextPutAll: 'hello' asByteArray. >> >> This breaks code. >> >> Best, >> Marcel >> > > âTechânically this is an expected error - you simply cannot put Characters > (the elements of a String) into a ByteArray. However, for convenience we > do > support copying Strings into ByteArrays in various places, including > WriteStream>>nextPutAll:. > > However, the test in WriteStream>>nextPutAll: is too strict. It needs to > be > "collection class isBits" instead of "collection isString". This makes the > code actually match its comment: > > WriteStream>>nextPutAll: aCollection > > | newEnd | > (collection class == aCollection class > or: [ collection class isBits > and: [ aCollection isString > and: [ collection class format = aCollection class format ] ] ]) "Let > Strings with the same field size as collection take the quick route too." > ifFalse: [ ^ super nextPutAll: aCollection ]. > > newEnd := position + aCollection size. > newEnd > writeLimit ifTrue: > [self growTo: newEnd + 10]. > > collection replaceFrom: position+1 to: newEnd with: aCollection > startingAt: 1. > position := newEnd. > ^aCollectionâ > > With that change your example works. I think this was the original intent > of the code. > > Fixed in Collections-bf.787 > > - Bert - ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 3

Is Beacon still planned to be added to P7?
by Peter UhnÃ¡k April 26, 2018

April 26, 2018

Hi, in several older discussions there was a mention of Beacon logger being added to Pharo 7 (by default)... is that still the plan? Thanks, Peter

6 5