demarey wrote > Maybe it could be related to this bug: > https://github.com/pharo-project/pharo-launcher/issues/52
It is a different bug in the same behavior. The easy workaround is to manually create a pharo.version file for the offending image. As to the bug… The immediate problem turned out to be that I had a startup error in certain images due to a startup script that only worked in more recent Pharo versions. So, suggestion #1: check that pharo.version has actually been created, and if not produce a better error message. Also, ideally there should probably also be a timeout in determining the image version because sometimes the process returns without creating the file and other times it doesn't return at all. However, even after disabling the startup scripts, I was only able to generate pharo.version by replacing "~/Documents/Pharo/vms/private/6505/Pharo.app" with "~/Documents/Pharo/vms/30-x86/Pharo.app", so there does also seem to be something fishy with the 6505 VM ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
