| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
GitLab's .patch URLs only provide abbreviated hashes, while .diff URLs
provide full hashes. There does not seem to be a parameter to force
.patch URLs to also return full hashes, so we should make sure to use
the .diff ones.
|
|
|
|
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
(#40643)
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
GitLab's .patch URLs do not provide stable/full hashes, while .diff URLs
do. See #40656 for more information.
|
|
Includes Score-P 8.3 and Cubew/cubelib 4.8.2.
|
|
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com>
|
|
|
|
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com>
|
|
* Docs: Add version range example to conditional dependencies
* Add when context manager example
|
|
While e.g. GNU patch 2.7.6 (as provided by homebrew) would apply the previous
version of this patch without problems, Apple's patch 2.0-12u11-Apple fails
to find out which file to patch.
Adding two lines to the patch fixes that. Renamed the patch in order to
not require a `spack clean -m`.
|
|
|
|
|
|
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
|
|
* gromacs: add 2022.6, 2023.2 versions
* gromacs: add version 2023.3
|
|
|
|
when verbose (#40634)
|
|
* gromacs +cp2k: build in CI
* libxsmm: x86 only
* attempt to fix dbcsr + new mpich
* use c11 standard
* gromacs: does not depend on dbcsr
* cp2k: build with cmake in CI, s.t. dbcsr is a separate package
* cp2k: cmake patches for config files and C/C++ std
* cp2k: remove unnecessary constraints due to patch
|
|
* [add] py-corner: new package
* py-corner: remove py-wheel dependence with respect to reviewing commentary
---------
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
|
|
With the introduction of multiple build dependencies from the same package in the DAG, we need to minimize a few weights accounting for edges rather than nodes. If we don't do that we might have multiple "optimal" solutions that differ only in how the same nodes are connected together. This commit ensures optimal versions are picked per parent in case of multiple choices for a dependency.
|
|
Co-authored-by: adamjstewart <adamjstewart@users.noreply.github.com>
|
|
* add recipes for sphinx-book-theme and its dependencies if unknown
* fix version and mission https
* fix based on reviewers remarks
|
|
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
|
|
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
|
|
Co-authored-by: LydDeb <lyderic.debusschere@eolen.com>
|
|
* py-statsmodels: add 0.14.0
* Fix style
* Update var/spack/repos/builtin/packages/py-statsmodels/package.py
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
* Update var/spack/repos/builtin/packages/py-statsmodels/package.py
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
* Remove python limits
* Remove comment
---------
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
* py-dcm2bids: add 3.1.0
* Fix python restriction
|
|
* py-bidscoin: add 4.1.1
* Fix style
* Fix restrictions for dependencies
|
|
* py-cykhash: adding new package py-cykhash
* py-hmmlearn: adding new package py-hmmlearn
* py-macs3: adding new package py-macs3
* py-macs3: adding python version restriction and other changes.
|
|
Fix the following syntax which validates only the first array entry:
```python
"compilers": {
"type": "array",
"items": [
{
"type": ...
}
]
}
```
to
```python
"compilers": {
"type": "array",
"items": {
"type": ...
}
}
```
which validates the entire array.
Oops...
|
|
On some systems, multiple pythonx.y are placed in the same prefix as
pythonx (where only one of them is associated with that pythonx).
Spack external detection for Python was willing to register all of
these as external versions. Moreover, the `package.py` for Python
was able to distinguish these.
This can cause an issue for some build systems, which will just look
for python3 for example, so if that python3 is actually python3.6,
and the build system needs 3.7 (which spack may have found in the
same prefix, and offered as a suitable external), it will fail when
invoking python3.
To avoid that issue, we simply avoid treating pythonx.y as external
candidates. In the above case, Spack would only detect a Python 3.6
external, and the build would be forced to use a Spack-built Python
3.7 (which we consider a good thing).
|
|
|
|
|
|
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This adds a `SetupContext` class which is responsible for setting
package.py module globals, and computing the changes to environment
variables for the build, test or run context.
The class uses `effective_deptypes` which takes a list of specs (e.g. single
item of a spec to build, or a list of environment roots) and a context
(build, run, test), and outputs a flat list of specs that affect the
environment together with a flag in what way they do so. This list is
topologically ordered from root to leaf, so that one can be assured that
dependents override variables set by dependencies, not the other way
around.
This is used to replace the logic in `modifications_from_dependencies`,
which has several issues: missing calls to `setup_run_environment`, and
the order in which operations are applied.
Further, it should improve performance a bit in certain cases, since
`effective_deptypes` run in O(v + e) time, whereas `spack env activate`
currently can take up to O(v^2 + e) time due to loops over roots. Each
edge in the DAG is visited once by calling `effective_deptypes` with
`env.concrete_roots()`.
By marking and propagating flags through the DAG, this commit also fixes
a bug where Spack wouldn't call `setup_run_environment` for runtime
dependencies of link dependencies. And this PR ensures that Spack
correctly sets up the runtime environment of direct build dependencies.
Regarding test dependencies: in a build context they are are build-time
test deps, whereas in a test context they are install-time test deps.
Since there are no means to distinguish the build/install type test deps,
they're both.
Further changes:
- all `package.py` module globals are guaranteed to be set before any of the
`setup_(dependent)_(run|build)_env` functions is called
- traversal order during setup: first the group of externals, then the group
of non-externals, with specs in each group traversed topological (dependencies
are setup before dependents)
- modules: only ever call `setup_dependent_run_environment` of *direct* link/run
type deps
- the marker in `set_module_variables_for_package` is dropped, since we should
call the method once per spec. This allows us to set only a cheap subset of
globals on the module: for example it's not necessary to compute the expensive
`cmake_args` and w/e if the spec under consideration is not the root node to be
built.
- `spack load`'s `--only` is deprecated (it has no effect now), and `spack load x`
now means: do everything that's required for `x` to work at runtime, which
requires runtime deps to be setup -- just like `spack env activate`.
- `spack load` no longer loads build deps (of build deps) ...
- `spack env activate` on partially installed or broken environments: this is all
or nothing now. If some spec errors during setup of its runtime env, you'll only
get the unconditional variables + a warning that says the runtime changes for
specs couldn't be applied.
- Remove traversal in upward direction from `setup_dependent_*` in packages.
Upward traversal may iterate to specs that aren't children of the roots
(e.g. zlib / python have hundreds of dependents, only a small fraction is
reachable from the roots. Packages should only modify the direct dependent
they receive as an argument)
|
