Full Rebuild (Sync) of December 2025: bump ros2-distro-mutex to 0.13.0 and build_number to 14 #135
+187
−29
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
Updated numpy and libzenohc versions, added libcap.
Fixes compilation issues with Boost 1.87 by updating Point.h to remove deprecated rescaling code.
Removed build_number entry for next full rebuild.
Signed-off-by: wep21 <[email protected]>
This was referenced Nov 29, 2025
Closed
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Contributor
|
need to wait this migration? |
Member
Author
|
For reference, the error seems: but it does not seems related to the spdlog 1.16 migration. |
Member
Author
Actually, indeed pcl and vtk have not migrated to spdlog 1.16, see conda-forge/vtk-feedstock#413 (I am trying to unblock this in conda-forge/vtk-feedstock#417). How was it possible for PCL to be installed here? |
Member
Author
Ok, I think by demangling the problematic symbol, the issue is more clear: rclpy expects spdlog with fmt 12, but somehow fmt 11 is installed instead, resulting in error. However, this should be handled at the level of runexports of fmt in the |
Member
Author
Ok, this is indeed the output of: So |
Member
Author
|
Ok, now it fails at package installation time as expected. This should unblocked by conda-forge/vtk-feedstock#417 and conda-forge/vtk-feedstock#413 . |
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
Contributor
|
Contributor
|
@traversaro Do you understand what dependency is wrong? |
Member
Author
|
Which platform fail with that? Linux fails with another error: |
Member
Author
This seems related to ros-navigation/navigation2#4583, we need to understand if SuiteSparse is actually needed or not, and if earlier version of ceres provided the suitesparse component. |
Member
Author
My bad, that is ros-navigation/navigation2#2753, it is probably a conda-forge ceres regression. |
Member
Author
Related to conda-forge/ceres-solver-feedstock#50 and ceres-solver/ceres-solver#1026 . |
Member
Author
|
Member
Author
Found, it is the |
Member
Author
|
But those should be done by conda-forge/gz-common-feedstock#73 . |
Contributor
|
That’s because we’re still on v4 here: https://github.com/traversaro/ros-jazzy/blob/542548109083b613027283ecbd50a34784a14231/robostack.yaml#L168 |
Member
Author
Who is pulling that rosdep key? I would expect Jazzy to be using Gazebo Harmonic, see https://gazebosim.org/docs/latest/getstarted/ . |
Contributor
|
You are right, that was a false alarm – I've restarted the builds, let's see |
Updated vinca dependency to a specific commit.
Member
Author
Fixed in conda-forge/ceres-solver-feedstock#53 . |
Member
Author
|
I think I reproduced the |
Member
Author
Ok, this boils down to p11_kit being pinned to 0.24.* in https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/7f362791cb07c9683613f5cb77446ff3d6b21250/recipe/conda_build_config.yaml#L850, and libffi 3.5 rebuild missing for 0.24.* (there is conda-forge/p11-kit-feedstock#32, but it is for 0.25.*). I tried to unblock this in conda-forge/conda-forge-pinning-feedstock#5091 . |
Member
Author
Member
Author
|
There is a different error here: |
Member
Author
|
The issue is now conda-forge/gz-transport-feedstock#84 . |
Member
Author
|
Member
Author
|
New failure: if we remove the |
Contributor
Is removing the xml pin something we can actually do safely? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.