Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot load Magritte into Pharo 12 Image #342

Open
PowellDean opened this issue Dec 4, 2023 · 9 comments
Open

Cannot load Magritte into Pharo 12 Image #342

PowellDean opened this issue Dec 4, 2023 · 9 comments

Comments

@PowellDean
Copy link

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

@jborden23
Copy link

jborden23 commented Dec 15, 2023 via email

@PowellDean
Copy link
Author

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
Copy link
Author

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
Copy link

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
Copy link
Member

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
Copy link
Member

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

@sebastianconcept
Copy link

Screen Shot 2024-03-03 at 14 46 06 I get this @seandenigris

@JanBliznicenko
Copy link
Contributor

JanBliznicenko commented May 9, 2024

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
Copy link
Author

PowellDean commented May 9, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants