On 15 April 2017 at 09:12, Alistair Grant <akgrant0710@gmail.com> wrote:
On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote:
> The latest stable image release is Pharo-50771.image.
> The latest stable VM source release is pharo-vm-2016.02.18.
> These two releases are not compatible: This interpreter (vers. 6505) cannot
> read image file (vers. 6521).

Is this from a VM you built yourself?

This is a VM built from source during packaging for NixOS Linux.

�� What's the output of:

$ pharo --version

Here it is:

$ pharo-vm-nox --version
3.9-7 #1 Tue Mar 28 16:26:45 UTC 2017 gcc 5.4.0 [Production ITHB VM]
NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr ��5 2016
NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr ��5 2016
https://github.com/pharo-project/pharo-vm.git Commit: ba1aa855f546b084ec0ebdeb85a36f2352f97b49 Date: 2016-02-18 17:17:13 +0100 By: Esteban Lorenzano <estebanlm@gmail.com> Jenkins build #15040
Linux localhost 4.4.23 #1-NixOS SMP Fri Sep 30 08:20:43 UTC 2016 i686 GNU/Linux
plugin path: /nix/store/5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/pharo-vm-i386-2016.02.18/ [default: /nix/store/5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/pharo-vm-i386-2016.02.18/]

Note that the date 2016-02-18 corresponds with the latest non-spur source tarball release at http://files.pharo.org/vm/src/vm-unix-sources/

I just downloaded:

$ curl http://get.pharo.org/50+vm | bash

And it started without problem.

I *think* the difference is that you are downloading the VM as a binary and I am downloading it as source code, and we get different versions because pharo.org is regularly shipping updated binaries but not updating the source code releases at the same time. So the source releases lag behind over time and now it's at the point that they can't run the 5.0 image.