I downloaded from STHub as I wrote (so no clones involved). Sorry the script mentioned in the mail was wrong, I used Metacello new configuration:'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #stable; load to install from GitHub as it is mentioned directly on https://github.com/SeasideSt/Seaside Should I try the loading of Seaside directly from the Github repository using Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load as given on the same page? Do the versions on GitHub and STHub differ already? Are they in synch? According to the page it looks like loading from GitHub is just a second way of loading. I will try ... Thx T.
Gesendet: Freitag, 18. Mai 2018 um 15:24 Uhr Von: "Cyril Ferlicot D." <cyril.ferlicot@gmail.com> An: pharo-dev@lists.pharo.org Cc: "Seaside - developer list" <seaside-dev@lists.squeakfoundation.org> Betreff: Re: [Pharo-dev] [Seaside-dev] Seaside loading broken in Pharo 7
Le 18/05/2018 à 15:21, Torsten Bergmann a écrit :
Thanks Sven for the #stable definition.
That seems to solve the Zinc issue ... but now I run into a problem with #greaseInteger sent to a character in WAUrlEncoder class when loading Seaside-Core-Johan-Brichau.875.
Screenshot attached.
But #greaseInteger is not defined for Character, only for Number, Integer and String.
To reproduce: I loaded Seaside from STHub using
Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load
on latest Pharo-7.0+alpha.build.917.
I did not get the problem (yet).
Can you check that your local Seaside and Grease clones are up to date? Iceberg does not manage yet upgrade of the local clones :(
Thanks Torsten
-- Cyril Ferlicot https://ferlicot.fr