A side note, VM version strings are an absolute disaster for end users, it is simply impossible to talk about a specific version.
$ ./pharo-ui --version 5.0 5.0.201901051900 Mac OS X built on Jan 5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) [Production Spur 64-bit VM] CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git WTH ? > On 3 Mar 2020, at 19:07, tbrunz <[email protected]> wrote: > > Pablo, does this only affect Macs? I just tried this on a Linux machine, > updating/launching a Pharo 8 64-bit image. > > It still showed the older VM. I tried restarting the VM Manager, restarting > Pharo Launcher (1.9.2), and then re-installing Pharo Launcher, then creating > a new image, each time trying everything again. > > But the version of the VM only ever says "2020-02-12", not "2020-02-20". > When I tried the same thing for a 32-bit Pharo 8 image, it uses a VM dated > "2020-02-06". > > What am I doing wrong? > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >
