Annoying No version found for #stable of ConfigurationOfOmniBrowser while loading Seaside

Loading Seaside in Pharo 1.1.1 with a script below, I get a couple of 'No version found for #stable of' for ConfigurationOfOmniBrowser and ConfigurationOfRefactoringBrowser exception.


I can simply ignore these exceptions and everything seems to work. But they are still annoying. And more than that, they continue to appear (many times!) when I load other packages dependent on Seaside. Can it be disabled or fixed some how?



--
Dennis Schetinin

Let me look into this ... something must have changed since I originally tested ConfigurationOfSeaside30 ...

Thanks for reporting the problem...

Dale

On Mar 20, 2011, at 11:21 AM, Dennis Schetinin wrote:

Loading Seaside in Pharo 1.1.1 with a script below, I get a couple of 'No version found for #stable of' for ConfigurationOfOmniBrowser and ConfigurationOfRefactoringBrowser exception.

Gofer new
    squeaksource: 'MetacelloRepository';
    package: 'ConfigurationOfSeaside30';
    load.
(Smalltalk at: #ConfigurationOfSeaside30) load.

I can simply ignore these exceptions and everything seems to work. But they are still annoying. And more than that, they continue to appear (many times!) when I load other packages dependent on Seaside. Can it be disabled or fixed some how?



--
Dennis Schetinin

Dennis,

Try updating to a later version of Metacello:

  ConfigurationOfMetacello project updateProject.
  ConfigurationOfMetacello load.

Symbolic versions were introduced in version 1.0-beta.28...

Dale

On Mar 20, 2011, at 11:21 AM, Dennis Schetinin wrote:

Loading Seaside in Pharo 1.1.1 with a script below, I get a couple of 'No version found for #stable of' for ConfigurationOfOmniBrowser and ConfigurationOfRefactoringBrowser exception.

Gofer new
    squeaksource: 'MetacelloRepository';
    package: 'ConfigurationOfSeaside30';
    load.
(Smalltalk at: #ConfigurationOfSeaside30) load.

I can simply ignore these exceptions and everything seems to work. But they are still annoying. And more than that, they continue to appear (many times!) when I load other packages dependent on Seaside. Can it be disabled or fixed some how?



--
Dennis Schetinin

This helps, thank you!




--
Dennis Schetinin