summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-10-07sysstat: add v12.7.6 (#46812)Wouter Deconinck1-2/+10
2024-10-07busybox: add v1.37.0 (#46810)Wouter Deconinck1-0/+1
2024-10-07gawk: add v5.3.1 (#46809)Wouter Deconinck1-0/+1
2024-10-07py-numpy: add v2.1.2 (#46817)Adam J. Stewart1-0/+1
2024-10-07lis: add v2.1.5 and v2.1.6 (#46820)Filippo Barbari1-0/+2
2024-10-07gradle: add v8.10.x (#46821)Filippo Barbari1-0/+3
2024-10-07gtkplus: depends_on libxfixes when @:2 (#46824)Wouter Deconinck1-0/+1
2024-10-07py-validators: add v0.34.0 (#46825)Wouter Deconinck1-1/+2
2024-10-07libdrm: add v2.4.123 (#46831)Wouter Deconinck1-0/+1
2024-10-07activemq: add v5.18.6, v6.1.3 (#46833)Wouter Deconinck1-1/+11
2024-10-07libdwarf: add v0.11.0 (#46834)Wouter Deconinck1-0/+1
2024-10-07ocl-icd: add v2.3.2 (#46806)Wouter Deconinck1-0/+1
2024-10-07codecov: increase project threshold to 2% (#46828)Todd Gamblin1-1/+1
We run tests for more python versions on `develop` than we do for PRs, so codecov project status is nearly always failing. There is about a 1% difference in max coverage between `develop` tests and PR tests, so we should increase the project threshold to 2% to allow for this difference. The purpose of the project test on PRs is just to make sure that nothing done on the PR massively affects coverage of code not covered by the PR. This is valuable, but rare. It only really affects PRs that deal with test or coverage configuration. - [x] change project coverage threshold from .2% to 2% Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-10-06Add v3.0.0 version for libfirefly package (#46801)ĐARK々MÁTTER1-0/+2
* Add v3.0.0 version for libfirefly package * [@spackbot] updating style on behalf of tbhaxor --------- Co-authored-by: tbhaxor <tbhaxor@users.noreply.github.com>
2024-10-06root: add v6.32.06 (#46804)Wouter Deconinck1-0/+5
2024-10-06gdbm: add v1.24 (#46808)Wouter Deconinck1-0/+1
2024-10-05Remove -ld_classic from all packages (#46608)Adam J. Stewart7-26/+2
2024-10-05py-krb5: add v0.7.0 (#46799)Wouter Deconinck1-0/+2
* py-krb5: add v0.7.0 * [@spackbot] updating style on behalf of wdconinc --------- Co-authored-by: wdconinc <wdconinc@users.noreply.github.com>
2024-10-05build(deps): bump docker/setup-buildx-action from 3.7.0 to 3.7.1 (#46796)dependabot[bot]1-1/+1
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.7.0 to 3.7.1. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](https://github.com/docker/setup-buildx-action/compare/8026d2bc3645ea78b0d2544766a1225eb5691f89...c47758b77c9736f4b2ef4073d4d51994fabfe349) --- updated-dependencies: - dependency-name: docker/setup-buildx-action 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-04`gc`: restrict to specific specs (#46790)Todd Gamblin4-2/+30
`spack gc` has so far been a global or environment-specific thing. This adds the ability to restrict garbage collection to specific specs, e.g. if you *just* want to get rid of all your unused python installations, you could write: ```console spack gc python ``` - [x] add `constraint` arg to `spack gc` - [x] add a simple test Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-10-04mapl: add 2.49.0 (#46787)Matt Thompson1-0/+3
* mapl: add 2.49.0 * Remove unneeded depends_on
2024-10-04py-rpds-py: add v0.18.1 (#46786)Wouter Deconinck1-1/+4
2024-10-04py-cookiecutter: add v2.6.0 (fix CVE) (#46762)Wouter Deconinck2-6/+25
* py-cookiecutter: add v2.6.0 * py-poyo: add v0.5.0 * py-poyo: fix style
2024-10-04hdf5: use spack installed zlib (#46612)Satish Balay2-0/+18
Avoid that hdf5 searches all search paths for ZLIB.cmake config files (inluding /usr/lib), before it looks for zlib without cmake config files, which is how Spack installs it
2024-10-04freetype: add v2.13.3 (#46751)Wouter Deconinck1-0/+1
2024-10-04WarpX: 24.10 (#46763)Axel Huebl4-37/+103
* WarpX: 24.10 This updates WarpX and dependencies for the 24.10 release. New features: - EB runtime control: we can now compile with EB on by default, because it is not an incompatible binary option anymore - Catalyst2 support: AMReX/WarpX 24.09+ support Catalyst2 through the existing Conduit bindings * Fix Typo in Variant Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com> * Improve Python Dep Version Ranges * Add Missing `-DWarpX_CATALYST` * AMReX: Missing CMake Options for Vis --------- Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2024-10-04re2c: rework package to use multiple build systems (#46748)Massimiliano Culpo8-51/+36
Signed-off-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2024-10-04justbuild: add version 1.3.2 (#46777)Alberto Sartori1-0/+1
2024-10-04abinit: fixed "if" statement bug (#46785)downloadico1-2/+2
fixed "if" statement when selecting the linear algebra flavor.
2024-10-04py-rsatoolbox: add v0.2.0 (#46780)Manuela Kuhn1-0/+5
2024-10-04raja-perf: Fix support for SYCL (#46782)Adrien Bernede1-1/+1
2024-10-04mold: add 2.34.1 (#46783)Mikael Simberg1-0/+1
2024-10-04laynii: add new package (#46781)Manuela Kuhn1-0/+31
2024-10-04py-glmsingle: Add v1.2 (#46776)Manuela Kuhn1-0/+2
2024-10-04pika: add 0.29.0 (#46778)Mikael Simberg1-1/+4
2024-10-04clingo: fix build with Python 3.13+ (#46775)Harmen Stoppels2-0/+13
Python 3.9 deprecated `PyEval_InitThreads` and kept it as a no-op, and Python 3.13 deleted the function. The patch removes calls to it.
2024-10-04Separate bootstrapping tests for Windows from other platforms (#46750)Massimiliano Culpo1-43/+47
This allows us to keep the workflow file tidier, and avoid using indirections to perform platform specific operations. Signed-off-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2024-10-04umpire: re-instate lost depend on camp ~rocm when umpire itself has ~rocm ↵Mikael Simberg1-0/+1
(#46747)
2024-10-04py-mpi4py: add v4.0.0 (#46652)Satish Balay2-4/+5
* py-mpi4py: add v4.0.0 * sensei: update mpi4py dependency build with py-mpi4py@4.0.0 due to fatal no such file or directory error * petsc4py: update license, and remove C++/Fortran dependency
2024-10-04paraview: add new v5.13.1 release (#46695)Vicente Bolea1-2/+3
2024-10-04build(deps): bump docker/setup-buildx-action from 3.6.1 to 3.7.0 (#46768)dependabot[bot]1-1/+1
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.6.1 to 3.7.0. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](https://github.com/docker/setup-buildx-action/compare/988b5a0280414f521da01fcc63a27aeeb4b104db...8026d2bc3645ea78b0d2544766a1225eb5691f89) --- updated-dependencies: - dependency-name: docker/setup-buildx-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>
2024-10-03armadillo: add v12.8.4, v14.0.2 (#46761)Wouter Deconinck1-0/+4
* armadillo: add v12.8.4, v14.0.2 * armadillo: fix git --------- Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2024-10-03duckdb: add v1.1.1, remove 0.7.1->0.8.1, update variants (#46743)Teague Sterling1-26/+45
Signed-off-by: Teague Sterling <teaguesterling@gmail.com> Co-authored-by: Bernhard Kaindl <bernhardkaindl7@gmail.com>
2024-10-03update CHANGELOG.md (#46758)Harmen Stoppels1-0/+71
2024-10-03hiop: add v1.1.0 (#46764)Satish Balay1-0/+3
2024-10-03py-keras: add v3.6 (#46767)Adam J. Stewart1-3/+7
2024-10-03at-spi2-core: add v2.52.0,2.54.0 (#46769)Teague Sterling1-0/+2
Signed-off-by: Teague Sterling <teaguesterling@gmail.com>
2024-10-03doxygen: add v1.12.0 (#46752)Wouter Deconinck1-10/+13
2024-10-03catch2: add v3.7.1 (#46759)Wouter Deconinck1-0/+1
2024-10-03Better docs and typing for `_setup_pkg_and_run` (#46709)Todd Gamblin1-8/+52
There was a bit of mystery surrounding the arguments for `_setup_pkg_and_run`. It passes two file descriptors for handling the `gmake`'s job server in child processes, but they are unsed in the method. It turns out that there are good reasons to do this -- depending on the multiprocessing backend, these file descriptors may be closed in the child if they're not passed directly to it. - [x] Document all args to `_setup_pkg_and_run`. - [x] Document all arguments to `_setup_pkg_and_run`. - [x] Add type hints for `_setup_pkg_and_run`. - [x] Refactor exception handling in `_setup_pkg_and_run` so it's easier to add type hints. `exc_info()` was problematic because it *can* return `None` (just not in the context where it's used). `mypy` was too dumb to notice this. Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>