summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-03-10feh: add v3.9.1 (#35858)Alec Scott1-0/+1
2023-03-10Add packages OSPRay, rkcommon, Open VKL, and Open Image Denoise (#35530)kwryankrattiger5-1/+186
2023-03-10Update yaFyaml, pFlogger, and gFTL versions, add list_url (#35968)Matthew Thompson5-0/+9
* Update yaFyaml, pFlogger, and gFTL versions * Add list_url
2023-03-10py-deap: newer version can use newer setuptools (#35986)Erik Heeren1-1/+3
* py-deap: newer version can use newer setuptools * Update var/spack/repos/builtin/packages/py-deap/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> --------- Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2023-03-10scons: add version 4.5.1. (#35990)H. Joe Lee1-1/+2
2023-03-10py-scikit-learn: add v1.2.2 (#35982)Adam J. Stewart1-1/+3
2023-03-10rivet: remove tag (deleted by upstream developers) (#35971)Valentin Volkl1-1/+0
2023-03-10spectre: add v2023.03.09 (#35972)SXS Bot1-0/+3
Co-authored-by: sxs-bot <sxs-bot@users.noreply.github.com>
2023-03-10cgns: enable tools (#35713)nicolas le goff2-1/+72
2023-03-09QMCPACK v3.16.0 (#35967)Paul R. C. Kent1-0/+2
2023-03-09reorder_flags: properly handle flags from concrete reused specs (#35951)Greg Becker2-4/+23
2023-03-09scalasca: add 2.6.1 (#35970)Michael Kuhn1-5/+11
2023-03-09[liburing] Adds liburing package (#35762)Matthieu Dorier1-0/+24
* [liburing] Adds liburing package * Update var/spack/repos/builtin/packages/liburing/package.py * [liburing] Added conflicts for darwin and windows platforms --------- Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2023-03-09concretizer.yaml: document valid values for granularity (#35961)Harshula Jayasuriya1-4/+5
2023-03-09Automated deployment to update package flux-core 2023-03-09 (#35956)Vanessasaurus1-0/+1
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
2023-03-09scorep: fix dependencies (#35966)Michael Kuhn1-5/+6
The overlapping dependency version ranges caused the concretizer to pick version 7.1 even though version 8.0 is available: ``` ==> Error: No version for 'cubelib' satisfies '@4.7.1' and '@4.8' ``` Moreover, Score-P 8.0 requires libbfd: ``` configure: error: bfd.h required ```
2023-03-09bdftopcf: add v1.1 (#35845)Alec Scott1-0/+1
2023-03-09Deprecate elpa rc2 (#35953)Rocco Meli1-0/+1
2023-03-09fontconfig: add v2.14.2 (#35861)Alec Scott1-0/+1
2023-03-09hpctoolkit: adjust dependency and conflict for xz (#35950)Mark W. Krentel1-1/+2
Hpctoolkit doesn't build cleanly with xz 5.2.7 and 5.2.8 due to a misuse of the symver attribute. This is now fixed in 5.2.9 and later.
2023-03-09New packages: py-fireworks, py-flask-paginate (#35939)Benjamin Meyers2-0/+56
* New packages: py-fireworks, py-flask-paginate * [@spackbot] updating style on behalf of meyersbs
2023-03-09New package py-custodian (#35938)Benjamin Meyers1-0/+27
* New package py-custodian * [@spackbot] updating style on behalf of meyersbs
2023-03-09Update py-boltons (#35937)Benjamin Meyers1-0/+1
2023-03-08gawk: add v5.2.1 (#35863)Alec Scott1-0/+1
2023-03-08git: add 2.39.2 (#35911)Michael Kuhn1-0/+2
2023-03-08libuv-julia: fix mtime again (#35945)Michael Kuhn1-5/+12
On some systems touch runs out of order, so set a equal mtimes to the relevant files
2023-03-08gcc: Patch building of GCC 5.1-12.1 with glibc >= 2.36 (#35798)Maciej Wójcik3-0/+59
2023-03-08Halide: Add 15.0.0 (#35924)Teo1-6/+6
2023-03-08nek5000/nekcem: test_install -> check_install (#35925)Tamara Dahlgren2-2/+2
2023-03-08Add pika 0.13.0 and pika-algorithms 0.1.2 (#35933)Auriane R2-0/+3
* Add last release of pika-algorithms + version constraint * Add pika release 0.13.0
2023-03-08p7zip: update checksum for 17.05 (#35923)Michael Kuhn1-1/+1
See https://github.com/p7zip-project/p7zip/issues/220
2023-03-08rmgdft: add version 5.0.5 (#35922)Emil Briggs1-0/+1
* Updated for version 5.0.5.
2023-03-08amrex: add v23.03 (#35765)Weiqun Zhang1-4/+6
2023-03-08intel-mpi-benchmarks: variant and conflicts fixes (#35670)Jean-Baptiste Besnard1-18/+28
2023-03-08Provide openmp from rocm-open-extras when tensile uses openmp (#35767)renjithravindrankannath2-3/+35
* Provide openmp from rocm-open-extras when tensile uses openmp * Correcting audit check failure in rocm-openmp-extras dependency * Fixing style check error * rocm-openmp-extras required instead of llvm-amdgpu both varient
2023-03-08add logging to help users debug where external file searches are taking a ↵Peter Scheibel1-0/+13
long time (#35900)
2023-03-08qwt: lift restrictions on qt version and added an opengl variant and VisIt ↵nicolas le goff3-2/+21
use (#35734)
2023-03-08gdb: version 13.1 and debuginfod support (#35769)Robert Underwood1-16/+12
* gdb: version 13.1 and debuginfod * gdb: update to autotools helpers --------- Co-authored-by: Robert Underwood <runderwood@anl.gov>
2023-03-08gitlab ci: Provide a knob to control untouched spec pruning (#35274)Scott Wittenburg3-22/+149
When untouched spec pruning is enabled, specs possibly affected by a change cannot be pruned from a pipeline. Previously spack looked at all specs matching changed package names, and traversed dependents of each, all the way to the environment root, to compute the set of environment specs possibly affected by a change (and thus, not candidates for pruning). With this PR, when untouched spec pruning is enabled, a new environment variable can control how far towards the root spack traverses to compute the set of specs possibly affected by a change. SPACK_UNTOUCHED_PRUNING_DEPENDENT_DEPTH can be set to any numeric value before the "spack ci generate" command is called to control this traversal depth parameter. Setting it to "0" traverses only touched specs, setting it to "1" traverses only touched specs and their direct dependents, and so on. Omitting the variable results in the previous behavior of traversing all the way to the root. Setting it to a negative value means no traversal is done, and always yields an empty set of possibly affected specs (which would result in the max pruning possible).
2023-03-08buildcache create: reproducible tarballs (#35623)Harmen Stoppels2-50/+177
Currently `spack buildcache create` creates compressed tarballs that differ between each invocation, thanks to: 1. The gzip header containing mtime set to time.time() 2. The generated buildinfo file which has a different mtime every time. To avoid this, you have to explicitly construct GZipFile yourself, since the Python API doesn't expose the mtime arg, and we have to manually create the tarinfo object for the buildinfo metadata file. Normalize mode: regular files & hardlinks executable by user, dirs, symlinks: set 0o755 permissions in tarfile; other files use 0o644
2023-03-08new py-thop package (#35889)Sangu Mbekelu1-0/+22
* "new py-thop package" * [@spackbot] updating style on behalf of Sangu-Mbekelu * Update package.py modified the url and dependencies --------- Co-authored-by: Sangu Mbekelu <s.mbekelu9@gmail.com>
2023-03-08py-openmesh: new package (#35907)Erik Heeren1-0/+25
* py-openmesh: new package * Update var/spack/repos/builtin/packages/py-openmesh/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> --------- Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2023-03-08mfem: add missing cublas for cuda support (#35608)Aaron Black1-1/+1
2023-03-08py-parse-type: new package (#35909)Erik Heeren1-0/+18
2023-03-08parallelio: new version (#35553)Gerhard Theurich1-0/+1
2023-03-08newly released 0.8.3 (#35910)Alberto Invernizzi1-0/+1
2023-03-08Split `satisfies(..., strict=True/False)` into two functions (#35681)Massimiliano Culpo39-857/+1055
This commit formalizes `satisfies(lhs, rhs, strict=True/False)` and splits it into two functions: `satisfies(lhs, rhs)` and `intersects(lhs, rhs)`. - `satisfies(lhs, rhs)` means: all concrete specs matching the left hand side also match the right hand side - `intersects(lhs, rhs)` means: there exist concrete specs matching both lhs and rhs. `intersects` now has the property that it's commutative, which previously was not guaranteed. For abstract specs, `intersects(lhs, rhs)` implies that `constrain(lhs, rhs)` works. What's *not* done in this PR is ensuring that `intersects(concrete, abstract)` returns false when the abstract spec has additional properties not present in the concrete spec, but `constrain(concrete, abstract)` will raise an error. To accomplish this, some semantics have changed, as well as bugfixes to ArchSpec: - GitVersion is now interpreted as a more constrained version - Compiler flags are interpreted as strings since their order is important - Abstract specs respect variant type (bool / multivalued)
2023-03-08New package: py-imbalanced-learn (#35895)Benjamin Meyers1-0/+37
* New package: py-imbalanced-learn * Fix typo * [@spackbot] updating style on behalf of meyersbs * Update var/spack/repos/builtin/packages/py-imbalanced-learn/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> --------- Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2023-03-08bump elpa (#35908)Rocco Meli1-0/+3
2023-03-08Update and fix py-meldmd (#35783)Benjamin Meyers2-6/+80
* Update/fix py-meldmd; update openmm * Restrict filter_file based on openmm version * Updates based on Adam's feedback * [@spackbot] updating style on behalf of meyersbs * Break up long filter_file Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> --------- Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>