Merge from upstream as a base for upstream PRs #250
Merged
Conversation
This file contains 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
* dla-future: Add conflict for pedantic warnings turning into errors * dla-future: Add conflicts for nvcc/fmt/Umpire compilation issues
* added new packages * align release with ccl patch * revert version on compiler classics
* gipaw.x installed by cmake if version >= 5c4a4ce. gipaw.x will only be installed with cmake if the qe-gipaw version is >= 5c4a4ce. Currently, QE source uses the older f5823521 one. Here a patch to the submodule_commit_hash_records to use a newer qe-gipaw version.
Co-authored-by: Harmen Stoppels <me@harmenstoppels.nl>
* Kokkos: adding version 4.2.00 to the package * Kokkos: adding AMD GPU arch * kokkos@4.2.00 +sycl: patch numeric traits unit test --------- Co-authored-by: eugeneswalker <eugenesunsetwalker@gmail.com> Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
* py-pygeos: add v0.14 * Python is also a link dep
* py-numba: add v0.58.1 * Passing tests
Also fix netcdf-c zlib reference
Replace last release due to build issues on windows. Tag was applied incorrectly
* Update SIRIUS version for CP2K master * Update var/spack/repos/builtin/packages/cp2k/package.py Co-authored-by: Rocco Meli <r.meli@bluemail.ch> --------- Co-authored-by: Rocco Meli <r.meli@bluemail.ch>
* tests: default_config drop scope * use default_config elsewhere * use parse_install_tree for missing defaults in default config
…ured (spack#35975) This looks to me like the best compromise regarding externals in a build cache. I wouldn't want `spack install` on my machine to install specs that were marked external on another. At the same time there are centers that control the target systems on which spack is used, and would want to use external in buildcaches. As a solution, reuse concretization will now consider those externals used in buildcaches that match a locally configured external in packages.yaml. So for example person A installs and pushes specs with this config: ```yaml packages: ncurses: externals: - spec: ncurses@6.0.12345 +feature prefix: /usr ``` and person B concretizes and installs using that buildcache with the following config: ```yaml packages: ncurses: externals: - spec: ncurses@6 prefix: /usr ``` the spec will be reused (or rather, will be considered for reuse...)
* developer tools stack try 2 This version is actually in use locally and has largely stabilized, at least on x86. Some packages are still a challenge on ppc64le, but maybe worth keeping this working as a set. * add packages, try to get container with newer gcc * remove reuse: true * try to get cmake to build on medium, 25 minutes is too long * add lsd package and add to dev tools stack * clean up fzf dependency and sorting * Update share/spack/gitlab/cloud_pipelines/stacks/developer_tools/spack.yaml * cuda: add 12.3.0 (spack#40827) * Switch to dashes * yet more underscores --------- Co-authored-by: Paul R. C. Kent <kentpr@ornl.gov>
…1423) Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5.2.0 to 5.3.0. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@e6428a5...31cebac) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
Intel made an incompatible change in XED in 2023.08.21 that breaks hpctoolkit (at run time). Hpctoolkit develop can adapt (soon will), but older versions must use xed :2023.07.09.
This was missed while backporting the new `spack info` command from spack#40326. Variants should be sorted by name when invoking `spack info --variants-by-name`.
…tory (spack#41000) * grep WM_PROJECT_VERSION from etc/bashrc This fixes the problem when building from a manually checked out repo which might have a different version wrt the one defined in the spack package (e.g. anything later than 5.0 is known as 5.x by the build system) * patch applies to just 5.0, in newer versions it is already addressed In `5.20171030` there's a commit OpenFOAM/OpenFOAM-5.x@c66fba3 very similar (almost identical) to what the patch `50-etc.patch` does. So the patch should not be applied to other than `5.0` otherwise it errors. References: - https://github.com/OpenFOAM/OpenFOAM-5.x/commits/20171030/etc/bashrc - https://github.com/OpenFOAM/OpenFOAM-5.x/blob/197d9d3bf20ac0641a8fe4f57be6a6325ca834b1/etc/bashrc#L45-L47
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
) * [mfem] Add a patch to resolve issue spack#41382 * [mfem] Spack CI wants "patch URL must end with ?full_index=1"
* Add maintainers to fdb * Add maintainers to eckit * Add maintainers to mekit * Add maintainers to eccodes * Add maintainers to ecbuild * Add climbfuji to eccodes maintainers
* gidgetlab: add new package * Convert both cachetools and aiohttp to optional deps with variants * Fix forgotten variant conditional on cachetools dependency * Add git url and main version for dev workflows * Fix variant and dependency ordering * Remove cachetools variant and merge dependency with aiohttp variant
* py-gidgethub: add new package * Add main branch version and scope flit/flit-core dependency * Update var/spack/repos/builtin/packages/py-gidgethub/package.py Co-authored-by: Manuela Kuhn <36827019+manuelakuhn@users.noreply.github.com> * Add optional dependencies as variants of package * Add git url for main version * Fix variant and dependency ordering --------- Co-authored-by: Manuela Kuhn <36827019+manuelakuhn@users.noreply.github.com>
|
This includes the final version of spack#35975. |
gartung
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
spack info --variants-by-name(bugfix: sort variants inspack info --variants-by-namespack/spack#41389)+gslib+shared+miniappsbuild (MFEM: Add a patch to fix the+gslib+shared+miniappsbuild spack/spack#41399)