You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll note that I don't consider this a concretizer bug and I think this change is the ideal way to resolve the problem: we intend that a when spec like [email protected] applies to 1.5 as well as 1.5.1 (in order to allow specifying @1.5 to mean all instances of 1.5.x). Given that, @1.5 is ambiguous when a package has both 1.5/1.5.1.
In other words, a package could legitimately request:
In which case we want foo to depend on x and y when @1.5.1.
Avoiding this issue in the case of votca would be complicated: Spack would have to analyze the depends_on clauses to check whether x and y are conflicting and if the when_specs are simultaneously satisfiable; it would then have to further extrapolate that a user wouldn't actually request x and y together (in this case where x=[email protected] and y=[email protected]). To be clear I don't think even the new concretizer would attempt this: it just outputs whether the constraints are satisfiable and doesn't attempt an alternative interpretation of the constraints in the case that they aren't.
This brings me back to the discussion in #8957. In general, I agree, I should be able to say something like depends_on('[email protected]') and have Spack know I mean 3.7.X. I also wish there was an easier way to handle things like patch('foo.patch', when='@3.2') when a package contains 3.2 and 3.2.1. My first thought was to change the behavior depending on whether or not a package actually contains both 3.2 and 3.2.1, but I can see how that would make concretizer design a nightmare.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #13831