Closed climbfuji closed 2 days ago
Not yet ready for prime time. Getting lots of build errors on nautilus, seem to be related to the new setuptools or pip
@AlexanderRichert-NOAA When I restrict py-numpy to 1:25 or earlier, everything builds fine on my end and in CI. Do you want to check out these additions here on top of your PR?
I think we should lobby the Spack devs to see about a concretization option that really unifies everything, including build-only dependencies, which as far as I can tell is the root of all these issues (i.e., Spack doesn't count build-only dependencies as duplicates for unify:true or unify:when_possible).
I think we should lobby the Spack devs to see about a concretization option that really unifies everything, including build-only dependencies, which as far as I can tell is the root of all these issues (i.e., Spack doesn't count build-only dependencies as duplicates for unify:true or unify:when_possible).
That's a good point. Why don't you join the (almost) weekly spack user's meeting (Wed 10am MT/12pm ET) - quite often there is a number of spack developers on the call (for example today).
Ubuntu CI runner had a full disk again. I fixed it and submitted a PR to a JCSDA repo to avoid this problem in the future. Hopefully the current Intel build will go through smoothly, then I will rerun GNU.
@AlexanderRichert-NOAA - https://github.com/AlexanderRichert-NOAA/spack-stack/pull/3
Closing, no longer needed.
Summary
This PR should get merged into https://github.com/JCSDA/spack-stack/pull/1138 (or it can replace #1138, since it is based on it), but for the purpose of testing in CI I am creating a PR here.
The changes on top of #1138 are:
Testing
Applications affected
See #1138
Systems affected
See #1138
Dependencies
n/a
Issue(s) addressed
See #1138
Checklist
All dependency PRs/issues have been resolved and this PR can be merged.