Full Rebuild (Sync) July 2025: bump ros2-distro-mutex to 0.10.0 and build_number to 9 #95
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ok, most of the porting done, now there is the usual cleanup of upstreamed (or outdated) patches, probably the easiest thing is to iterate on this locally with |
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
|
We should consider moving to cyclonedds here as well for MacOS. |
cleanup patches
5 tasks
Signed-off-by: wep21 <[email protected]>
|
The "got segment" message I was using in the test was silenced: ros/robot_state_publisher#206 . |
|
osx-64 failure: I think we fixed this somewhere previously, but I can't see where .. osx-arm64 failure: linux-* failures (very long, just a snippet): win-64 failure: Don't look like any easy wins ... |
We removed the binutils dependency so all that part of backward is not compiled, see RoboStack/ros-humble@9374e56 and RoboStack/ros-kilted#23 . |
For some reason the exit code on macOS are failing in the tests, I skipped it in RoboStack/ros-humble@afe5b72 . |
macOS is failing with a similar error: I guess control_toolbox is missing a link to fmt::fmt, either direct or via a library that exposes fmt in its public headers. |
|
|
It looks like there is an empty |
See RoboStack/ros-humble#320 (comment) , so the fix is easy. Let me do a general alignement of ros-jazzy and ros-humble to propagate other fixes. |
General alignment done in 3bc909b . |
|
Let me guess, clang 19 created to many new warnings on projects that set Werror? |
Yes, and even some other errors not related to |
|
I remember now, it was a conflict because of https://github.com/traversaro/ros-jazzy/blob/a721b29c5986a0677f767da5b431f9bf4b382ba8/patch/dependencies.yaml#L103 |
|
Looks like we’re nearly done here :) |
|
We're running into RoboStack/ros-kilted#19 @traversaro - we should try and fix conda-forge/pygraphviz-feedstock#45 to resolve this once and for all :) |
|
See also 97c812d |
|
The pygraphviz PR has been merged. Is it easiest to do another full rebuild? Or just a few packages? |
|
Looks like it just works - hooray :) |
Closed
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #93 . Definitely not complete, but it can be a starting point, if anyone wants to iterate on the patches please ping me so I can give you access to the fork.
Fix #81 .
Fix #93 .
Fix #57 .