Re: [Pharo-dev] Startup Error in Recent Pharo 7

[Sean P. DeNigris]

Update: It succeeded with a GH URL. The two scenarios that seemed to fail
were:
1. a filetree URL
2. If I accidentally opened the same image twice via Launcher

Still investigating…



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] Startup Error in Recent Pharo 7

[Sean P. DeNigris]

Did something change in the last two or three days with
Iceberg/Metcello/Monticello? I was loading a project successfully in a
startup script via:
   Metacello new   
repository: 'filetree://', (repoFolder / 'src') fullName;
baseline: 'DeNigrisPreferences';
onConflict: [ :ex | ex allow ];
load.

That now fails with "IceCloneLocationAlreadyExists": IceGenericError:
'~/Dynabook/Working Images/MM 23
1021/pharo-local/iceberg/seandenigris/Pharo-Preferences' exists and is not
an empty directory. The crazy thing is that the directory does *not* exist!

This only fails at startup. If I run manually after startup, the load
succeeds. Ideas?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] PharoLauncher : Image version determination error

[Sean P. DeNigris]

demarey wrote
> I just published a new version of the launcher

Thanks!



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] PharoLauncher : Image version determination error

[Christophe Demarey]

Hi,

I just published a new version of the launcher: 1.4 (http://pharo.org/download 
)
Improvements:
Add Origin Template Column
Simplify Timestamp Printing
Bug fixes:
#233 Cannot launch recent Pharo 7 images

This version mainly solves the problem of launching recent Pharo 7.0 images. 
Once this version is downloaded, do not forget to delete the folders related to 
70 vms in the Pharo/vms folder. This way, Pharo Launcher will download the 
latest one.
By the way, it also comes with some UI improvements (contributed by Sean and 
Tim).
I will work on a new version with a VM manager able to list locally available 
VMs, and a way to update or delete them. This new version will be based on 
Pharo 7 because Pharo Launcher development switched to github 
(https://github.com/pharo-project/pharo-launcher) and upcoming features are 
based on Pharo 7 (new UI, model refactoring).

Cheers,
Christophe


> Le 22 août 2018 à 15:54, Alistair Grant  a écrit :
> 
> Hi Christophe,
> 
> On Wed, 22 Aug 2018 at 15:33, Christophe Demarey
>  wrote:
>> 
>> Hi Alistair,
>> 
>>> Le 22 août 2018 à 12:02, Alistair Grant  a écrit :
>>> 
>>> Hi Christophe,
>>> 
>>> On Wed, 22 Aug 2018 at 09:36, Christophe Demarey
>>>  wrote:
 
 ...
 
 As a workaround for now, we are thinking to ship the pharo.version file 
 along with the image to avoid to run images with compatible VMs that we 
 cannot ensure they work well with a given image.
>>> 
>>> Part of the issue here is that Pharo 7 is still  in development.  My
>>> understanding is that within the development cycle we assume that the
>>> latest VM is being used (if I'm wrong, I'm sure someone will correct
>>> me :-)).
>>> 
>>> I don't use Pharo Launcher, so I'm not familiar with it, but it seems
>>> to me that for the current development version (currently Pharo 7) the
>>> launcher needs to ensure that it has the latest stable VM.
>> 
>> You’re right but the problem is that Pharo Launcher has no way to know what 
>> is the pharo version of an image before running it and evaluate a small 
>> expression. To achieve that, Pharo Launcher uses a VM that is, at least, 
>> compatible with the image format number. We do not have any guarantee that 
>> the expression evaluation of the VM will work fine for all images. For now, 
>> to detect the pharo version of Spur images, we use Pharo 61 VM. You can 
>> assume it will work well for 6. images. What if we use the 70 VM to 
>> determine pharo version of 6.* images? It will probably work better for 
>> Pharo 7 images (assuming we use the latest 70 VM) but then, no guarantee it 
>> will work for 61 images.
>> 
>> The core of the problem is that we should not be forced to run an image to 
>> determine its pharo version. Nevertheless, I think it would be good to use 
>> the latest available VM for a given image format to determine its pharo 
>> version. It should work in most cases.
> 
> Thanks very much for the explanation, it makes sense now.
> 
> My understanding is that the Pharo 7 VM is backward compatible with
> Pharo 6.1 (for now).  Esteban's process is to release a new stable
> Pharo 7 VM, and then a month later upgrade the Pharo 6.1 VM as well.
> Of course, that will be superseded by the availability of
> pharo.version.
> 
> Thanks again,
> Alistair