exception raised when installing Cozy

[rvillemeur]

Hi

After watching Cozy annoncement, I tried to install it on a clean image using:
'Metacello new
baseline: 'Cozy';
repository: 'github://Ducasse/Cozy/tree/master/src';
load'

I had the two exceptions declared during install.

I didn't investigate further to see what was wrong. Creating the missing file manually leads to more error messages and exceptions.

I can see that there is a new menu entry with cozy script. However, the new theme is not available.
Did I miss something ?

System used: Pharo 7 - 32 bits on windows 10 - 64 bits. Image Pharo7.0.4-0-32bit-ccd1f64.image

[Ducasse]

Thanks for the report. I did not test it in Pharo 70.
I only tested it and use it in Pharo 80.
Could you try and let me know?

[Ducasse]

I'm busy but I will see if I can try on Pharo 70 by the end of the week.

[rvillemeur]

I used Pharo8 - 32 bits from pharo launcher, fresh download.

Pharo 8.0.0
Build information: Pharo-8.0.0+build.1100.sha.99168805cde02d925202484d9902a12afef7e864 (32 Bit)

I have again both exeption:
File does not exist On: C:\Users\villemre\AppData\Roaming\pharo\SettingResources\sharedRepositoryFolderPath.ston
File does not exist On: "Path / 'C:' / 'Users' / 'villemre' / 'AppData' / 'Roaming' / 'pharo' / 'SettingResources' / 'backgrounds'"

I have also tried on pharo8 - 64 bits: Pharo 8.0.0
Build information: Pharo-8.0.0+build.1100.sha.99168805cde02d925202484d9902a12afef7e864 (64 Bit)

I have exactly the same issue on both version. I have attached the callstack of the 64bit version. I guess it's identical for the 32 bits.

callstack.txt
callstack2.txt

[Ducasse]

Thanks a lot I will have a look.
This is for a feature I do not really use and I got problems with too.
The process is Pharo-scripts is to clone a repo with all the folders already created and I do not want to force people to do the same so I will remove the background features .

I commited a version without the background folder features (I will check later because I was checking that it existed. I will restart a clean install later to see).