To load the latest Seaside in Pharo 7 I use the develop branch: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:develop/repository'; load.
In any case you need this recent commit https://github.com/SeasideSt/Seaside/commit/fd2887df520505520d5bb7fbf37c2f8a4758d72e which seems to be on master as well > On 18 Dec 2018, at 15:18, [email protected] wrote: > > Ciao, > > after a Pharo 7.0 - 64 bit crash, > > for now irrecoverable, > > where i lose some works......... ( i'm not happy for some days ). > > I'm trying to set up a new image. > > But..... > > Because i think to messed up on /home/party/Pharo/images/Pharo 7.0 - > 64bit (development version) > > i rename it. > > After with the command: wget -O- https://get.pharo.org/64/70+vm | > bash > > i create new lonely /opt/pharo7.0.0rc1b57 build 57 image > > With this command the system create a new directory: > /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) > > > Into Iceberg i import my local existing entry repository: > > Seaside master 9566cb4 add MetacelloAllowLockedProjectChange > handling > > When on this repository i do the Metacello Install baseline of > Seaside3 (default) > > the system open a Window with titled: > > Could not resolve: ConfigurationOfZincHTTPComponents > [ConfigurationOfZincHTTPComponents] in /home/party/Pharo/images/Pharo 7.0 - > 64bit (development version)/pharo-local/package-cache > http://mc.stfx.eu/ZincHTTPComponents > > > The Metacello report a package entry with: > > BaselineOfSeaside3 (CompatibleUserName.1537724254) > > with repository set to: /home/party/Pharo/images/Pharo 7.0 - 64bit > (development version)/pharo-local/package-cache > > > Why this situation? > > Considerations? > > Thanks, > > Dario > >
