and ConfigurationOfVoyageMongo is using “stable”… same as before :( is this another case for metaceller? :P
Esteban On 07 Jan 2014, at 15:03, Norbert Hartl <norb...@hartl.name> wrote: > > Am 07.01.2014 um 14:57 schrieb Esteban Lorenzano <esteba...@gmail.com>: > >> >> On 07 Jan 2014, at 14:25, Norbert Hartl <norb...@hartl.name> wrote: >> >>> I have problems loading voyage in a 2.0 image. For testing I downloaded a >>> fresh one and installed voyage via the configuration browser. Somehow the >>> dependencies from magritte down to grease seem to be broken somewhat. I >>> tries to load a package >>> >>> Grease-Pharo20-Core-pmm.1 >>> >>> and a debugger pops up saying >>> >>> This package depends on the following classes: >>> GRDelegatingStream >>> You must resolve these dependencies before you will be able to load these >>> definitions: >>> GRCountingStream >>> count >>> greaseNext:putAll:startingAt: >>> initialize >>> next >>> next: >>> nextPut: >>> nextPutAll: >>> reset >>> greaseNext:putAll:startingAt: >>> >>> >>> Select Proceed to continue, or close this window to cancel the operation. >>> >>> Anybody has a glue what is going on? Is this something introduced by the >>> release of seaside? Hints are appreciated. >> >> most probably. >> probably voyage for 2.0 should be updated to use a fixed version of grease >> instead #stable. > > That is what I don’t understand. > > ConfigurationOfMagritte3>>#stable: spec > <symbolicVersion: #stable> > > spec for: #'common' version: '3.0.1'. > spec for: #'pharo3.x' version: '3.1' > > and version 3.0.1 includes > > … > spec timestamp: '30 January 2012 12:55:56 pm'. > spec > project: 'Grease' with: '1.0.8‘; > > Norbert
