Cannot load Magritte into Pharo 12 Image about magritte

[jborden23]

Hi - what command are you using to load it? I thought adding onConflictUseLoaded would solve it but a quick check fails on 12. You may have to stick with Pharo 11.Thanks,JohnOn Dec 4, 2023, at 00:36, Dean Powell ***@***.***> wrote: Following the directions to load Magritte into my Pharo 12 image, I receive the following error message: MetacelloConflictingProjectError: Load Conflict between existing BaselineOfGrease. I removed BaselineOfGrease from my Pharo image to no avail. Screenshot.from.2023-12-03.23-35-23.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[PowellDean]

Hi - I'm following the directions posted here: https://github.com/magritte-metamodel/magritte

Metacello new
baseline: 'Magritte';
repository: 'github://magritte-metamodel/Magritte';
load

I've just successfully loaded it into a clean Pharo 11 image (64-bit), so it is only the 12 version that breaks.

Thanks

[PowellDean]

EXCEPT...I've subsequently tried to load Seaside 3 into that same Pharo 11 image, and loading Seaside fails with the exact same message as originally posted. So:
In Pharo 11: if I load Magritte first, that works, but I cannot subsequently load Seaside. If I load Seaside first, that is successful, but I cannot subsequently load Magritte.

I assume the problem is that Seaside and Magritte require different specific versions of BaselineOfGrease?

Do you know if there's a specific version of Seaside that will work with Magritte loaded first?

[sebastianconcept]

Pharo 11 cannot load v3.8

Metacello new
  baseline: 'Magritte';
  repository: 'github://magritte-metamodel/magritte:v3.8';
  load: #( Core ).

It can manually be loaded with:

Metacello new
  baseline: 'Magritte';
  repository: 'github://magritte-metamodel/Magritte';
  load.

Can we have a pinned version to load in Pharo 11?

[seandenigris]

Sure, @sebastianconcept, but I noticed load: #( Core ) in the first script but not the second. Could that be a factor? Also what is the specific error you’re seeing?

[seandenigris]

@jborden23 what error are you seeing with onConflictUseLoaded? That seems like it should fix @PowellDean’s issue…

[sebastianconcept]

I get this @seandenigris

[JanBliznicenko]

Well, the 3.8 version is over 100 commits old, made for Pharo 10.
It lacks, for example, my commit 6d67df3 named "Made loadable in Pharo 11 and 12".
I really believe version 3.8 is not loadable in Pharo 11 and 12 and the only way to fully load it there (not just Core) is to use master or specific commit until new release/tag is made.

However, only making the release might not help @PowellDean as it is about version conflict between two projects - Magritte uses fixed version of Grease while some other project seems to always load most recent master of Grease.

[PowellDean]

Is there anything I can help with? My time is limited and my focus has been elsewhere lately but if there's something I can do let me know. Dean

…

On Thu, May 9, 2024, 1:52 a.m. Jan Blizničenko ***@***.***> wrote: Well, the 3.8 version is over 100 commits old, made for Pharo 10. It lacks, for example, my commit 6d67df3 <6d67df3> named "Made loadable in Pharo 11 and 12". I really believe version 3.8 is not loadable in Pharo 11 and 12 and the only way to fully load it there (not just Core) is to use master or specific commit until new release/tag is made. — Reply to this email directly, view it on GitHub <#342 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGPPCUB3AJG2R4WBNX2PNLZBMTLRAVCNFSM6AAAAABAFORJZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSGE2DGMRWGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>