Age | Commit message (Collapse) | Author | Files | Lines |
|
* py-pytorch-lightning: add +extra variant
* Update dependencies
* py-fsspec: add v2023.1.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Loïc Pottier <pottier1@llnl.gov>
|
|
|
|
|
|
* Add packages for scine modules
- lbfgspp (dependency for scine-utilities)
- scine-core
- scine-utilities and py-scine-utilities (virtual)
- scine-readuct and py-scine-readuct (virtual)
- scine-sparrow and py-scine-sparrow (virtual)
- scine-database and py-scine-database (virtual)
- scine-molassembler and py-scine-molassembler (virtual)
- scine-xtb and py-scine-xtb (virtual)
- py-scine-chemoton
- py-scine-puffin
* Fix line-length for flake8
* Remove virtual dependencies
* Update detection of boost, minor fixes in packages / dependencies
* Correctly declare build-only dependencies, add git versions
* Add sparrow dummy packages, fix dependencies
* Rename latest version from develop to master
* Restore original sparrow package
* Also rename latest version for chemoton and puffin
|
|
* py-flatten-dict: require poetry to build.
The sources seem to contain a bundled, auto-generated `setup.py`.
Building with `pip` insist on using Poetry as mentioned in
`pyproject.toml`, so require it as a build dependency.
* Update var/spack/repos/builtin/packages/py-flatten-dict/package.py
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
* Update var/spack/repos/builtin/packages/py-flatten-dict/package.py
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
* py-lazy: add 1.4 and 1.5
* py-lazy: add url_for_version
|
|
* Add package `py-continuum`
* `py-continuum`: missing `py-pytest-mock` dependency
* `py-continuum`: add missing python dependency
* [@spackbot] updating style on behalf of thomas-bouvier
* Patch to remove useless `prospector` package
* Link to original PR
Co-authored-by: thomas-bouvier <thomas-bouvier@users.noreply.github.com>
|
|
* py-pyspark: new versions
* py-py4j: new versions
* py-py4j: more style
* py-py4j: even more style
* py-spark, py4j: review remarks
|
|
Currently we print "sha256 checksum failed for [file]. Expected X but
got Y".
This PR extends that message with file size and contents info:
"... but got Y. File size = 123456 bytes. Contents = b'abc...def'"
That way we can immediately see if the file was downloaded only
partially, or if we downloaded a text page instead of a binary, etc.
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
|
|
Currently 6.0.0 fails on develop about incorrect shasum, but I can't
reproduce; maybe the download was temporarily unavailable.
|
|
|
|
py-scipy 1.6 and older come with pre cython-ized files that
use the _PyGen_Send symbol that was removed from python 3.10.0.161,
so do not build these old versions with python 3.10.1 and later
|
|
|
|
First added as user-hdnnp in version 20210527.
|
|
* Add package `py-nvidia-dali`
* Add linux check
* Add missing deps
|
|
|
|
|
|
* Initial srcml
* [srcml]
- Fixed dependencies likely will need some more rework
- Disabling packaging cmake file (for now)
- Added patch to fix issue with source code library import
* [srcml] updated copyright
* [srcml] requires antlr complied with -fPIC
* [srcml] cleaned up dependencies
* [srcml] flake8
* [srcml] limiting boost versions
Co-authored-by: Benjamin Meyers <bsmits@rit.edu>
Co-authored-by: qwertos <qwertos@users.noreply.github.com>
|
|
|
|
* Add whip 0.1.0
* Make pika depend on whip@0.1.0
Co-authored-by: msimberg <msimberg@users.noreply.github.com>
|
|
* Updated for RMG version 5.0.1
* Update var/spack/repos/builtin/packages/rmgdft/package.py
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
|
|
Parts of libgcrypt should not be optimized with -O1/2/3, so it's best to
let the build system do that; the build system cannot know the compiler
wrapper would inject optimization flags
|
|
|
|
|
|
|
|
|
|
When running unit-test the test/ci.py module is leaving
garbage (help.sh, test.sh files) in the current working
directory.
This commit changes the current working directory to a
temporary path before those files are created.
|
|
* ParaView/VTK: Patch xdmf2 for HDF5 1.13
* Meson: update meson build system for 0.64
* ParaView: Change HDF5 1.13 patch to 1.13.1/2 patchs
* Mesa: Remove legacy mesa option from meson_args
* Use append to assemble meson args
|
|
|
|
and htslib (#35118)
* samtools: add version 1.16.1 (for real this time!)
also, fix Copyright date
* bcftools and htslib: fix Copyright date
|
|
* Update variant & compiler propagation
* Add the info for non boolean variants
* Add example for multi variants
|
|
|
|
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
|
|
|
|
|
* freeimage: fails to compile with c++17, use c++14
Only `opencascade` when a (non-default) variant depends on `freeimage`, which seems to have gone unmaintained. There are c++17 standard violations [[1]]( https://en.cppreference.com/w/cpp/language/except_spec) in the code, so we can at most expect c++14. Since some compilers default to c++17 (gcc-12) we need to be explicit.
* freeimage: install directly in prefix
* freeimage: fix inverted patch
|
|
* samtools: add version 1.6.1
* htslib: update version to 1.6
* bcftools: update version to 1.6
|
|
|
|
* [antlr] modernize config arg processing
* [antlr] added pic variant
* [antlr] flake8
|
|
|
|
concretize/install (#34958)
* environments: don't rewrite relative view path, expand path on cli ahead of time
Currently if you have a spack.yaml that specifies a view by relative
path, Spack expands it to an absolute path on `spack -e . install` and
persists that to disk.
This is rather annoying when you have a `spack.yaml` file inside a git
repo, cause you want to use relative paths to make it relocatable, but
you constantly have to undo the changes made to spack.yaml by Spack.
So, as an alternative:
1. Always stick to paths as they are provided in spack.yaml, never
replace them with a canonicalized version
2. Turn relative paths on the command line into absolute paths before
storing to spack.yaml. This way you can do `spack env create --dir
./env --with-view ./view` and both `./env` and `./view` are resolved
to the current working dir, as expected (not `./env/view`). This
corresponds to the old behavior of `spack env create`.
* create --with-view always takes a value
|
|
|