[suitespare] updated the pinning to the latest 5.4 for Windows.

[seanyen]

Checklist

• Used a 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-linter]

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) and found it was in an excellent condition.

[seanyen]

Now the suitesparse for Windows has been updated to 5.4 with the latest blas convention. I am suggesting to update the pinning.
conda-forge/suitesparse-feedstock#65
conda-forge/suitesparse-feedstock#66

[seanyen]

@conda-forge/core This is ready for review and merge. Thanks!

[CJ-Wright]

This most likely needs a migration

[CJ-Wright]

This needs a migration (most likely)

[seanyen]

This needs a migration (most likely)

@CJ-Wright What does that mean? How do I make it happen?

[CJ-Wright]

Put a copy of this file in the migrations folder of this repo.
Then modify the file to match the changes you made here:

suitesparse:
  - 5.6                # [not win]
  - 5.4                # [win]

[seanyen]

@CJ-Wright Thanks for the tip! Hope I get the migration description right...

[isuruf]

Btw, how many existing packages use suitesparse on windows? I assume one or two

[CJ-Wright]

you need to remove this change this will go in once the migration has finished.

[seanyen]

Btw, how many existing packages use suitesparse on windows? I assume one or two

@isuruf Frankly I don't know. Any commands to quickly check it? And it seems to me that there are two ways: Pinning a version in conda_build_config.yaml or adding a migrator. What's the consideration which to use?

[isuruf]

Looks like it is only cvxopt. (Inspected https://conda.anaconda.org/conda-forge/win-64/repodata.json)
So, if you can revert back to the original commit, I'll merge.

There's no point doing a migration for 1 package.

[seanyen]

@isuruf Done. I removed the migrator file.