-
Notifications
You must be signed in to change notification settings - Fork 55
Remove dask, pytorch, and nvidia channels #768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jameslamb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support this change generally, but I think that sed change needs to look a little different.
Co-authored-by: James Lamb <jlamb@nvidia.com>
|
The My read of that is "there are not |
|
Well that's problematic. It means we've been pulling invalid environments so far. cufile packages didn't exist on arm until 12.2, so if we were getting them from nvidia (likely the correct diagnosis) we were getting packages that weren't actually constrained to the right cuda-version. I wonder why we have these though; our cufile dependency should be conditional on the cuda version. |
|
Ah the problem is kvikio's recipe, not cudf's. I have to look a bit closer to figure out the correct fix here though; kvikio has a tighter connection to cufile than cudf, so I don't know if simply removing the dependency is the right answer here. |
|
Yeah was just going to say... I just looked and see |
|
OK I've put in a temporary patch in rapidsai/kvikio#753 to get around this issue. We'll need a follow up that sets up the correct constraints, probably with a variant build. |
jameslamb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
|
/merge |
Contributes to rapidsai/build-planning#166