Fix patches for cuda 12.9

[hmaarrfk]

Trying to address #467 (comment)

but will have to verify that this is working by uploading to my channel.

We have an internal test that seems to be failing with the latest 12.9 build.
Checklist

• Used a personal fork of the feedstock to propose changes
• 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 @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[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.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/19908328920. Examine the logs at this URL for more detail.}

[hmaarrfk]

We might want to look into fixing the zstd issues if it is easy.

I’m no bazel expert though

[h-vetinari]

We might want to look into fixing the zstd issues if it is easy.

Bazel is never easy (that's paraphrasing @xhochy, who's much more knowledgeable about this than me). I suggest not to couple the two PRs.

[hmaarrfk]

unfortunately, this still doesn't pass our internal tests.

Other potential patches:
tensorflow/tensorflow#90494

Perhaps we can pull the builds and just try to build 1.20 instead of patching 1.19?

[hmaarrfk]

To be honest, if I were to have done this, this would have appeared as my name.

I could have added aravind's name in the commit message.

[h-vetinari]

git commit --amend --author="aravindhbalaji1985 <[email protected]>" --date="Mon, 25 Aug 2025 15:15:14 -0700"

[hmaarrfk]

Thanks this helps and I’ll keep this in my backpocket for future patching!