fix opencolorio recipe build number

[ndeybach]

As discussed in #155 (comment) , the ocio output had a shared build number. Meaning when oiio updated and the global build number was reset ... ocio was also reset.

Introduce a separate (not auto discovered by regro-bot) build number for ocio.

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.

[ndeybach]

@conda-forge-admin, please rerender

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

[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 (using the @ notation) 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 pinnings.
• 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/27565803236. Examine the logs at this URL for more detail.}

[ndeybach]

@conda-forge-admin, please rerender

[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 (using the @ notation) 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 pinnings.
• 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/27566508333. Examine the logs at this URL for more detail.}

[ndeybach]

@conda-forge-admin, please rerender

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[ndeybach]

@h-vetinari ,

I had some CI rerenderer problem that I bypassed with a local rerender. Seems to have worked.

I think with what I just did we loose the regro-bot auto detect update and PR for ocio. But since ocio is not updated as often as oiio and usually an ocio update has a oiio update associated ... I think we should be fine if we check manually oiio when an ocio update is detected.

Though I would think supporting multiple versions / targets with regro-bot could be a nice improvement (didn't see an obvious existing PR / work on such a thing though).

---

So in current state are we good to merge ?

Considering the existing builds do we let them be or do we need to yank them or anything similar ?

[h-vetinari]

Thanks!