Age | Commit message (Collapse) | Author | Files | Lines |
|
Co-authored-by: Nathan Hanford <hanford1@llnl.gov>
|
|
* Fix to concretize.lp
do not allow dev specs to be reused
Co-authored-by: Gregory Becker <becker33@llnl.gov>
|
|
Spack added support in #24639 for ad-hoc Git-commit-hash-based
versions: A user can install a package x@hash, where X is a package
that stores its source code in a Git repository, and the hash refers
to a commit in that repository which is not recorded as an explicit
version in the package.py file for X.
A couple issues were found relating to this:
* If an environment defines an alternative package repo (i.e. with
repos.yaml), and spack.yaml contains user Specs with ad-hoc
Git-commit-hash-based versions for packages in that repo,
then as part of retrieving the data needed for version comparisons
it will attempt to retrieve the package before the environment's
configuration is instantiated.
* The bookkeeping information added to compare ad-hoc git versions was
being stripped from Specs during concretization (such that user
Specs which succeeded before concretizing would then fail after)
This addresses the issues:
* The first issue is resolved by deferring access to the associated
Package until the versions are actually compared to one another.
* The second issue is resolved by ensuring that the Git bookkeeping
information is explicitly applied to Specs after they are concretized.
This also:
* Resolves an ambiguity in the mock_git_version_info fixture used to
create a tree of Git commits and provide a list where each index
maps to a known commit.
* Isolates the cache used for Git repositories in tests using the
mock_git_version_info fixture
* Adds a TODO which points out that if the remote Git repository
overwrites tags, that Spack will then fail when using
ad-hoc Git-commit-hash-based versions
|
|
Co-authored-by: Mikael Simberg <mikael.simberg@iki.if>
|
|
* curl: nss deprecated since 7.82
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit updates the `gpg publish` command to work with the mirror
arguments, when trying to push keys to a mirror.
- [x] update `gpg publish command
- [x] add test for publishing GPG keys and rebuilding the key index within a mirror
|
|
|
|
|
|
|
|
|
|
|
|
(#29995)
* zstd: bring back libs=shared,static and compression=zlib,lz4,lzma variants
Should make building `gcc+binutils ^zstd libs=static` a bit easier (this
is the case where we don't control the compiler wrappers of gcc because
of bootstrapping, nor of ld because of how gcc invokes the linker).
|
|
* Use auto_or_any_combination_of for AMD GPU architecture variant
* Make consistent rocmlibs amdgpu_target variants
* Propagate amdgpu_target variant
* Fix amdgpu_target=auto
* Fix amdgpu_target=auto setting HCC_AMDGPU_TARGET
* Tighten HIP CMake requirements
Co-authored-by: Teodor Nikolov <teodor.nikolov22@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* abi-dumper: remove custom phases
* apktool: remove custom phases, add v2.6.1
* aragorn: remove custom phases
* ascent: remove custom phases
* astral: remove custom phases, add v5.7.1
* bigdft: remove redundant phase definitions
* bazel: remove custom phases phase definitions
* blasr: remove custom phases phase definitions
* bmake: remove custom phases phase definitions, add v20220330
* botan: remove custom phases phase definitions
* breakdancer: remove custom phases phase definitions
* dnstracer: remove custom phases phase definitions
* conduit: remove custom phases phase definitions
* eclipse-gcj-parser: remove custom phases phase definitions
* eem: remove custom phases phase definitions
* fasttree: remove custom phases phase definitions
* fleur: remove custom phases phase definitions
* fpm: remove custom phases phase definitions
* genie: remove custom phases phase definitions
* gluegen: remove custom phases phase definitions
* gnat: remove custom phases phase definitions
* hpgmg: remove custom phases phase definitions
* karma: remove custom phases phase definitions
* libc: remove custom phases phase definitions
|
|
* expat: Deprecate 2.4.6
* expat: Increase detail on deprecation of 2.4.5
|
|
|
|
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 3.1.0 to 3.1.1.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/9c644ca2ab8e57ea0a487b5ec2f8290740378bfd...21c0493ecfd34b1217f0a90ec19a327f3cc0a048)
---
updated-dependencies:
- dependency-name: actions/setup-python
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
|
Restrict lbann to use v1.3.0 of this package
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
|
|
|
|
|
|
|
|
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 2 to 3.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v2...v3)
---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 2 to 3.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](https://github.com/actions/download-artifact/compare/v2...v3)
---
updated-dependencies:
- dependency-name: actions/download-artifact
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
|
|
|
|
|