- Pharo-dev - lists.pharo.org

preparing to release: what do we do with this linux distros?
by Esteban Lorenzano May 9, 2017

May 9, 2017

http://pharo.org/STAGE.gnu-linux-installation <http://pharo.org/STAGE.gnu-linux-installation> I donât think they will work. We need to update or remove. Esteban

3 5

[pharo-project/pharo-core]
by GitHub May 9, 2017

May 9, 2017

Branch: refs/tags/60483 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 8e2258: 60483
by GitHub May 9, 2017

May 9, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 8e2258e8197862907e88f46042cc8bebc62a773d https://github.com/pharo-project/pharo-core/commit/8e2258e8197862907e88f460… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-09 (Tue, 09 May 2017) Changed paths: R Deprecated60.package/extension/CompiledMethodTest/instance/deprecatedMethod.st R Deprecated60.package/extension/CompiledMethodTest/instance/deprecatedMethod2.st R Deprecated60.package/extension/SUnitTest/instance/deprecatedMessage.st A Kernel-Tests.package/CompiledMethodTest.class/instance/examples/deprecatedMethod.st A Kernel-Tests.package/CompiledMethodTest.class/instance/examples/deprecatedMethod2.st A Kernel-Tests.package/CompiledMethodTest.class/instance/examples/deprecatedMethod3.st A Kernel-Tests.package/CompiledMethodTest.class/instance/examples/deprecatedMethod4.st M Kernel-Tests.package/CompiledMethodTest.class/instance/tests - testing/testIsDeprecated.st M Kernel.package/CompiledMethod.class/instance/testing/isDeprecated.st M Morphic-Widgets-FastTable.package/FTFilterFunction.class/instance/private/showFilterFieldFromKeystrokeEvent_.st A SUnit-Tests.package/SUnitTest.class/instance/helpers/deprecatedMessage.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60482.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60483.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60482.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60483.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60483 20023 #isDeprecated does not cover all deprecation messsages https://pharo.fogbugz.com/f/cases/20023 19920 FTTableMorph implicit filter isnt working properly with the escape keystroke https://pharo.fogbugz.com/f/cases/19920 http://files.pharo.org/image/60/60483.zip

1 0

(Iceberg?) Merge compiles copies of trait methods in user classes
by Aliaksei Syrel May 8, 2017

May 8, 2017

Hi, Time to time I notice that suddenly Trait methods are copied to user classes. And now I realised that this happens as the result of merge even if there are no differences in that particular Trait. Sometimes I manage to notice new methods in changes window but sometimes not, and then after months it is extremely difficult to find bugs related to copied methods, because I may change Trait code expecting that it will be updated in all users of that trait... Unfortunately I don't have a testcase that reproduces this issue.. sorry.. Just wanted to let you know, maybe it is something that can be fixed before release... Cheers, Alex

1 0

FileReference>>=
by Alistair Grant May 8, 2017

May 8, 2017

Hi All, The current definition of FileReference>>= returns false if two instances point to the same location, but one is relative and the other is absolute, e.g.: | f1 f2 | f1 := FileLocator workingDirectory / 'pharo-local'. f2 := f1 asAbsolute. f1 = f2 "false" This definition seems unintuitive to me as I'd expect this to be true since they are both pointing to the same file/directory. This introduces unexpected behaviour, e.g. I currently have two entries in Iceberg pointing to the same local git repository as one was added with a relative file reference, while the other was added with an absolute file reference. Apart from the potential to introduce problems by changing the definition, are there any arguments in favour of keeping the current definition? What do you think of changing the definition (in Pharo 7)? P.S. If we decide not to change it, then IceRepository>>checkForRegistryConflicts should be modified to compare absolute paths. Thanks, Alistair

1 0

Estebanâs list of blocking issues for release Pharo 6.0 (updated to May 08)
by Esteban Lorenzano May 8, 2017

May 8, 2017

Hello, This are the things I believe still needs to be solved to be able to release Pharo 6.0: PENDING: - image: iceberg hit the image (dev-0.4 is ready to enter) - remove all test regressions - NEW: pharovm is crashing on 64bits FIXED: (none) POSPOSED: iceberg to use libgit2 0.25.1 (needed to compile it in 64bits, but not mandatory) Release checklist: ==== - Prepare release notes Image: - add welcome browser (ONGOING) - generate PharoV60.sources (ONGOING) - move SystemVersion - prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P) VM: - stable for 6.0 release (DONE) WebSite: - Update index - Update download page Infrastructure: - ZeroConf: Open new 7.0 development (ONGOING) - SmalltalkCI: Open new 7.0 development (ONGOING) - Create platform stable versions - Jenkins: move all CI projects to Pharo 7.0 (ONGOING) Pub: - announce post - announce mail - post to YC, Reddit Iâm targeting this week for release. But you know how it isâ¦ it will happen most probably next monday ;) Also, I donât know what the problem with 64bits crashing is, Iâm just starting to explore thereâ¦ that can be a detail or a huge problem, and dince 64bits is âTHEâ important part of this release, is blocking enough to delay release.

1 0

Esteban's ChangeLog week of 1 May 2017
by estebanlm＠gmail.com May 8, 2017

May 8, 2017

Hello! This is my weekly ChangeLog, from 1 May 2017 to 7 May 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=1/5/2017&to=7/5/2017 ChangeLog ========= 5 May 2017: ----------- * I just made this little script: ---- startDate := Date year: 2016 month: 04 day: 01. authors := Set new. unknown := Set new. CompiledMethod allInstancesDo: [ :each | | array date | array := each timeStamp substrings. ((array size = 3) and: [ date := [ array second asDate ] on: Error do: [ :e | ]. date notNil ]) ifTrue: [ date >= startDate ifTrue: [ authors add: array first trimBoth ] ] ifFalse: [ unknown add: each timeStamp] ]. ---- To collect this release authors :) Seems that we have at least 88 contributors this version. And we are not counting VM contributors or the people who contributes in other ways: documenting, enhancing frameworks... just particupanting in the lists. This are the authors this script collects: [[[ a Set('BernhardPieber' 'AliakseiSyrel' 'MaxLeske' 'StephanEggermont' 'KenCausey' 'RogerStebler' 'EliotMiranda' 'AndreiChis' 'SergeStinckwich' 'DenisKudryashov' 'ThierryGoubier' 'CyrilFerlciot' 'HenrikSperreJohansen' 'ThibaultRaffaillac' 'monty' 'MarcusDenker' 'RonieSalgado' 'Uko' 'ChristopheDemarey' 'NicolaiHess' 'JohnSnow' 'SomeName' 'md' 'DenisKUdryashov' 'StefanReichhart' 'BenComan' 'DirkRoeleveld' 'johanfabry' 'AutoDeprecationRefactoring' 'CyrilFerlicot' 'YuriyTymchuk' 'mml' 'GitHub' 'SvenVanCaekenberghe' 'LucFabresse' 'matteob8' 'JurajKubelka' 'TommasoDalSasso' 'VincentBlondeauMaximeRoelandt' 'kks' 'pk' 'RM' 'AlexandreBergel' 'auto' 'MerwanOuddane' 'PavelKrivanek' 'OffrayLuna' 'dik' 'nice' 'BooleanSlotTest' 'StephaneDucasse' 'LionelAkue' 'VincentBlondeau' 'eem' 'HenrikNergaard' 'AlejandroInfante' 'hn' 'NicoPasserini' 'PropertySlotTest' 'HilaireFernandes' 'PeterUhnak' 'BernardoContreras' 'ClementBera' 'PabloTesone' 'UnlimitedInstanceVariableSlotTest' 'ThibaultArloing' 'CamilloBruni' 'Spirita' 'cb' 'Anonymous' 'TorstenBergmann' 'PaulDeBruicker' 'TheIntegrator' 'ClementBer' 'AlistairGrant' 'TravisCI' 'JanVanDeSandt' 'TudorGirba' 'EstebanLorenzano' 'SlotErrorsTest' 'Denis' 'ClementBEra' 'MartinDias' 'GlennCavarle' 'GustavoSantos' 'GuillermoPolito' 'RyckewaertValentin' 'ValentinRyckewaert') ]]] Yes, there are some repeated (like "Denis" and "DenisKudriasov") and some wrong (like "CamilloBruni", he is not in the community since some time now), and finally there are others that are robots (like "TheIntegrator"). But this gives a hint of the people contributing which overall will be more than 80 for sure. 4 May 2017: ----------- * So, I worked a bit on [smalltalk-travis-ci](http://github.com/estebanlm/smalltalk-travis-ci) to allow some environment configurations: ---- PHARO_VM=stable*|latest PHARO_ARCH=i386*|x86_64 LINUX_HEARTBEAT=threaded*|itimer ---- Idea is simple: we want to be able to tune the compilations a bit more than now. The options added allows us to declare the type of VM (and in the case of the +PHARO_ARCH+ variable, also the type of the image). For now, this is experimental and if you want access to it you need to add this to your +.travis.yml+ file: ---- smalltalk_edge: source: estebanlm/smalltalk-travis-ci branch: dev ---- I will test and add other options as we need, but it remains to integrate it/generalise it better, that needs to be talked with Fabio later :) * I just fixed all crashes on [libgi2 0.25.1](https://github.com/pharo-vcs/libgit2-pharo-bindings/tree/v0.25.1) and [iceberg](https://github.com/pharo-vcs/iceberg) ! But now I realised I cannot activate the tests on github and travis because it needs a special VM :S 3 May 2017: ----------- * I spent the day recovering the tests for [iceberg](http://github.com/pharo-vcs/iceberg). At this moment, tests are disabled because after moving to internal backend they got broken. Now, we need to make then pass. And I 'almost' succeeded. They are still two tests crashing the image, but most of the rest seems to be ok. I hope to finish tomorrow. * I take some time to verify and promote new [stable VMs for Pharo 6.0](http://files.pharo.org/get-files/60). They are now based on the [opensmalltalk-vm](http://github.com/opensmalltalk/opensmalltalk-vm) process so I expect certain noise, but in general this should be working a lot better than before. cheers! Esteban

1 0

First commit
by Evan Donahue May 7, 2017

May 7, 2017

Hello, I have just tried to submit my first patch to the main Pharo inbox. I submitted a patch for issue https://pharo.fogbugz.com/f/cases/17848 because it basically amounted to changing an error message and seemed like a good place to start figuring out how the submission process works. I saved my slice to the Pharo60Inbox, but when I typed my commit message and hit save, I did not see any confirmation. How can I tell if my slice was submitted or not? Thank you, Evan

4 5

./pharo --help returns exit code 1 on ubuntu
by Andrei Chis May 7, 2017

May 7, 2017

Hi, In an ubuntu installation with the latest vm and Pharo 6 image when executing `./pharo --help` I get an error code of 1. wget -O- get.pharo.org/vmLatest60 | bash wget -O- get.pharo.org/60 | bash ./pharo --help echo $? --> returns 1 On mac the error code is 0. Also when executing './pharo' or './pharo Pharo.image --help' or './pharo --version' the error code is 0 on both mac and linux. So it seems there is some issues with --help. Actually, it gives a usage warning, but still I'd expect to not return an error code. Usage: Pharo.app/Contents/MacOS/Pharo [<option>...] [<imageName> [<argument>...]] Pharo.app/Contents/MacOS/Pharo [<option>...] -- [<argument>...] Cheers, Andrei

3 5

Respect Pharo and respect us
by Stephane Ducasse May 6, 2017

May 6, 2017

Hi guys Could we have discussion about ***PHARO*** in the Pharo-dev mailing-list? Can we get a bit of respect? Should we create a private dev mailing-list so that we can get our focus? I start to get bored to have to mute threads. I let you imagine the threads I'm muting. In addition, I would really like that you ask yourself when is the last time that you did something for Pharo if ever. You see doing something for Pharo is as easy as - removing typo from a book - adding a comment in a method - helping a newbie but often you prefer to talk I know why because this is easy. So you do not need to have the perfect X&*^*&^ system to take 10 min of your great life to HELP (see above) Our goal is to build Pharo and we would love other people to help or at least do not use our bandwidth about other goals. So respect Pharo and us. Stef

2 1