Merge fron upstream 2025-02-25 #511
Merged
Conversation
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
Co-authored-by: LMS Bioinformatics <[email protected]> Co-authored-by: Massimiliano Culpo <[email protected]>
Co-authored-by: sxs-bot <[email protected]>
…#48754) With CFLAGS, the code path in the amdfftw build system will bypass the logic around AMD_ARCH. --------- Co-authored-by: vijay kallesh <[email protected]>
* Add a message for CMake incremental build Requested message to explain CMake phase is getting skipped. * [@spackbot] updating style on behalf of psakievich * Update import --------- Co-authored-by: psakievich <[email protected]>
* ICU4C: Don't reference a spec variant on a platform on which it's not defined * icu4c: no cxx flag on Windows
* Use more idiomatic construct, shorten recipe * Remove deprecated versions, and associated patches * Remove v10.0.0
Current location is within the Spack prefix, which causes builds to pollute VCS with stage artifacts and generally inflates the Spack install prefix. This PR moves it to the user cache location now that we can consistently support paths with spaces on Windows.
* fix regression `apple-clang` vs `%apple-clang` * use f-strings * remove --verbose flag from LDFLAGS
…pack#48918) * Apply workarounds for oneAPI compiler for ascent problem with build * Use the way with use patch through the PR address * stylecheck - missing comma
Signed-off-by: Shane Nehring <[email protected]> Co-authored-by: Shane Nehring <[email protected]>
* Add possibility to build nwchem from master branch * add oneapi@2025: patch for @7.2.3 --------- Co-authored-by: eugeneswalker <[email protected]>
* Python: add new versions * black
… be resolved (spack#49124) Currently, we have `config:shared_linking:missing_library_policy` to error or warn when shared libraries cannot be resolved upon install. The new `spack verify libraries` command allows users to run this post install hook at any point in time to check whether their current installations can resolve shared libs in rpaths.
This commit adds version 1.14.0 of the vecmem package.
…es (spack#49141)" (spack#49172) This reverts commit 0da5baf.
ParaView 5.12.0 through 5.13.2 do not compile. See https://gitlab.kitware.com/vtk/vtk/-/issues/19620.
* pyAMReX: 25.02 * PICMI: 0.33.0 * WarpX: 25.02 * `amrex +fft` depends on `pkgconfig` * Updated CMake logic uses `pkgconfig`
…h autoload none. Ref issue: 42535 (spack#48050) * Update survey package file with latest releases and python path settings for building with autoload none. * Submitting reformatted file. * update survey package file with libmonitor dependency changes, take out py-gpustat, and minor comment change. * Trigger build.
* py-sympy: add v1.13.1
Currently, environments can end up with higher priority than `-C` custom
config scopes and `-c` command line arguments sometimes. This shouldn't
happen -- those explicit CLI scopes should override active environments.
Up to now configuration behaved like a stack, where scopes could be only be
pushed at the top. This PR allows to assign priorities to scopes, and ensures
that scopes of lower priorities are always "below" scopes of higher priorities.
When scopes have the same priority, what matters is the insertion order.
Modifications:
- [x] Add a mapping that iterates over keys according to priorities set when
adding the key/value pair
- [x] Use that mapping to allow assigning priorities to configuration scopes
- [x] Assign different priorities for different kind of scopes, to fix a bug, and
add a regression test
- [x] Simplify `Configuration` constructor
- [x] Remove `Configuration.pop_scope`
- [x] Remove `unify:false` from custom `-C` scope in pipelines
On the last modification: on `develop`, pipelines are relying on the environment
being able to override `-C` scopes, which is a bug. After this fix, we need to be
explicit about the unification strategy in each stack, and remove the blanket
`unify:false` from the highest priority scope
Signed-off-by: Massimiliano Culpo <[email protected]>
VariantMap.concrete is unused, and would be incorrect if it were used due to conditional variants. Just let the Spec dictate what is concrete and what is not.
…k#49180) Bumps [sphinx](https://github.com/sphinx-doc/sphinx) from 8.2.0 to 8.2.1. - [Release notes](https://github.com/sphinx-doc/sphinx/releases) - [Changelog](https://github.com/sphinx-doc/sphinx/blob/v8.2.1/CHANGES.rst) - [Commits](sphinx-doc/sphinx@v8.2.0...v8.2.1) --- updated-dependencies: - dependency-name: sphinx dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Fix setup.fish syntax * Simplify conditional in share/spack/setup-env.fish Co-authored-by: Wouter Deconinck <[email protected]> --------- Co-authored-by: Wouter Deconinck <[email protected]>
* davix: add v0.8.8, v0.8.9, v0.8.10 * davix: url_for_version * davix: depends on googletest when @0.8.8: (type test, maybe build) * davix: define DAVIX_TESTS
…e-from-upstream-2025-02-24
…e-from-upstream-2025-02-25
greenc-FNAL
force-pushed
the
maintenance/merge-from-upstream-2025-02-25
branch
from
c8e7461 to
05f0f64
Compare
gartung
approved these changes
Feb 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 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.
whichandwhich_string(Add type-hints towhichandwhich_stringspack/spack#48554)spack.build_systemstyping (improve build system api / signatures spack/spack#48590)spack.platformspackage spack/spack#47756)+docsvariant and manpages (hpctoolkit: Add+docsvariant and manpages spack/spack#48566)not inandis not(style: fixnot inandis notspack/spack#48831)ruff format(update pyproject.toml forruff formatspack/spack#48823)flang-newandflangin newer LLVM versions (spack compiler find:flang-newin newer LLVM versions spack/spack#48914)Spec.virtual->spack.repo.PATH.is_virtualspack/spack#48986)rust@nightly(Fix installingrust@nightlyspack/spack#49098)