bump build number (hpp-fcl update)

conda-forge / pinocchio-feedstock

A conda-smithy repository for pinocchio.

BSD 3-Clause "New" or "Revised" License

12 stars 10 forks source link

bump build number (hpp-fcl update) #10

Closed jcarpent closed 4 years ago

jcarpent commented 4 years ago

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] 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)
[x] Ensured the license file is being packaged.

conda-forge-linter commented 4 years ago

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.

jcarpent commented 4 years ago

@conda-forge-admin, please rerender

conda-forge-linter commented 4 years ago

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

I tried to re-render for you, but it looks like there was nothing to do.

wolfv commented 4 years ago

I think you might have to wait a little longer if you just merged the other PR, as the conda CDN usually takes at least 30 minutes to make the updated package available ...

wolfv commented 4 years ago

also if you dynamically link against the HPP-FCL and the binary compatibility hasn't changed, and run_exports isn't set too strictly, you don't necessarily have to rebuild I believe :)

jcarpent commented 4 years ago

@wolfv You're right. But the binary compatibility has changed in hpp-fcl 1.2.0 and I've forgotten to update this package before the new release of Pinocchio. Hard to think of all dependencies at all time.