[packaging] Stricter install requirements in setup.cfg
#3135
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.
This fixes the failures of the "wheelvalidation" GH action in random PRs after archspec 0.2.3 release which breaks ReFrame. The problem is the following:
The
install_requires
in oursetup.cfg
is too loose, stating only the package names not versions. When the CI tries to create the wheel, it fetches the latest archspec which then breaks us. I've made theinstall_requires
stricter to avoid such problems. We should make sure to update alsosetup.cfg
in the next release of archspec.