Some Metacello issue

Hi,

after having made some new releases I have an odd Metacello issue and I am not sure how to debug it. This happens on my legacy Pharo3/Pharo4 images that I still need to support in deployment.

It seems to be related to a dependency chain of "app"->VoyageMongo->Magritte3 3.5.0 and somehow version '3.1.1.1' of Magritte3 doing something with Grease #stable and not finding a 'Core' group. Any idea how to debug it or if any configuration changed recently? It also only seems to happen if there are two dependency chains that try to load the same VoyageMongo version.


Broken:

pharo Pharo3.image config http://smalltalkhub.com/mc/osmocom/Osmocom/main ConfigurationOfOsmoUniverse --install=bleedingEdge

Error: Name not found: Core
MetacelloMCVersionSpec(Object)>>error:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpec:forLoad:forMap:packages: in Block: [ ^ self error: 'Name not found: ' , aString ]
MetacelloMCVersionSpec(MetacelloVersionSpec)>>packageNamed:forLoad:forMap:ifAbsent: in Block: [ ...
Dictionary>>at:ifAbsent:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>packageNamed:forLoad:forMap:ifAbsent:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpec:forLoad:forMap:packages:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs:forLoad:map: in Block: [ :req | ...
Array(SequenceableCollection)>>do:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs:forLoad:map:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs:
MetacelloMCVersionSpec(MetacelloVersionSpec)>>expandToLoadableSpecNames: in Block: [ :cache | ...
MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [ :dict | ...
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
...


Working:

Metacello new
        configuration: 'Magritte3';
        repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
        version: '3.5.0';
        load

On 07/06/17 06:19, Holger Freyther wrote:
> Metacello new configuration: 'Magritte3'; repository:
> 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main'; version:
> '3.5.0'; load

version: #'release35' (or #'release3'

Never refer to fixed versions unless you know why (you need to avoid a
specific bug fix).

What is most likely is that there is some overconstrained configuration.
Does your ConfigurationOfVoyageMongo or one of the configurations it
pulls in refer to different versions of grease or magritte? Another
issue can be that there are older configurations already loaded that
conflict with the newest ones. Indeed, the ConfigurationOfMongoTalk
is broken, refering to a fixed and older version of Grease.
ConfigurationOfVoyageMongo should probably be using #'release3' of
Magritte, but that doesn't break it.

Stephan

I would like to repeat here again: don't refer to fixed version numbers
of packages out of your control in configurations. Refer to #'release'
versions that can be patched by the maintainers of your dependencies.
That is only appropriate when having to patch around a problem, and
couples your configuration hard to the development schedule of your
dependency, making it your responsibility to update your configuration
whenever that of your dependency is updated.

Stephan

> On 7. Jun 2017, at 14:09, Stephan Eggermont <[hidden email]> wrote:
>
> Never refer to fixed versions unless you know why (you need to avoid a
> specific bug fix).

When wanting to have repeatable builds (e.g. for bugfixes) and in the
absence of other means to lock/define versions externally, I think using
a fixed version is the way to go.


> What is most likely is that there is some overconstrained configuration.
> Does your ConfigurationOfVoyageMongo or one of the configurations it
> pulls in refer to different versions of grease or magritte? Another
> issue can be that there are older configurations already loaded that
> conflict with the newest ones. Indeed, the ConfigurationOfMongoTalk
> is broken, refering to a fixed and older version of Grease.
> ConfigurationOfVoyageMongo should probably be using #'release3' of
> Magritte, but that doesn't break it.

Right. So we have a "OsmocomUniverse" build job that pulls in all the
apps into a single image. This helps to make API modifications and not
forget any of the client code.

The configuration has such dependencies:

ConfigurationOfOsmocomUniverse
        -> ConfigurationOfHLR
                -> ConfigurationOfVoyageMongo
                        -> Mongotalk
                                -> Grease A
                        -> Magritte3
                                -> Grease B
        -> ConfigurationOfSMPPRouter
                -> ConfigurationOfVoyageMongo
                        -> Mongotalk
                                -> Grease A
                        -> Magritte3
                                -> Grease B

What happens is that somehow "Grease A" gets loaded, then "Grease B" and
when it is time for "Grease A" again.. the system kind of explodes and this
is for Pharo3 and Pharo6. Now the question to me is.. why is this coming
up right now? Did MongoTalk change or Magritte3 or something else?

Is there an easy way for Metacello to try a mirror instead of the original,
e.g. to inject an older ConfigurationOfMagritte3?


holger

On 06/07/2017 03:46 AM, Holger Freyther wrote:
I think that the `lock` command[1] is what you are looking for ...

Dale

[1]
https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md#locking

Just a small addition: I just looked at Pillar, but the build of Pillar was building fine until beginning of this month. My change is from the beginning of May …