summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2021-10-19Gitlab pipelines: use images from the Spack organization (#26796)Massimiliano Culpo7-16/+14
2021-10-18Speed up pipeline generation (#26622)Scott Wittenburg2-16/+38
- [x] Stage already concretized specs instead of abstract ones - [x] Reduce number of network calls by reading naughty list up front
2021-10-18new package: berkeleygw (#21455)Miguel Dias Costa1-0/+220
2021-10-18cosma: add new versions and improve package (#24136)Harmen Stoppels1-30/+61
* cosma: add new versions and improve package * Move method below depends_on's
2021-10-18patches: make re-applied patches idempotent (#26784)Todd Gamblin4-25/+137
We use POSIX `patch` to apply patches to files when building, but `patch` by default prompts the user when it looks like a patch has already been applied. This means that: 1. If a patch lands in upstream and we don't disable it in a package, the build will start failing. 2. `spack develop` builds (which keep the stage around) will fail the second time you try to use them. To avoid that, we can run `patch` with `-N` (also called `--forward`, but the long option is not in POSIX). `-N` causes `patch` to just ignore patches that have already been applied. This *almost* makes `patch` idempotent, except that it returns 1 when it detects already applied patches with `-N`, so we have to look at the output of the command to see if it's safe to ignore the error. - [x] Remove non-POSIX `-s` option from `patch` call - [x] Add `-N` option to `patch` - [x] Ignore error status when `patch` returns 1 due to `-N` - [x] Add tests for applying a patch twice and applying a bad patch - [x] Tweak `spack.util.executable` so that it saves the error that *would have been* raised with `fail_on_error=True`. This lets us easily re-raise it. Co-authored-by: Greg Becker <becker33@llnl.gov>
2021-10-18httpie: add v2.6.0 (#26791)Mickaël Schoentgen2-13/+18
Signed-off-by: Mickaël Schoentgen <contact@tiger-222.fr> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2021-10-18file and python dependents: add missing dependencies (#26785)Seth R. Johnson4-3/+34
* py-magic: delete redundant package This package is actually named py-python-magic (since the project itself is "python-magic"). * New package: libmagic * Py-python-magic: add required runtime dependency on libmagic and new version * Py-filemagic: add required runtime dependency * py-magic: restore and mark as redundant This reverts commit 4cab7fb69e2c2b8098895bee92aabe5df8b7aaaa. * file: add implicit dependencies and static variant Replaces redundant libmagic that I added. Compression headers were previously being picked up from the system. * Fix py-python-magic dependency * Update python version requirements
2021-10-18tasmanian: add smoke test (#26763)Miroslav Stoyanov1-1/+9
2021-10-18Make macOS installed libraries more relocatable (#26608)Seth R. Johnson7-115/+395
* relocate: call install_name_tool less * zstd: fix race condition Multiple times on my mac, trying to install in parallel led to failures from multiple tasks trying to simultaneously create `$PREFIX/lib`. * PackageMeta: simplify callback flush * Relocate: use spack.platforms instead of platform * Relocate: code improvements * fix zstd * Automatically fix rpaths for packages on macOS * Only change library IDs when the path is already in the rpath This restores the hardcoded library path for GCC. * Delete nonexistent rpaths and add more testing * Relocate: Allow @executable_path and @loader_path
2021-10-18docutils > 0.17 issue with rendering list items in sphinx (#26355)Shahzeb Siddiqui2-0/+4
* downgrade_docutils_version * invalid version * Update requirements.txt * Improve spelling and shorten the reference link * Update spack.yaml * update version requirement * update version to maximum of 0.16 Co-authored-by: bernhardkaindl <43588962+bernhardkaindl@users.noreply.github.com>
2021-10-18Remove unused exist_errors in installer.py (#26650)Harmen Stoppels1-5/+1
2021-10-18Don't print error output in the test whether gpgconf works (#26682)Harmen Stoppels1-1/+1
2021-10-18allow multiple values for tensile_architecture and expand the gpu list for ↵Sreenivasa Murthy Kolam1-9/+20
rocm-4.3.1 (#26745)
2021-10-18environment-modules: add version 5.0.1 (#26786)Xavier Delaruelle1-1/+2
2021-10-18Revert 19736 because conflicts are avoided by clingo by default (#26721)Harmen Stoppels2-98/+95
2021-10-17py-jupytext: add new package (#26732)Valentin Volkl3-0/+70
* py-jupytext: add new package * Apply suggestions from code review Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * update jupytext dependencies * Apply suggestions from code review Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * py-jupytext: remove py-jupyerlab dependency Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2021-10-17py-vermin: add latest version 1.3.0 (#26787)Morten Kristensen1-1/+2
2021-10-17py-gevent: add version 1.5 (#26731)Valentin Volkl1-4/+10
* py-gevent: add version 1.5 * py-gevent: update dependencies for v1.5.0 * Apply suggestions from code review Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-gevent/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2021-10-17Add ECP tags for CoPA and related packages (#26739)Sam Reeve5-8/+12
* Add ECP tags for CoPA (and related) packages * Update CoPA maintainers
2021-10-17nlohmann-json: update to version 3.10.4 (#26779)Ryan Mast1-0/+2
2021-10-16[Fix for the GitLab CI] phist: prefer @1.9.5 (1.9.6 is not compatible w/ ↵Bernhard Kaindl1-3/+70
mpich%gcc:9) (#26773) * phist: Prefer 1.9.5 (1.9.6 uses mpi_f08, but not available in CI) * phist: remove dupe of 1.9.5, missing preferred=True Also, for 1.9.6, patch the (most, one does not work) tests to use
2021-10-15Update GASNet package.py to include version 2021.9.0 (#26736)Scot Halverson1-0/+1
2021-10-15libblastrampoline: add v3.1.0 (#26769)Mosè Giordano1-0/+1
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
2021-10-15Fix ruby dependent extensions. (#26729)Brice Videau2-6/+17
* Fix ruby dependent extensions. * Added Kerilk as maintainer.
2021-10-15GCC: Conflict for <12 for M1 (#26318)Axel Huebl1-0/+4
aarch64/M1 is only a supported build combination for GCC in the planned GCC 12+ release.
2021-10-15py-charset-normalizer: add v2.0.7 (#26756)Mickaël Schoentgen1-0/+19
Signed-off-by: Mickaël Schoentgen <contact@tiger-222.fr>
2021-10-15py-rdflib: add 6.0.2 (#26757)Manuela Kuhn1-2/+5
2021-10-15py-ipykernel: add 6.4.1 and fix deps (#26758)Manuela Kuhn1-3/+10
2021-10-15py-setuptools: add 58.2.0 (#26759)Manuela Kuhn1-0/+1
2021-10-15py-jupyter-client: add 6.1.12 (#26760)Manuela Kuhn1-0/+4
2021-10-15Revert "Don't run lsb_release on linux (#26707)" (#26754)Harmen Stoppels2-4/+1
This reverts commit fcac95b0654a84151ad51a9123f74e8cdfcf8d26.
2021-10-15EnvironmentModifications: allow disabling stack tracing (#26706)Harmen Stoppels2-14/+29
Currently Spack keeps track of the origin in the code of any modification to the environment variables. This is very slow and enabled unconditionally even in code paths where the origin of the modification is never queried. The only place where we inspect the origins of environment modifications is before we start a build, If there's an override of the type `e.set(...)` after incremental changes like `e.append_path(..)`, which is a "suspicious" change. This is very rare though. If an override like this ever happens, it might mean a package is broken. If that leads to build errors, we can just ask the user to run `spack -d install ...` and check the warnings issued by Spack to find the origins of the problem.
2021-10-15libabigail: add v2.0 (#26753)Vanessasaurus2-1/+42
Signed-off-by: vsoch <vsoch@users.noreply.github.com> Co-authored-by: vsoch <vsoch@users.noreply.github.com>
2021-10-15Disable parallel builds in groff and gosam-contrib (#26730)Joseph Wang2-1/+5
Work around to #26726 and #26714
2021-10-15HiOp: add v0.5.0 + small changes in dependencies (#26744)Cameron Rutherford1-3/+5
2021-10-15paraview: add adios2 variant (#26728)kwryankrattiger1-0/+7
2021-10-15Removing NCEP Post (ncep-post). (#26749)Timothy Brown2-399/+0
UPP and ncep-post are the same package, so this PR removes the duplication. ncep-post was originally named after the upstream repo that now changed its name to UPP.
2021-10-15vtk: modify conflict between osmesa and qt (#26752)Eric Brugger1-3/+2
2021-10-14Stand-alone tests: disallow re-using an alias (#25881)Tamara Dahlgren4-8/+82
It can be frustrating to successfully run `spack test run --alias <name>` only to find you cannot get the results because you already use `<name>` in some previous stand-alone test execution. This PR prevents that from happening.
2021-10-14Remove extra tag assignments (#26692)Tamara Dahlgren4-12/+4
2021-10-14py-datalad: add 0.15.2 (#26750)Manuela Kuhn1-1/+2
2021-10-14cp2k: use variant propagation trick for virtuals (#26737)Harmen Stoppels1-5/+6
2021-10-14ASP-based solver: add a rule for version uniqueness in virtual packages (#26740)Massimiliano Culpo4-0/+43
fixes #26718 A virtual package may or may not have a version, but it never has more than one. Previously we were missing a rule for that.
2021-10-14add py-pyh5md and update py-espressopp (#26746)Christoph Junghans2-0/+21
* add py-pyh5md and update py-espressopp * Update package.py
2021-10-14libfive: Add all variants, +qt needs qt@5.15.2:+opengl (#26629)Bernhard Kaindl1-3/+22
Refresh of deps to fix the build and add variants from CMakeLists.txt
2021-10-14sombrero: add version 2021-08-16 (#26741)Mosè Giordano1-0/+2
2021-10-14vc: Enable the testsuite, excluding tests failing on Zen2 (#26699)Bernhard Kaindl2-0/+35
This fixes running the testsuite, it adds the package virtest for it.
2021-10-14switch to the smoke testing included in heffte (#26720)Miroslav Stoyanov1-54/+9
2021-10-14alpgen: new package (#26713)iarspider7-0/+6922
Co-authored-by: Bernhard Kaindl <43588962+bernhardkaindl@users.noreply.github.com>
2021-10-14edm4hep: new version, fix tests (depends on catch2) (#26679)Thomas Madlener2-0/+16