Allow other compatible versions of regex#6
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For the use of
lidrsinAetherus, I would like to allow for other compatible regex vers to be used.The problem stemmed from using netcdf, which under the hood needs hdf5, but the version packaged in the nix flakes you have on
Aetherusis too high for the version ofnetcdfused in the project, but updatingnetcdfrequired a higher version ofregexand clashing with the hard requirement forlidrs.Hence, allow other version of regex to be used here allows
Aetherusto look for a version supported for all its dependencies