August 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

by Marcus Denker

> On 25 Aug 2017, at 15:47, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > Less crassly, what I meant to say, was; it'd be really nice if the > integration process was fixed before too much energy is spent trying to > backport/solve reported issues. > Yes, you are rightâ¦ the strange thing is that the problem was introduced very late and we do not yet really understand what it isâ¦ (And I kind of suppressed my knowledge about itâ¦ just rememberd it when I tried to check a back port and it failed). Marcus

Aug. 25, 2017

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

by Henrik Sperre Johansen

Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues. Cheers, Henry -- View this message in context: http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 25, 2017

Re: [Pharo-dev] [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

by Henrik Sperre Johansen

What's the point? Even if an issue has slice attached, is marked as Fixed, and has no failing tests in a local image, it'll be thrown out by a broken monkey / integration process, ref. for example https://pharo.fogbugz.com/f/cases/20119/basicIdentityHash-and-only-basicIde… (I imagine the same fix would be beneficial on Pharo7 as well, btw) Cheers, Henry -- View this message in context: http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 25, 2017

[ Pharo 70 ] Build 59 PR 201

by Marcus Denker

New build with one trivial fix (which will be back ported to Pharo6, too): [ Pharo 70 ] Build 59 PR 201 -DarkTheme-disabledTextColor-is-too-close-of-textColor https://github.com/pharo-project/pharo/pull/201 https://pharo.fogbugz.com/f/cases/20248

Aug. 25, 2017

[Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

by Marcus Denker

Hi, We have 40 issues that are tagged for Pharo6: https://pharo.fogbugz.com/f/filters/1192/6-0-All <https://pharo.fogbugz.com/f/filters/1192/6-0-All> We should move as many of those to âLaterâ, so that we can focus on important fixes and back portsâ¦ sadly here we need to be realistic: We can not fix everything or even back port everythingâ¦ we need to prioritise. It would help if people could âhelp decidingâ which issues do not need the Pharo6 milestone. Marcus

Aug. 25, 2017

Call for Spanish/ Portuguese and more subtitles for the PharoMooc

by Stephane Ducasse

Hi guys The Pharo is a wonderful vehicule to promote Pharo and we need your help to translate the subtitles to different languages. This year we will have english voices paid by Inria (thanks) but we cannot do everything and we need your help. https://github.com/SquareBracketAssociates/PharoMooc/tree/master/Subtitles Stef

Aug. 25, 2017

libpng fails to download

by Alistair Grant

Hi All, Esteban, I just attempted to build the pharo vm on Win32 and it failed due to: ftp://ftp.simplesystems.org/pub/libpng/png/src/libpng16/libpng-1.6.29.tar.gz not being available. The current version is 1.6.30, which also appears to be unavailable from this address. I successfully downloaded 1.6.29 from: http://prdownloads.sourceforge.net/libpng/libpng-1.6.29.tar.gz?download which is referenced on what appears to be the official web page: http://www.libpng.org/pub/png/libpng.html I plan to test with 1.6.30 tonight. Is there any reason not to submit a PR pointing to sourceforge? Thanks, Alistair

Aug. 25, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Stephane Ducasse

Because he wrote it but indeed it should be migrated to Pharo. On Thu, Aug 24, 2017 at 11:12 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Why is that document in the account of guille? > > Norbert > > Am 12.08.2017 um 11:47 schrieb Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > > > 2017-08-12 11:36 GMT+02:00 Holger Freyther <holger(a)freyther.de>: >> >> >> > On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> > wrote: >> > >> > Hi, >> >> Hey! >> >> thank you for this HOWTO! >> >> > username := 'YOUR-USER-NAME'. >> > repository := IceRepositoryCreator new >> > url: 'git@github.com:pharo-project/pharo.git'; >> > location: ('pharo-core' asFileReference ensureCreateDirectory); >> > subdirectory:'src'; >> > createRepository. >> > repository checkoutBranch: 'development'. >> > repository register. >> > >> > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' >> > format: {username})). >> > repository addRemote: fork. >> > repository pushRemote: fork. >> > repository pullRemote: repository origin. >> >> I am using "pharo-mac-stable.zip" and >> "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your >> howto and run into various Iceberg issues. Where would be the best place to >> report them? >> >> Open Iceberg, selech "Pharo", click on Branches >> => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. >> >> Open Iceberg, double click on "Pharo" >> => DNU, #/ was sent to nil >> UndefinedObject(Object)>>doesNotUnderstand: #/ >> ... IceSavedPackage repository location seems to return nil. >> >> >> Are these known? Fogbugz? Github issues of Iceberg? > > > yes, because this HOWTO is already obsolete. See: > > https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-P… > > -- Pavel > >> >> >> >> cheers >> holger >> >> >> >> >

Aug. 24, 2017

Re: [Pharo-dev] 20294 Add FileAttributesPlugin to the linux 32 bit VM

by Stephane Ducasse

Yes yes yes we need to handle decently symlink. On Thu, Aug 24, 2017 at 4:29 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Esteban, > > It looks like there has been some recent activity with VM plugins, I > would really appreciate it if you could also add #20294. > > This is the plugin that fixes #isSymlink and adds symlink attributes. > > See: > https://pharo.fogbugz.com/f/cases/20294/Add-FileAttributesPlugin-to-the-lin… > > > If there's anything I can do to help the process, please let me know. > > Thanks, > Alistair > >

Aug. 24, 2017

Re: [Pharo-dev] [Vm-dev] 20294 Add FileAttributesPlugin to the linux 32 bit VM

by Alistair Grant

Hi Eliot, On Thu, Aug 24, 2017 at 08:15:20AM -0700, Eliot Miranda wrote: > > Hi Alistair, > > > > On Aug 24, 2017, at 7:29 AM, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > > > > Hi Esteban, > > > > It looks like there has been some recent activity with VM plugins, I > > would really appreciate it if you could also add #20294. > > > > This is the plugin that fixes #isSymlink and adds symlink > > attributes. > > My main concern with this new plugin is what happens on windows? Is > this a unix only thing? Have you provided support for windows, even > if they're only stubs that always answer false? It works on both Windows and Linux, I've tested it on: - Linux 32 bit - Linux 64 bit - Windows 32 bit I'm hoping that it will just work on Mac OS (I don't have a machine to test it with). I'm not aware of any accepted process for adding plugins, but I was hoping to: - Enable the plugin on Linux 32 bit. Hopefully this is low friction, since it is where it has had most testing (Ubuntu 16.04). Once I'm confident that it is OK here... - Enable the plugin on the other platforms. This can be one at a time, or everything at once, whatever you prefer. - Add the supporting smalltalk code to the image, minus the integration. This will allow people to test the new functionality, without any danger of breaking the existing code. - Switch the behaviour over to the new plugin. The smalltalk code is already available, see the fogbugz issue. Once it is ready to be added to the image I'll create a pull request. If you've got any other questions or concerns, please let me know. Cheers, Alistair > > > > See: > > https://pharo.fogbugz.com/f/cases/20294/Add-FileAttributesPlugin-to-the-lin… > > > > > > If there's anything I can do to help the process, please let me know. > > > > Thanks, > > Alistair > > > >

Aug. 24, 2017