Skip to content
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

run_exports missing in cuda-cupti-dev 12.0.* #14

Closed
1 task done
traversaro opened this issue May 9, 2024 · 7 comments
Closed
1 task done

run_exports missing in cuda-cupti-dev 12.0.* #14

traversaro opened this issue May 9, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@traversaro
Copy link
Contributor

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

The issue in #9 was fixed in #10 , however it was fixed for cuda-cupti-dev 12.4.* . However, the conda-forge pinning pins the cuda libraries to 12.0.*, so the fix is not there.

I wonder if you would consider creating a branch v12.0 so that I can create a PR to also fix the problem for 12.0.* ? Thanks! @conda-forge/cuda-cupti

Installed packages

.

Environment info

.
@traversaro
Copy link
Contributor Author

I wonder if you would consider creating a branch v12.0 so that I can create a PR to also fix the problem for 12.0.* ? Thanks! @conda-forge/cuda-cupti

For reference, the PR I would open on the v12.0 is the one with this commit traversaro@b4cf32d .

@jakirkham
Copy link
Member

Can we repodata patch the run_exports field? If so, that seems like the best option

@traversaro
Copy link
Contributor Author

Can we repodata patch the run_exports field? If so, that seems like the best option

I am afraid/could not understand if that is possible, as I guess the run_exports are got from the package itself, not from the repodata, but I would be happy to be wrong.

@traversaro
Copy link
Contributor Author

By the way, I just noticed that the @conda-forge/cuda-cupti team is empty, apparently that is because the mantainer is a team:

extra:
  recipe-maintainers:
    - conda-forge/cuda

so I guess I need to mention @conda-forge/cuda instead.

@jakirkham
Copy link
Member

cc @billysuh7 (to follow up on whether we can create a 12.0 branch and backport this fix)

@jakirkham
Copy link
Member

Addressed in PR: #20

@traversaro
Copy link
Contributor Author

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants