it is not urgent for me - I have a workaround. So for me it can wait until the next stable is released. Albrecht On 07.02.19 09:58, Alistair Grant wrote:
Hi Esteban,
On Thu, 7 Feb 2019 at 09:41, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Means we will need a new stable for Pharo 7/8 ?
Esteban Albrecht will obviously be the one to say how urgent it is for him, or whether he can get by with vmLatest80. From my perspective: the issue has been there "forever" (2010 or earlier) and has only just been reported. I expect that we'll eventually update the Pharo 7 VM anyway, and this can probably wait until then. Pharo 8 can wait as well, for the same reasons.
Cheers, Alistair
On 7 Feb 2019, at 09:23, Alistair Grant <akgrant0710@gmail.com> wrote:
On Thu, 7 Feb 2019 at 09:08, Albrecht Baur <baur.albrecht@googlemail.com> wrote:
Hi Alistair,
I have tested it and works with the latest VM. Great, thanks for the confirmation.
Cheers, Alistair
thanks,
Albrecht
On 07.02.19 07:56, Alistair Grant wrote:
Hi Albrecht,
On Wed, 6 Feb 2019 at 19:51, Albrecht Baur via Pharo-users <pharo-users@lists.pharo.org> wrote:
thank you! That is good news.
best,
Albrecht Would you please download the latest VM and confirm that it resolves the issue:
curl get.pharo.org/64/vmLatest80 | bash
The Pharo 8 VM works with Pharo 7 images.
Thanks, Alistair
On 06.02.19 09:34, Alistair Grant wrote:
Hi Albrecht,
On Tue, 5 Feb 2019 at 15:26, Albrecht Baur <baur.albrecht@googlemail.com> wrote:
Hi Alistair,
here the system report output:
... Thanks for the info. Please see:
Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/368 PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/371
Assuming the CI build passes, I'll wait a day or so to give the VM guys a chance to review the changes and comment before merging.
Cheers, Alistair