May 2018 - Pharo-dev - lists.pharo.org

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

by Guillermo Polito

Cool, Thanks! On Fri, May 4, 2018 at 3:24 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> 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 removal, no > action needed > addCategory:before: - solved by Nautilus removal, no action needed > hasErrorTest - solved by Nautilus removal, no action needed > inheritsFrom: - solved by Nautilus removal, no action needed > compile:classified:notifying: - solved by Nautilus removal, no action > needed > traits - solved by Nautilus removal, no action needed > hasPassedTest - solved by Nautilus removal, no action needed > extendingPackages - solved by Nautilus removal, no action needed > hasFailedTest - solved by Nautilus removal, no action needed > #color - solved by Nautilus removal, no action needed > annotateRubricText: - solved by Nautilus removal, no action needed > > The rest are the menu entries (https://pharo.fogbugz.com/f/ > cases/21827/clean-NautilusRefactoring-menu-entries-for-Nautilus). > > So at least from the method extensions point of view, we should be safe. > Thanks > > -- Pavel > > 2018-05-04 13:30 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > >> In an old image with Nautilus I did this: >> >> names := #('Nautilus' 'NautilusCommon' 'Nautilus-GroupManager' >> 'Nautilus-GroupManagerUI' 'QualityAssistant' 'QualityAssistantRecording' >> 'QualityAssistant-Test'). >> >> selectors := names flatCollect: [ :packageName | packageName asPackage >> extensionMethods collect: #selector as: Set ]. >> selectors reject: [ :each | >> senders := SystemNavigation default allSendersOf: each. >> senders allSatisfy: [ :sender | names includes: sender package name ] ]. >> >> This is the result of problematic extensions. Some of them are solved by >> the removal, most of them are menu entries in NautilusRefactorings. The >> mentioned selector #createPackageNamed: is there. >> >> "#(#codeRewritingClass: #methodRefactoring: #refactoringMenu: >> #varRefactoringSubMenu: #groupRefactoring: #createPackageNamed: >> #sourceCodeRefactoring: #refactoringSubmenu: #instVarRefactoring: >> #refactoringMethod: #browse #sourceCodeRefactoringMenu: #asRingDefinition >> #addCategory:before: #hasErrorTest #inheritsFrom: >> #compile:classified:notifying: #traits #hasPassedTest #extendingPackages >> #browsedEnvironment: #hasFailedTest #notifyViewedDiffFor:of: #repairIcon >> #color #annotateRubricText: #notifyBanInitiatedFor:of: >> #notifyCritique:AutoFixedFor:)" >> >> I will check them and make the issue entries. >> >> -- Pavel >> >> 2018-05-04 13:08 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >>> >>> >>> 2018-05-04 10:19 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>>> Hi, >>>> >>>> I've just tried to create a new package in Calypso and I got bitten by >>>> this: >>>> >>>> https://pharo.fogbugz.com/f/cases/21804/Creating-a-Package-f >>>> rom-Calypso-produces-DNU >>>> >>>> Creating a new package was an extension of Nautilus, and was never >>>> introduced in RPackage. >>>> >>>> How should we procceed? How can we know all the "extensions" that were >>>> not so? >>>> >>> >>> I will try to check them >>> >>> -- Pavel >>> >>> >>>> >>>> -- >>>> >>>> >>>> >>>> Guille Polito >>>> >>>> Research Engineer >>>> >>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>> >>>> CRIStAL - UMR 9189 >>>> >>>> French National Center for Scientific Research - *http://www.cnrs.fr >>>> <http://www.cnrs.fr>* >>>> >>>> >>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>> >>>> *Phone: *+33 06 52 70 66 13 >>>> >>> >>> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 14, 2018

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

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

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 Issue Url: https://pharo.fogbugz.com/f/cases/21891 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 14, 2018

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

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

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 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 14, 2018

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

by Esteban Lorenzano

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 <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> stable is now promoted. > > I just did `curl https://get.pharo.org/vm61 | bash`, but Pharo is reporting > a seemingly old VM: > CoInterpreter VMMaker.oscog-eem.2265 uuid: > 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

May 14, 2018

Esteban's ChangeLog week of 7 May 2018

by estebanlm＠gmail.com

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&to=13/5/2018 ChangeLog ========= 9 May 2018: ----------- * I promoted a new stable vm (3rd or 4th attempt, I do not remember). Let's hope this time it works :) 7 May 2018: ----------- * I spent the full that (along with many days before today) fixing the build of libgit2 for the VM in linux 32bit. This was broken since a lot of time and it was making impossible to release a new stable version. I made to OSVM, and the result is what seems to be a valid build (linux 32bit shows a healthy libgit2). I will wait a couple of days to test but that means we can release a new stable VM, perhaps wednesday. cheers! Esteban

May 14, 2018

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

by Sean P. DeNigris

EstebanLM wrote > stable is now promoted. I just did `curl https://get.pharo.org/vm61 | bash`, but Pharo is reporting a seemingly old VM: CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 14, 2018

[Pharo 7.0-dev] Build #886: 21893 Some cleaning in Network packages

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

There is a new Pharo build available! The status of the build #886 was: SUCCESS. The Pull Request #1347 was integrated: "21893 Some cleaning in Network packages" Pull request url: https://github.com/pharo-project/pharo/pull/1347 Issue Url: https://pharo.fogbugz.com/f/cases/21893 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 13, 2018

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

by Esteban Lorenzano

yes, but too lateâ¦ stable is now promoted. and nobody complained so we should be ok :) Esteban > On 13 May 2018, at 12:08, Norbert Hartl <norbert(a)hartl.name> wrote: > > Do I get it from get.pharo.org <http://get.pharo.org/>? > > Am 09.05.2018 um 14:05 schrieb Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > >> Tested on 32-bit and 64-bit Linux. Everything seems to work well. >> >> -- Pavel >> >> 2018-05-09 13:36 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> hi, >> >> I will try to promote new stables. >> Can you people try the latest vm and report issues? (linux32 libgit2 problem should be fixed) >> >> thanks! >> Esteban >>

May 13, 2018

[Pharo 7.0-dev] Build #885: 21895 Cleanup of SUnit

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

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

May 13, 2018

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

by Norbert Hartl

Do I get it from get.pharo.org? > Am 09.05.2018 um 14:05 schrieb Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > Tested on 32-bit and 64-bit Linux. Everything seems to work well. > > -- Pavel > > 2018-05-09 13:36 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> hi, >> >> I will try to promote new stables. >> Can you people try the latest vm and report issues? (linux32 libgit2 problem should be fixed) >> >> thanks! >> Esteban >

May 13, 2018