2.4.1 backports

[hmaarrfk]

A few fixes to backport small lifts from the 2.5.X branch back to the 2.4.1 at user requests.

• Relax pin for pytorch-gpu/pytorch-cpu package -- Closes pytorch-gpu 2.4.1 package for linux-64, python 3.10, CUDA 12.0 variant doesn't exist #338
• Others as they come in.

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.

[hmaarrfk]

Workflow cancelled to save resources

[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/13092701177. Examine the logs at this URL for more detail.}

[h-vetinari]

Thanks! I was considering doing this when the queue has cleared up a bit (after all the fixes, tensorflow and pytorch 2.6), especially since there are viable work-arounds in the meantime.

[hmaarrfk]

no problem ,i have a repo data patch (i think....)

[hmaarrfk]

@h-vetinari i feel like this should actually be

Suggested change

	- pytorch {{ version }}=cuda*_{{ blas_impl }}*{{ PKG_BUILDNUM }} # [megabuild and cuda_compiler_version != "None"]
	- pytorch {{ version }}=cpu_{{ blas_impl }}*{{ PKG_BUILDNUM }} # [megabuild and cuda_compiler_version == "None"]
	- pytorch {{ version }}=cuda*_{{ blas_impl }}*_{{ PKG_BUILDNUM }} # [megabuild and cuda_compiler_version != "None"]
	- pytorch {{ version }}=cpu_{{ blas_impl }}*_{{ PKG_BUILDNUM }} # [megabuild and cuda_compiler_version == "None"]

[h-vetinari]

It doesn't make much of a difference (except exercising the new glob-matcher); the build number is always separated from the build hash, so there can be no spurious match even without the underscore. 🤷

[hmaarrfk]

yeah i guess cpu_*5 can't match with cuda126*305

[h-vetinari]

With conda-forge/conda-forge-repodata-patches-feedstock#956 merged, there shouldn't be an immediate need for this anymore AFAICT. We did a bunch of relevant backports in #322 and a pinning update in #325, so I think we can probably let v2.4.x go into well-deserved retirement...