Remove 'METIS' variant of SuiteSparse since it's wrong#24483
Merged
branfosj merged 2 commits intoeasybuilders:developfrom Nov 9, 2025
Merged
Remove 'METIS' variant of SuiteSparse since it's wrong#24483branfosj merged 2 commits intoeasybuilders:developfrom
branfosj merged 2 commits intoeasybuilders:developfrom
Conversation
Contributor
|
Yes. Suitesparse does not use user-provided METIS anymore |
…asyconfigs into 20251107105435_new_pr_mwmXNPmpeU
branfosj
approved these changes
Nov 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(created using
eb --new-pr)This variants with METIS suffix and dependency are actually wrong as I've understood it. We should just use the SuiteSparse-7.10.3-foss-2025a.eb instead.
I suggest removing this to avoid confusing people into thinking they want/need the one with external METIS.
Is this correct @appolloford ?