Re-build after servers brought online

[mattwthompson]

Let's see if git --allow-empty can work as intended for re-triggering CI without adding spaces!

Checklist

• [x] 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 code>@<space/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.

[mattwthompson]

Tag #25

[Lnaden]

I've re-triggered the #24 builds, if those pass, this should not be needed, correct?

[mattwthompson]

I'd think that would work but I'm not entirely sure? I'd hope that the chances of either working are pretty high, so consider this a backup (and apologies, submitted this before I saw you were already working on it)

[Lnaden]

It's all good. If what I'm doing fails, we can use this as a fallback.

[Lnaden]

If we need to use this to re-trigger the builds, then the correct way to do it is update the meta.yaml file and bump the build number. That's the mechanic which we can use to trigger the next build to get this out there, and conda will resolve higher build numbers first in priority.

[Lnaden]

I think something is up with the build since it came from not the official mechanisms. Can you update the meta.yaml file and bump the build: 0 to build: 1 (I think thats what that key is called). That should trigger the mechanism to signal official builds.

[mattwthompson]

Ah, yes, I forgot about the build numbers. Let's give this a whirl