MNT: Re-rendered with conda-build 3.18.10, conda-smithy 3.6.2, and co…

[kayarre]

Checklist

• [x] Used a fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [x] Reset the build number to 0 (if the version changed)
• [x] 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.

code>@<space/conda-forge-admin, please rerender

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

[wolfv]

Hi, great! Thanks.

Is there a particular need for this rebuild? I'm happy to merge it otherwise!

[kayarre]

I am new at this. I was trying to update the version.

[wolfv]

okay! did you change meta.yaml in the recipe folder? usually you'll have to replace the version and SHA256 sums:

https://github.com/conda-forge/openexr-feedstock/blob/master/recipe/meta.yaml

you can find the sha256 sum by downloading the tarball, and running sha256sum myfile.tar.gz on the (Linux) command line (not sure what the command would be for OS X or Windows).

[kayarre]

I did and I did update the sha256sum. I also modified the build.sh , but I am not sure it is correct.

[wolfv]

then you might need to push these changes? I checked 3 times now, I can't see meta.yaml in this PR :)

[kayarre]

Closing, am not sure what I did wrong.

[wolfv]

maybe what you were missing is:

git add recipe/meta.yaml
git commit -am 'update openexr version'
git push

Would be great if you could add the updated meta.yaml! Then the new version will be released.

[wolfv]

if you check your branch, it still has the current meta.yaml:

https://github.com/kayarre/openexr-feedstock/tree/master/recipe