summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-07-19justbuild: add v1.1.4 (#38985)Alberto Sartori1-0/+1
2023-07-19modules: use curly braces to enclose value in Tcl modulefile (#38375)Xavier Delaruelle5-44/+95
Use curly braces instead of quotes to enclose value or text in Tcl modulefile. Within curly braces Tcl special characters like [, ] or $ are treated verbatim whereas they are evaluated within quotes. Curly braces is Tcl recommended way to enclose verbatim content [1]. Note: if curly braces charaters are used within content, they must be balanced. This point has been checked against current repository and no unbalanced curly braces has been spotted. Fixes #24243 [1] https://wiki.tcl-lang.org/page/Tcl+Minimal+Escaping+Style
2023-07-19[py-openapi-schema-pydantic] New package (#38973)Jen Herting1-0/+19
2023-07-19[py-langsmith] New package (#38971)Jen Herting1-0/+20
2023-07-19Fetch & patch: actually acquire stage lock, and many more issues (#38903)Harmen Stoppels17-219/+210
* Fetching patches wouldn't result in acquiring a stage lock during install * The installer would acquire a stage lock *after* fetching instead of before, leading to races * The name of the stage for patches was random, so on build failure (where stage dirs are not removed), these directories would continue to exist after a second successful install. * There was this redundant "composite fetch" object -- there's already a composite stage. Remove this. * For some reason we do *double* shasum validation of patches, before and after compression -- that's just too much? I removed it.
2023-07-19[py-uc-micro-py] New package (#38967)Jen Herting1-0/+18
2023-07-19[py-pydub] new package (#38966)Jen Herting1-0/+18
2023-07-19[py-hatch-requirements-txt] new package (#38965)Jen Herting1-0/+19
2023-07-19[py-ffmpy] New package (#38964)Jen Herting1-0/+18
2023-07-19[py-colorama] added version 0.4.6 (#38737)Jen Herting1-3/+6
* [py-colorama] added version 0.4.6 * [py-colorama] limited py-setuptools dependency
2023-07-19drop redundant rpaths post install (#38976)Harmen Stoppels2-0/+152
Spack heuristically adds `<install prefix>/lib` and `<install prefix>/lib64` as rpath entries, as it doesn't know what the install dir is going to be ahead of the build. This PR cleans up non-existing, absolute paths[^1], which 1. avoids redundant stat calls at runtime 2. drops redundant rpaths in `patchelf`, making it relocatable -- you don't need patchelf recursively then. [^1]: It also removes relative paths not starting with `$` (so, `$ORIGIN/../lib` is retained -- we _could_ interpolate `$ORIGIN`, but that's hard to get right when symlinks have to be taken into account). Relative paths _are_ supported in glibc, but are relative to _the current working directory_, which is madness, and it would be better to drop those paths.
2023-07-19py-cython: add v3.0.0 (#38961)Adam J. Stewart4-8/+15
2023-07-19llnl.util.lock: add type-hints (#38977)Massimiliano Culpo3-71/+114
Also uppercase global variables in the module
2023-07-19Remove `LazyReference` from code (#38944)Massimiliano Culpo73-426/+377
A LazyReference object is a reference to an attribute of a lazily evaluated singleton. Its only purpose is to let developers use shorter names to refer to such attribute. This class does more harm than good, as it obfuscates the fact that we are using the attribute of a global object. Also, it can easily go out of sync with the singleton it refers to if, for instance, the singleton is updated but the references are not. This commit removes the LazyReference class entirely, and access the attributes explicitly passing through the global value to which they are attached.
2023-07-19magma: add package name to conflict messages (#38984)Aiden Grossman1-9/+11
Without the package name being present in the conflict messages, it is significantly more difficult to debug concretization failures in environments that contain many packages.
2023-07-19petsc: add version 3.19.3 (#38974)downloadico2-0/+4
2023-07-19rmgdft: add v5.3.1, v5.4.0 and cuda variant (#37813)Emil Briggs1-11/+32
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2023-07-19mesa-glu: Patch register long to long (#38833)Aiden Grossman2-0/+32
mesa-glu still has a couple instances of the register keyword which causes build failures with clang on my platform. This patch removes the register keyword which doesn't have any impact on correctness.
2023-07-19gperf: patch usage of register keyword (#38893)Aiden Grossman2-0/+19
gperf still uses the register keyword in one place which makes compilation fail with c++17. This patch adds in a patch file to remove the usage of the reigster keyword so that it compiles properly.
2023-07-19elfutils: remove conflicts with clang after version 0.186 (#38945)Aiden Grossman1-5/+2
In late 2021 elfutils was patched to make it build with clang, and these patches ended up in version 0.186. This commit updates the conflicts to specify this so elfutils can be built with clang.
2023-07-19amdfftw: turn conflicts into conditional variants (#38221)Carlos Bederián1-76/+51
2023-07-19palace: fix bugs introduced in #38910 (#38983)Sebastian Grimberg1-9/+9
2023-07-18Improve RDKit package (#36566)Rocco Meli3-8/+73
2023-07-18Windows testing: enable tests for installer components (#36970)markus-ferrell1-8/+0
These tests now work without any changes to core. Furthermore, it is surprising that they had to be disabled (at least, as long as the installer.py tests are run on Windows: these tests are more-basic and their functionality would have been exercised automatically).
2023-07-18palace: add v0.11.2 (#38910)Sebastian Grimberg1-36/+49
2023-07-18py-poetry-core: add 1.6.1 and fix url (#38452)Manuela Kuhn1-3/+12
* py-poetry-core: add 1.6.1 and fix url * Update var/spack/repos/builtin/packages/py-poetry-core/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Re-add python upper bound for older versions * Update var/spack/repos/builtin/packages/py-poetry-core/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> --------- Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2023-07-18Ensure the bootstrap store has a padding length of zero (#38975)Massimiliano Culpo3-17/+27
Without this PR, padded length was propagating from user configuration to bootstrap configuration, and was causing the issue reported in #38963
2023-07-18Windows testing: enable bootstrap test (#36972)markus-ferrell1-2/+0
2023-07-18FleCSPH: update package (#37888)Julien Loiseau1-19/+13
Co-authored-by: Richard Berger <richard.berger@outlook.com>
2023-07-18fftw: fix build with clang15+ (#38889)Aiden Grossman1-0/+7
In Clang 15, -Wint-conversion became an error instead of a warning, breaking the fftw build for clang versions > 15. This patch fixes fftw builds with clang 15+ by passing -Wno-error=int-conversion as a cflag.
2023-07-18test_clear_failures_success: run on Windows too (#36792)markus-ferrell1-2/+3
2023-07-18binary cache docs: remove redundant flag and comment (#38960)Harmen Stoppels1-5/+1
2023-07-18e4s cray: expand spec list (#38947)eugeneswalker1-0/+13
* e4s cray: expand spec list * unzip: require %gcc * remove datatrasnferkit
2023-07-18Windows testing: enable architecture test (#36973)markus-ferrell1-2/+0
Works out of the box: remove skip.
2023-07-18Windows testing: enable "spack clean" tests (#36840)markus-ferrell1-3/+0
They work out out of the box on windows. Simply removing skips.
2023-07-18chameleon: update to version 1.2.0 (#38936)fpruvost1-1/+3
2023-07-18buildcache push: make --allow-root the default and deprecate the option (#38878)Harmen Stoppels15-220/+38
Without --allow-root spack cannot push binaries that contain paths in binaries. This flag is almost always needed, so there is no point of requiring users to spell it out. Even without --allow-root, rpaths would still have to be patched, so the flag is not there to guarantee binaries are not modified on install. This commit makes --allow-root the default, and drops the code required for it. It also deprecates `spack buildcache preview`, since the command made sense only with --allow-root. As a side effect, Spack no longer depends on binutils for relocation
2023-07-18Pin Spack dev dependencies on RtD (#38950)Massimiliano Culpo1-0/+5
2023-07-18Fix default construction of locks (#38953)Massimiliano Culpo1-1/+1
This fixes a typo introduced in a refactor
2023-07-18Update dbcsr and cp2k to latest version (#38939)Taillefumier Mathieu2-11/+22
Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
2023-07-18modules: add support for conflict in lua modulefile (#36701)Xavier Delaruelle9-59/+122
Add support for conflict directives in Lua modulefile like done for Tcl modulefile. Note that conflicts are correctly honored on Lmod and Environment Modules <4.2 only if mutually expressed on both modulefiles that conflict with each other. Migrate conflict code from Tcl-specific classes to the common part. Add tests for Lmod and split the conflict test case in two. Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2023-07-18"spack develop": always pull full history for git repos (#38343)Peter Scheibel4-9/+66
2023-07-18Update package.py (#38946)Houjun Tang1-0/+1
2023-07-17wannier90 github (#38927)Rocco Meli1-0/+2
2023-07-17meson: add 1.2.0, 1.1.1 and 1.0.2 (#38935)Michael Kuhn1-0/+3
2023-07-18added new packages (#38941)Andrey Perestoronin16-0/+96
2023-07-18Update gsi-ncdiag/1.1.1 sha256 (#38943)David Huber1-1/+1
2023-07-17py-soupsieve: add 2.4.1 (#38929)Manuela Kuhn1-3/+5
2023-07-17py-setuptools: add 68.0.0 (#38930)Manuela Kuhn1-0/+5
* py-setuptools: add 68.0.0 * [@spackbot] updating style on behalf of manuelakuhn
2023-07-17py-setuptools-rust: add 1.6.0 (#38932)Manuela Kuhn1-3/+6