-
Notifications
You must be signed in to change notification settings - Fork 46
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
Some changes that need to be pushed to main Spack #1140
Comments
I will work on mepo. We have an RC in PyPi now (https://pypi.org/project/mepo/), so the package was easy to make. I'll work on our side to see if we are ready to move on with a release. (We have to be a bit more cautious internally as the mepo state file is moving from pickle to json, so existing clones throw some warnings. We want to let users know.) |
Thanks very much @mathomp4! Yes, I remembered our previous conversation and that's why assigned this to you rather than me pushing what is in our branch. |
@climbfuji Well, first we see if spack mainline likes it: if so, I can work to get it into JSCDA spack. ETA: Or if they take too long, I'll do the same here tomorrow or something. :) |
Both of my packages are merged into spack develop. Both of them received updates=improvements as part of the process, which will come back to spack-stack-dev with the next merge from spack develop. I updated the list above. |
Well, something weird is happening with spack mainline and mepo, so let me try and bring it in here. ETA: Okay JCSDA/spack#447 has the updates from my two spack mainline PRs for mepo. Just in case. |
Well, spack/spack#44879 is now in mainline spack so... 🤷🏼 The changes will get in some way :) |
@srherbener can you take a look at the openmpi recipe and push changes to main spack? |
My apologies for the slow response. I've been buried with getting spack-stack-1.8.0 to build on Mac Sonoma. I'm planning on getting to the openmpi recipe next week. |
The openblas update was merged upstream. Last one on the list is openmpi (two-level namespace) |
Sorry about the delay in getting to this. I initially tried to cherry-pick the openmpi, macos, two-level-namespace updates but there is enough divergence since the last time we sync'd with the authoritative spack repo that the cherry picked commits are pulling in a bunch of other changes not related to the macos openmpi update. So I have created a PR by manually adding in the code in the openmpi package.py script to introduce the two_level_namespace variant: spack/spack#47202 |
Packages in our fork's
builtin
repo but not main Spack:Changes that (probably) need to be pushed:
The text was updated successfully, but these errors were encountered: