Apply fix for cupy issue 8654 from PR 8655

[dagardner-nv]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

Applies fix for https://github.com/cupy/cupy/issues/8654 from PR https://github.com/cupy/cupy/pull/8655

Closes https://github.com/nv-morpheus/Morpheus/issues/1938

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jakirkham]

Thanks David! 🙏

Could you please squash the patch to one diff?

Otherwise this looks good

[jakirkham]

@conda-forge-admin , please re-render

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11284004994.}

[jakirkham]

Hmm...looks like there is an issue with re-rendering. Will explore that separately. Let's go ahead and get this in

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[jakirkham]

Hmm...looks like there is an issue with re-rendering. Will explore that separately.

Addressing with PR: https://github.com/conda-forge/cupy-feedstock/pull/289

[leofang]

Thanks to you both, @dagardner-nv @jakirkham!