diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2023-03-17 11:36:29 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-17 11:36:29 +0100 |
| commit | 97193a25ce0c0df6a03cc7d719b0e6e25a37d3a1 (patch) | |
| tree | 5faa6313da7035996dc49a9282655a03933105b7 /share | |
| parent | 5bf96561eeaec8728e86634a049074175ec017ec (diff) | |
| download | spack-97193a25ce0c0df6a03cc7d719b0e6e25a37d3a1.tar.gz spack-97193a25ce0c0df6a03cc7d719b0e6e25a37d3a1.tar.bz2 spack-97193a25ce0c0df6a03cc7d719b0e6e25a37d3a1.tar.xz spack-97193a25ce0c0df6a03cc7d719b0e6e25a37d3a1.zip | |
Mitigation for GitVersion bug when no `=reference` is given (#36159)
* ASP-based solver: use satisfies instead of intersects
They are semantically equivalent for concrete versions,
but the GitVersion.intersects implementation is buggy
* Mitigation for git version bug
fixes #36134
This commit works around the issue in #36134, by using
GitVersion.satisfies instead of GitVersion.intersects
There are still underlying issues when trying to infer the
"reference version" when no explicit one is given, but:
1. They are not reproducible with our synthetic repo
2. They occur only when the `git.<xxx>` form of Git version
is used
Here we just work around the user facing issue and ensure
the tests are correct with our synthetic repository.
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions