Ok, I can load my own project now when I exchange the grease reference from 1.1.5 to stable. After a hint from Stephan Eggermont I changed the mongotalk build to include the right repo for grease. So this mismatch should have been gone. While Iâm able to build my own project I still cannot load voyage in a fresh 2.0 image. Norbert Am 20.03.2014 um 16:39 schrieb Johan Brichau <johan@inceptive.be>:
Norbert,
From your screenshot, I see that the Grease package you have loaded in your image is dirty. It is also the package version that gets loaded with Grease 1.1.5. My first question is: why is it dirty? Can you check that?
The package version you are loading is the one that is referenced by Grease 1.1.6
I just tagged Grease 1.1.6 as #stable yesterday. So that probably triggers this.
Though I cannot see any reason why this occurs and Seaside 3.1 is loading well here.
Johan
On 20 Mar 2014, at 15:47, Norbert Hartl <norbert@hartl.name> wrote:
I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen
<Bildschirmfoto 2014-03-20 um 15.43.56.png>
Any ideas?
Norbert