Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libignition-transport9.0.0 #14

Merged
merged 8 commits into from
Nov 2, 2020
Merged

libignition-transport9.0.0 #14

merged 8 commits into from
Nov 2, 2020

Conversation

Tobias-Fischer
Copy link
Contributor

@Tobias-Fischer Tobias-Fischer commented Nov 1, 2020

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.

@conda-forge-linter
Copy link

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.

@Tobias-Fischer
Copy link
Contributor Author

Fix #13

@Tobias-Fischer
Copy link
Contributor Author

This fails on osx with error: 'shared_mutex' is unavailable: introduced in macOS 10.12. What is the best way to deal with this? Any clues @conda-forge/libignition-transport4?

@traversaro
Copy link
Contributor

I guess this could be related to conda-forge/conda-forge.github.io#891 . Note that the requirement was introduced in gazebosim/gz-transport#152 .

@Tobias-Fischer
Copy link
Contributor Author

Thanks @traversaro - let's see whether this does the job :)

@Tobias-Fischer
Copy link
Contributor Author

@conda-forge-admin, please rerender

@Tobias-Fischer
Copy link
Contributor Author

Tobias-Fischer commented Nov 1, 2020

This is ready to be merged @conda-forge/libignition-transport4 :)

Please also close #13

@traversaro traversaro mentioned this pull request Nov 2, 2020
3 tasks
@traversaro
Copy link
Contributor

Thanks @Tobias-Fischer ! For the branches for the older major releases, what is the best idea? We just create them if a new minor release of them come out and we need to generate a new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants