Full rebuild Septmber 2026 : bump ros2-distro-mutex to 0.21.0 and build number to 26 and switch to new pinning mechanism - #43
Full rebuild Septmber 2026 : bump ros2-distro-mutex to 0.21.0 and build number to 26 and switch to new pinning mechanism#43traversaro wants to merge 7 commits into
Conversation
|
| - 2.17 # [linux and not riscv64] | ||
| - 2.39 # [linux and riscv64] | ||
| - 2.17 # [linux and (x86_64 or aarch64) and os.environ.get("CF_CUDA_ENABLED", "False") == "True"] | ||
| - 12.0 # [osx] |
There was a problem hiding this comment.
I think we will run into quite a few errors on macOS if we pin this below 14.0. I'm curious whether there's any way to "force update" this generated file. #31 (comment)
There was a problem hiding this comment.
Yes, we can add the override in vinca_pinning.yaml's pinning_overrides.
There was a problem hiding this comment.
Ah, okay, cool. I didn't notice that
|
The build fails with: probably we need to remove the channels from the invocation, and override that. |
|
Also updating the compiler bring its own regressions: fixed upstream in ros2/rmw#423 . |
The inclusion of <stdbool.h> in time.h resolves compilation issues caused by changes in the include chain of rcutils.
|
New failure: this is similar to what @mini-1235 mentioned, we need to override an higher |
|
On macOS we have an actual failure OpenCV 5 failure: |
In particular, I would like to test the new pinning machinery introduced in RoboStack/vinca#138 . This effectively updates OpenCV to 5.* that I guess is mostly untested in ROS world (also other rolling distro efforts like's idesign0's brew one, nix overlay and bazel just ping opencv to 4.*) so I would expect a few failures due to that.