-
Notifications
You must be signed in to change notification settings - Fork 34
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
Comments
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: ***@***.***>
|
Hi - I'm following the directions posted here: https://github.com/magritte-metamodel/magritte Metacello new I've just successfully loaded it into a clean Pharo 11 image (64-bit), so it is only the 12 version that breaks. Thanks |
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: 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? |
Pharo 11 cannot load
It can manually be loaded with:
Can we have a pinned version to load in Pharo 11? |
Sure, @sebastianconcept, but I noticed |
@jborden23 what error are you seeing with |
I get this @seandenigris |
Well, the 3.8 version is over 100 commits old, made for Pharo 10. 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. |
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:
***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: