October 2026 - Pharo-users - lists.pharo.org

Pharo News of the Week 43/2026

by Marcus Denker

Hi, I want to restart sending a weekly summary to the list, this is now using an automatic process, let’s see how well this works in practice. In addition to the issue tracker summary, this already adds a mailinglist summary. Plan: - add a Discord discussion summary - Integrate news posts from Discord news channel Pharo News of the Week 43/2026 ============================== 16 October - 23 October 2026 Highlights ---------- - files.pharo.org was down 21/22 October (fixed) - VM: memory corruption in the allInstances primitive fixed on the main VM branch, with a backport for the Pharo 10 VM (#1115, #1116). - Pharo 13: fix for a VM crash caused by stale FullBlockClosures after a class reshape (#20067). - Pharo 15: more Calypso menus move to Commander2, and the pure Morphic find-and-replace dialog is removed in favour of the Spec one. - PRs merged: pharo 9 (Pharo 15: 8, Pharo 13: 1), pharo-vm 2, Spec 0, NewTools 0, iceberg 0. Pharo 15 -------- Eight PRs merged into Pharo15, the development branch. - #20097 Remove pure Morphic find and replace https://github.com/pharo-project/pharo/pull/20097 - #20106 Fix #20102: Add shortcut commands to define temporary and instance variables without dialog https://github.com/pharo-project/pharo/pull/20106 - #20109 Fix #20108: Fix broken hash in MetacelloProjectRegistration https://github.com/pharo-project/pharo/pull/20109 - #20107 Migrate the class menu of Calypso to Commander2 https://github.com/pharo-project/pharo/pull/20107 - #20103 Fix ClapDocumenter tests https://github.com/pharo-project/pharo/pull/20103 - #20104 Migrate Class/Method "Extras" menus from Commander to Commander2 https://github.com/pharo-project/pharo/pull/20104 - #20098 Clean various little glitches https://github.com/pharo-project/pharo/pull/20098 - #19846 Improve UI for rename argument/temporary variable and add tests https://github.com/pharo-project/pharo/pull/19846 Pharo 13 - #20067 [P13] 20046-Stale-FullBlockClosures-after-class-reshape- cause-VM-crash https://github.com/pharo-project/pharo/pull/20067 VM and other repositories ------------------------- VM (pharo-project/pharo-vm) - #1115 Fix/all instances primitive memory corruption (pharo-12 branch) https://github.com/pharo-project/pharo-vm/pull/1115 - #1116 [P10] - Fix/all instances primitive memory corruption (pharo-10 branch) https://github.com/pharo-project/pharo-vm/pull/1116 Iceberg (pharo-vcs/iceberg) - Tag v2.5.1 on Pharo14: pins libgit2-pharo-bindings v3.3.0 and Tonel v1.2.1 in BaselineOfIceberg. https://github.com/pharo-vcs/iceberg/tree/v2.5.1 - Work continues on the track-external-files branch (no PR merged yet). Mailing lists ------------- pharo-dev - Smalltalk as a wire format: agents sending Morphic UIs as source, run on a Dart/WasmGC interpreter (16 Oct): James Ladd presents Taskriz, where AI agents send Smalltalk source that builds native UIs, and asks for feedback on the Morph API, liveness and Pharo as the agent side. https://lists.pharo.org/hyperkitty/list/pharo-dev@lists.pharo.org/thread/HV…

Oct. 23, 2026

files.pharo.org online again

by Marcus Denker

Hello, The server http://files.pharo.org <http://files.pharo.org/> is online again. We will work on a better setup not relying on a single server. Marcus

Oct. 22, 2026

Re: Pharo-users] files.pharo.org no more accessible ?

by Marcus Denker

> On 22 Oct 2026, at 14:55, Christophe Touzé <chris.touze(a)gmail.com> wrote: > > Hello Marcus, > > Do you know where I can get pharo13-734.zip, waiting for the unblock ? > Local access via ssh to the machine still works, I copied it here: https://drive.proton.me/urls/DAWS622920#fzseMJffCNnZ Marcus

Oct. 22, 2026

Re: Pharo-users] files.pharo.org no more accessible ?

by Christophe Touzé

Hello Marcus, Do you know where I can get pharo13-734.zip, waiting for the unblock ? Christophe Le 22/10/2026 à 10:18, Marcus Denker a écrit : > Hello, > > I forgot to cc: pharo-users yesterday: > > The institute blocks all hosted machines due to the PHP Exploit. > > - we do not yet know when they unblock, but it seems fixes are available now > > Marcus > >> On 22 Oct 2026, at 09:43, Christophe Touzé via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> Hello, >> >> When trying to use a zero-conf for Pharo13 for Linux, the script fails when the connection wants to access to files.pharo.org. >> >> This is the same in http or https. >> >> Does someone know if it will be fixed ? >> >> >> Best regards >> >> Christophe >> >>

Oct. 22, 2026

Re: Pharo-users] files.pharo.org no more accessible ?

by Marcus Denker

Hello, I forgot to cc: pharo-users yesterday: The institute blocks all hosted machines due to the PHP Exploit. - we do not yet know when they unblock, but it seems fixes are available now Marcus > On 22 Oct 2026, at 09:43, Christophe Touzé via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > When trying to use a zero-conf for Pharo13 for Linux, the script fails when the connection wants to access to files.pharo.org. > > This is the same in http or https. > > Does someone know if it will be fixed ? > > > Best regards > > Christophe > >

Oct. 22, 2026

Re: Pharo-users] files.pharo.org no more accessible ?

by Guillermo Polito

Hi Christophe, Inria servers have been disconnected temporarily because of the disclosed PHP vulnerabilities. We hope they will be back up soon. G > Le 22 oct. 2026 à 9:43 AM, Christophe Touzé via Pharo-users <pharo-users(a)lists.pharo.org> a écrit : > > Hello, > > When trying to use a zero-conf for Pharo13 for Linux, the script fails when the connection wants to access to files.pharo.org. > > This is the same in http or https. > > Does someone know if it will be fixed ? > > > Best regards > > Christophe > >

Oct. 22, 2026

Pharo-users] files.pharo.org no more accessible ?

by Christophe Touzé

Hello, When trying to use a zero-conf for Pharo13 for Linux, the script fails when the connection wants to access to files.pharo.org. This is the same in http or https. Does someone know if it will be fixed ? Best regards Christophe

Oct. 22, 2026

Re: Pharo 13 on MacOS 27

by Hartmut Krasemann

Thx. This helped me, too Hartmut Krasemann ———————— Königsberger Str. 41c D 22869 Schenefeld +49.171.6451283 krasemann(a)acm.org > Am 09.10.2026 um 00:13 schrieb Tomohiro Oda via Pharo-users <pharo-users(a)lists.pharo.org>: > > Hartmut, > > I had the same problem and I replaced the content of > PharoLauncher.app/Contents/MacOS/Pharo and Plugins with the ones from > the zeroconf. > > $ curl -L https://get.pharo.org | bash > $ cp -rp pharo-vm/Pharo.app/Contents/MacOS/* > /Applications/PharoLauncher.app/Contents/MacOS/ > > So far it seems working. > I hope this helps. > --- > tomo > > 2026年10月8日(木) 19:56 Hartmut Krasemann via Pharo-users > <pharo-users(a)lists.pharo.org>: >> >> To whoever can help >> >> On MacOS 27 my Pharo Launcher did no longer start. >> Loading the latest Launcher from the Pharo website did not help. >> Neither startet my images by drag and drop (image to app) >> >> I found out that I used an arm-64 vm v10.3.9. and that the latest Launcher from Pharo.org starts the same version. >> >> After searching around a while I discovered that I could load a newer arm-64 vm v10.3.11 . >> I could not patch the Launcher with this vm, but make it default for all my images. >> Now an image starts with double click , choosing itself in a Mac dialog , and again double click it. >> However, starting this way, the working directory obviously is not set. >> I did not find a way to set the working directory in the running image. >> >> I then wrote a bash shell script (for each image to start) with the working directory as an argument. >> >> Now I can run my images but not the Launcher. >> >> Where can I get a download of a corrected Launcher >> Or >> Is there an easy fix? >> >> Regards, hartmut-k >> >> Hartmut Krasemann >> ———————— >> Königsberger Str. 41c >> D 22869 Schenefeld >> +49.171.6451283 >> krasemann(a)acm.org >> >>

Oct. 10, 2026

Re: Pharo 13 on MacOS 27

by Tomohiro Oda

Hartmut, I had the same problem and I replaced the content of PharoLauncher.app/Contents/MacOS/Pharo and Plugins with the ones from the zeroconf. $ curl -L https://get.pharo.org | bash $ cp -rp pharo-vm/Pharo.app/Contents/MacOS/* /Applications/PharoLauncher.app/Contents/MacOS/ So far it seems working. I hope this helps. --- tomo 2026年10月8日(木) 19:56 Hartmut Krasemann via Pharo-users <pharo-users(a)lists.pharo.org>: > > To whoever can help > > On MacOS 27 my Pharo Launcher did no longer start. > Loading the latest Launcher from the Pharo website did not help. > Neither startet my images by drag and drop (image to app) > > I found out that I used an arm-64 vm v10.3.9. and that the latest Launcher from Pharo.org starts the same version. > > After searching around a while I discovered that I could load a newer arm-64 vm v10.3.11 . > I could not patch the Launcher with this vm, but make it default for all my images. > Now an image starts with double click , choosing itself in a Mac dialog , and again double click it. > However, starting this way, the working directory obviously is not set. > I did not find a way to set the working directory in the running image. > > I then wrote a bash shell script (for each image to start) with the working directory as an argument. > > Now I can run my images but not the Launcher. > > Where can I get a download of a corrected Launcher > Or > Is there an easy fix? > > Regards, hartmut-k > > Hartmut Krasemann > ———————— > Königsberger Str. 41c > D 22869 Schenefeld > +49.171.6451283 > krasemann(a)acm.org > >

Oct. 8, 2026

Pharo 13 on MacOS 27

by Hartmut Krasemann

To whoever can help On MacOS 27 my Pharo Launcher did no longer start. Loading the latest Launcher from the Pharo website did not help. Neither startet my images by drag and drop (image to app) I found out that I used an arm-64 vm v10.3.9. and that the latest Launcher from Pharo.org starts the same version. After searching around a while I discovered that I could load a newer arm-64 vm v10.3.11 . I could not patch the Launcher with this vm, but make it default for all my images. Now an image starts with double click , choosing itself in a Mac dialog , and again double click it. However, starting this way, the working directory obviously is not set. I did not find a way to set the working directory in the running image. I then wrote a bash shell script (for each image to start) with the working directory as an argument. Now I can run my images but not the Launcher. Where can I get a download of a corrected Launcher Or Is there an easy fix? Regards, hartmut-k Hartmut Krasemann ———————— Königsberger Str. 41c D 22869 Schenefeld +49.171.6451283 krasemann(a)acm.org

Oct. 8, 2026