Thanks to these replies I found the issue, but I'm not sure how to solve it.
I found the start up script. I have never consciously set it, but I assume some process in the distant past automatically created it for me. The issue was that the settings for: #monticello#cacheDirectory and #monticello#defaultDirectoryName pointed to obsolete random projects from the past. I deleted them from the settings file, but it looks like when my new image autogenerated them, it stored new ones in the settings file that are equally irrelevant to future generated images: /home/myusername/Pharo/images/testimage/pharo-local/package-cache and /builds/workspace/Pharo-6.0-Update-Step-1-Tracker, respectively. What should I set these to so that they behave appropriately as I create new images in Pharo launcher? Does pharo launcher have a global dedicated place for a package cache, or is there a way to make it switch per new image? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
