summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-10-29builder.py: builder_cls should be associated to spack.pkg module (#47269)Harmen Stoppels2-5/+14
2024-10-29directives_meta.py: use startswith to test module part of spack.pkg (#47270)Harmen Stoppels1-1/+2
2024-10-28exawind: remove generated fortran dependencies (#47276)Jon Rood4-117/+47
2024-10-28cmd/solve: use interface from cmd/spec (#47182)Greg Becker4-67/+30
Currently, `spack solve` has different spec selection semantics than `spack spec`. `spack solve` currently does not allow specifying a single spec when an environment is active. This PR modifies `spack solve` to inherit the interface from `spack spec`, and to use the same spec selection logic. This will allow for better use of `spack solve --show opt` for debugging. --------- Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
2024-10-28lammps: add heffte support (#47254)Christoph Junghans2-1/+13
* lammps: add heffte support * Add Richard's suggestion
2024-10-28py-pyscf: add v2.7.0 (#47272)Paul R. C. Kent1-0/+1
2024-10-28feelpp/spack#11 (#47243)Christophe Prud'homme1-0/+32
2024-10-28gdk-pixbuf/atk: delete old versions, make mesonpackage (#47258)Harmen Stoppels3-121/+27
* gdk-pixbuf: delete old versions, make mesonpackage goal is to get rid of `std_meson_args` global, but clean up package while at it. `setup_dependent_run_environment` was removed because it did not depend on the dependent spec, and would result in repeated env variable changes. * atk: idem * fix a dependent
2024-10-28tasmanian: add v8.1 (#47221)Miroslav Stoyanov1-5/+5
Co-authored-by: Bernhard Kaindl <bernhardkaindl7@gmail.com> Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2024-10-28py-non-regression-test-tools: add v1.1.2 & remove v1.0.2 (tag removed) (#47256)teddy1-2/+2
Co-authored-by: t. chantrait <teddy.chantrait@cea.fr>
2024-10-28ML CI: Linux aarch64 (#39666)Adam J. Stewart3-0/+222
* ML CI: Linux aarch64 * Add config files * No aarch64 tag * Don't specify image * Use amazonlinux image Co-authored-by: kwryankrattiger <80296582+kwryankrattiger@users.noreply.github.com> * Update and require * GCC is too old * Fix some builds * xgboost doesn't support old GCC + cuda * Run on newer Ubuntu * Remove mxnet * Try aarch64 range * Use main branch * Conflict applies to all targets * cuda only required when +cuda * Use tagged version * Comment out tf-estimator * Add ROCm, use newer Ubuntu * Remove ROCm --------- Co-authored-by: kwryankrattiger <80296582+kwryankrattiger@users.noreply.github.com>
2024-10-28bazel: add Apple Clang 16 conflict (#47228)Adam J. Stewart1-0/+3
2024-10-28sst: update core, elements, macro to 14.1.0 (#47184)jmlapre3-3/+9
2024-10-28py-hatchet: add v1.4.0 (#47222)Adam J. Stewart5-2/+89
2024-10-28py-mgmetis: fails to build with mpi4py @4: depend on @3 (#47236)Bernhard Kaindl1-1/+1
2024-10-28cpr: add versions up to v1.11 (#47242)Christophe Prud'homme1-0/+3
2024-10-28pango: add v1.54.0 (#47244)Wouter Deconinck1-1/+10
2024-10-28geode: add v1.13.8, v1.14.3, v1.15.1 (#47253)Wouter Deconinck1-5/+12
2024-10-27less: add v661, v668 (#47252)Wouter Deconinck1-4/+8
2024-10-28nano: add v8.1, v8.2 (and v6.4) (#47245)Wouter Deconinck1-2/+7
* nano: add v8.1, v8.2 * nano: depends on gettext * nano: add v6.4
2024-10-27Add nextflow 24.10.0 (#47251)Diego Alvarez S.1-1/+5
2024-10-27Remove a few redundant imports (#47250)Harmen Stoppels6-15/+8
* remove self-imports * remove unused imports
2024-10-27gha: circular imports: pin (#47248)Harmen Stoppels1-1/+1
2024-10-27explicit splice: do not fail for bad config replacement if target not ↵Greg Becker2-2/+42
matched (#46925) Originally, concretization failed if the splice config points to an invalid replacement. This PR defers the check until we know the splice is needed, so that irrelevant splices with bad config cannot stop concretization. While I was at it, I improved an error message from an assert to a ValueError.
2024-10-27silo: resolve hdf5 develop-X.Y branch versions (#39344)William R Tobin1-2/+8
2024-10-27feat: Add OpenColorIO option to OpenImageIO (#47237)Beat Reichenbach3-0/+63
* feat: Add OpenColorIO option to OpenImageIO * style: Pep 8 --------- Co-authored-by: Beat Reichenbach <beatreichenbach@users.noreply.github.com>
2024-10-27pango: deprecate @:1.44 due to CVE (#47232)Wouter Deconinck1-2/+8
2024-10-27NWChem: add TCE_CUDA option (#47191)Jeff Hammond1-0/+8
Signed-off-by: Jeff Hammond <jehammond@nvidia.com>
2024-10-27add the USE_F90_ALLOCATABLE option to Spack (#47190)Jeff Hammond1-0/+4
Signed-off-by: Jeff Hammond <jehammond@nvidia.com>
2024-10-27gem5: new package (#47218)Andrew W Elble1-0/+70
2024-10-27py-olcf-velocity: new package (#47215)Asa1-0/+30
* Add package py-olcf-velocity * Removed trailing newline * Fixed packages description line length --------- Co-authored-by: Asa Rentschler <rentschleraj@ornl.gov>
2024-10-27py-alive-progress: support newer Python (#47220)Adam J. Stewart1-1/+1
2024-10-27byte-lite: new package (#47234)Pranav Sivaraman1-0/+29
* byte-lite: new package * byte-lite: style adjustments
2024-10-27adios2: mark conflict with newer Python@3.11 for @:2.7 (#47219)Adam J. Stewart1-0/+3
2024-10-26yosys: Update to version 0.46, also include 0.43, 0.44 and 0.45 (#47200)Dave Keeshan1-1/+5
2024-10-26Add `-t` short option for `spack --backtrace` (#47227)Todd Gamblin3-4/+5
Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-10-25Add Go 1.23.2, 1.22.8, and 1.22.7 (#47225)Paul1-0/+3
2024-10-25Normalize Spack Win entry points (#38648)John W. Parent4-65/+81
* Normalize Spack Win entrypoints Currently Spack has multiple entrypoints on Windows that in addition to differing from *nix implementations, differ from shell to shell on Windows. This is a bit confusing for new users and in general unnecessary. This PR adds a normal setup script for the batch shell while preserving the previous "click from file explorer for spack shell" behavior. Additionally adds a shell title to both powershell and cmd letting users know this is a Spack shell * remove doskeys
2024-10-25Intel/Oneapi compilers: suppress warnings when using Cray wrappers (#47046)Dom Heinzeller2-6/+8
#44588 we added logic to suppress deprecation warnings for the Intel classic compilers. This depended on matching against * The compiler names (looking for icc, icpc, ifort) * The compiler version When using an Intel compiler with fortran wrappers, the first check always fails. To support using the fortran wrappers (in combination with the classic Intel compilers), we remove the first check and suppress if just the version matches. This works because: * The newer compilers like icx can handle (ignore) the flags that suppress deprecation warnings * The Cray wrappers pass the underlying compiler version (e.g. they report what icc would report)
2024-10-25Packages/javacerts (#47201)Gregory Lee1-0/+39
* new openjdk variant to symlink system certificate * new openjdk variant to symlink system certificate * new openjdk variant to symlink system certificate * new openjdk variant to symlink system certificate * Update var/spack/repos/builtin/packages/openjdk/package.py Co-authored-by: Alec Scott <hi@alecbcs.com> --------- Co-authored-by: Alec Scott <hi@alecbcs.com>
2024-10-25ensure write_fd.close() isn't called when sys.std* cannot be redirectedHarmen Stoppels1-6/+7
2024-10-25Avoid a socket to communicate effectively a bitHarmen Stoppels1-3/+3
2024-10-25Replace MultiProcessFd with Connection objectsHarmen Stoppels2-134/+68
Connection objects are Python version, platform and multiprocessing start method independent, so better to use those than a mix of plain file descriptors and inadequate guesses in the child process whether it was forked or not. This also allows us to delete the now redundant MultiProcessFd class, hopefully making things a bit easier to follow.
2024-10-25build(deps): bump actions/checkout from 4.2.1 to 4.2.2 (#47185)dependabot[bot]8-23/+23
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.1 to 4.2.2. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871...11bd71901bbe5b1630ceea73d27597364c9af683) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-10-25file_cache.py: allow read transaction on uninitialized cache (#47212)Harmen Stoppels2-40/+58
This allows the following ```python cache.init_entry("my/cache") with cache.read_transaction("my/cache") as f: data = f.read() if f is not None else None ``` mirroring `write_transaction`, which returns a tuple `(old, new)` where `old` is `None` if the cache file did not exist yet. The alternative that requires less defensive programming on the call site would be to create the "old" file upon first read, but I did not want to think about how to safely atomically create the file, and it's not unthinkable that an empty file is an invalid format (for instance the call site may expect a json file, which requires at least {} bytes).
2024-10-25Add version 0.0.3836 (#47204)Dave Keeshan1-0/+5
2024-10-25build(deps): bump actions/setup-python from 5.2.0 to 5.3.0 (#47209)dependabot[bot]6-13/+13
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.2.0 to 5.3.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](https://github.com/actions/setup-python/compare/f677139bbe7f9c59b41e40162b753c062f5d49a3...0b93645e9fea7318ecaed2b359559ac225c90a2b) --- updated-dependencies: - dependency-name: actions/setup-python 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>
2024-10-25Add spack short version in config variables (#47016)Jordan Galby4-14/+35
2024-10-24tioga: add v1.2.0. (#47208)Jon Rood1-1/+2
2024-10-24exawind: add v1.1.0. (#47207)Jon Rood1-0/+1