On Uto, 2015-12-22 at 11:56 +0100, Ferlicot D. Cyril wrote: > Since last week a new VM is use for Pharo 5 beta.
Beginning Pharo user here...I had the same problem on my Debian box: "This interpreter (vers. 6505) cannot read image file (vers. 6521)." > You need to download the new VM on http://files.pharo.org/vm/pharo-spu > r32/. Then I downloaded the new VM image and tried to use it with latest Pharo Launcher ('Bleeding Edge'), but now I get: "This interpreter (vers. 6521) cannot read image file (vers. 6505)." which is kind of catch-22 situation... > Then you need to update Pharo Launcher. ...and it looks that I do not have updated Pharo Launcher. > For now the easiest way I think is to enable the development mode in > PharoLauncher, go in Monticello, and load the last version of Pharo > Launcher core. Tried that as well, but didn't work. > Later I think that a new release of Pharo Launcher will make thing > easier. Let me say that the potential of Pharo Launcher is really great - it allows (if I got it right) to have many development machines available via different VMs, while still keeping developer's machine in sane state which cannot be said when one does regular development with other (mostly compiled) languages, which is "simply wonderful!". Now I wonder if you can provide any further hint how to resolve the above? Is there a plan that in the future Pharo Launcher will become regular part of 'normal' Pharo image? I know that probably there would be more luch with V4.0, but I simply would like to try latest code eagerly anticipating the day to try 64bit VM. Still, kudos to all Pharo devs for providing human development environment in the days when things are going insane all around us. Sincerely, Gour -- As a lamp in a windless place does not waver, so the transcendentalist, whose mind is controlled, remains always steady in his meditation on the transcendent self.
