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

Update spack package for [email protected] release #45

Closed
3 tasks
cameronrutherford opened this issue Oct 12, 2023 · 2 comments
Closed
3 tasks

Update spack package for [email protected] release #45

cameronrutherford opened this issue Oct 12, 2023 · 2 comments
Assignees
Milestone

Comments

@cameronrutherford
Copy link
Contributor

cameronrutherford commented Oct 12, 2023

@cameronrutherford cameronrutherford added this to the 1.6.0 Release milestone Oct 12, 2023
@cameronrutherford cameronrutherford changed the title Update spack package for [email protected] to require [email protected] Update spack package for [email protected] release Oct 13, 2023
@cameronrutherford
Copy link
Contributor Author

Per #16, we should ensure +python required +mpi for the moment.

@cameronrutherford
Copy link
Contributor Author

Per #18, we should probably add something to the spack package for this issue, but will hopefully be removed in the next release.

Something like conflicts("+hiop~mpi ^[email protected]:~mpi @1.5.1:1.6.1", msg="GitHub Issue #18 identified build issues in 1.6.0 release."). Apart from potential syntax errors in that snippet, it's unclear when this bug was introduced, so just going to be conservative with the ExaGO range, as well as the HiOp range. I am sure people can expand those ranges in Spack if they care to better document the bugs...

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

2 participants