Fix package specifications - #424
Merged
Merged
Conversation
Contributor
I think we can drop it for now, and add it later if needed |
jjacobelli
approved these changes
Jan 27, 2022
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
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.
After rapidsai/integration#411 was merged, the build string for our meta-packages changed from
cuda11.5*to justcuda11*. This change caused our Docker builds to stop working.Since we now build with CUDA Enhanced Compatibility, I think it should be fine to drop the
=cudaspec from the strings below. However, an alternative would be to include thecudatoolkitspec as shown below, but I don't think that's necessary.@ethyling, any thoughts here?