[draft] Backport fix for ambiguous boost::ratio usage

conda-forge / boost-feedstock

A conda-smithy repository for boost.

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

15 stars 41 forks source link

Closed traversaro closed 6 months ago

traversaro commented 6 months ago

Checklist

[x] Used a personal 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.

traversaro commented 6 months ago

@conda-forge-admin, please rerender

conda-forge-webservices[bot] commented 6 months 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.

h-vetinari commented 6 months ago

This should wait until we get upstream feedback in https://github.com/boostorg/chrono/pull/75

traversaro commented 6 months ago

It turns out that the ambiguous call to ratio was not my problem, see https://github.com/RoboStack/ros-noetic/issues/448#issuecomment-1962127319 . The cleanup may still be useful, so I will leave open the upstream PR, but it does not make sense to backport the cleanup, so I will close this PR.