Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4.

This means that, at this point, in the Moose image Nautilus does not get updated anymore.

Cheers, Doru

On 11 May 2012, at 08:52, Tudor Girba wrote:

I can reproduce the problem.

Nautilus is loaded from its own repository like: Gofer new url: 'http://ss3.gemstone.com/ss/Nautilus'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work.

But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: Gofer new squeaksource:'MetaRepoForPharo14'; package: 'ConfigurationOfNautilus'; load. (ConfigurationOfNautilus project version: #stable) load.

Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4.

Cheers, Doru

On 10 May 2012, at 15:01, Fabrizio Perin wrote:

...

Hi, I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code.

I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else.

Any idea?

Cheers, Fabrizio

-- www.tudorgirba.com

"Sometimes the best solution is not the best solution."

-- www.tudorgirba.com

"It's not how it is, it is how we see it."