Full Rebuild (Sync) of May 2026: bump ros2-distro-mutex to 0.15.0 and build_number to 19#212
Open
ayushgnv wants to merge 26 commits into
Open
Full Rebuild (Sync) of May 2026: bump ros2-distro-mutex to 0.15.0 and build_number to 19#212ayushgnv wants to merge 26 commits into
ayushgnv wants to merge 26 commits into
Conversation
Author
|
@Tobias-Fischer @Traver could you take a look to see if it makes sense? |
asio 1.36 removed the asio::io_service typedef and asio::io_service::work, which broke ros-jazzy-io-context 1.2.0. Migrate to asio::io_context, asio::executor_work_guard, and the free-function asio::post().
Member
Thanks, sorry I missed the comment due to a typo in the reference. Let me check! |
traversaro
reviewed
May 11, 2026
Comment on lines
-168
to
-172
| apriltag: | ||
| generate_dummy_package_with_run_deps: | ||
| build_number: 17 | ||
| dep_name: apriltag | ||
| max_pin: 'x.x.x' |
Member
There was a problem hiding this comment.
Can you keep the apriltag generate_dummy_package_with_run_deps, just removing the build_number override?
Author
There was a problem hiding this comment.
Thanks for the pointer. Added this back in
traversaro
reviewed
May 11, 2026
traversaro
reviewed
May 11, 2026
| - gazebo 11.* | ||
| - libprotobuf 6.31.1.* | ||
| - libprotobuf 6.33.* | ||
| - vtk 9.5.2.* |
Member
There was a problem hiding this comment.
I guess we need to raise this to vtk 9.6.1 or similar.
Member
There was a problem hiding this comment.
I was wrong, this results in the error:
4
│ │ │ ├─ eigen *, which can be installed with any of the following
│ options:
│ │ │ │ ├─ eigen 5.0.1
│ │ │ │ └─ eigen 3.2.8 | 3.2.8 | 3.2.8 | 3.3.1 | 3.3.3 | 3.3.5 | 3.3.5 |
│ 3.3.5 | 3.3.5 | 3.3.6 | 3.3.6 | 3.3.7 | 3.3.7 | 3.3.7 | 3.3.8 | 3.3.8 |
│ 3.3.9 | 3.3.9 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0
│ │ │ └─ eigen-abi >=3.4.0.100,<3.4.0.101.0a0, which cannot be installed
│ because there are no viable options:
│ │ │ └─ eigen-abi 3.4.0.100 | 3.4.0.100 would constrain
│ │ │ └─ eigen >=3.4.0,<3.4.1.0a0, which conflicts with any
│ installable versions previously reported
│ │ └─ ros-jazzy-pcl-conversions 2.6.2 | 2.6.2 | 2.6.2 | 2.6.2 | 2.6.2 |
│ 2.6.2 | 2.6.2 | 2.6.2 | 2.6.2 is excluded because due to strict channel
│ priority not using this option from: 'https://conda.anaconda.org/
│ robostack-jazzy/'
│ └─ ros2-distro-mutex 0.15.* jazzy_* cannot be installed because there are
│ no viable options:
│ └─ ros2-distro-mutex 0.15.0 would constrain
│ ├─ vtk 9.6.1.*, which conflicts with any installable versions
│ previously reported
│ ├─ pcl 1.15.1.*, which conflicts with any installable versions
│ previously reported
│ └─ libboost 1.88.*, which conflicts with any installable versions
│ previously reported
The problem is that we are bound to eigen 3.4.0 until conda-forge/pinocchio-feedstock#163 is fixed, that constraints us to an old build of pcl, that requires vtk 9.6.0, so I guess for now we need to pin vtk to 9.6.0, not 9.6.1 .
Member
|
Can you please change the title of the PR to "Full Rebuild (Sync) of May 2026: bump ros2-distro-mutex to 0.15.0 and build_number to 19" for clarity? Thanks! |
Member
|
Builds fails with: I guess we may use a patch like https://github.com/esteve/ros-humble/blob/humble-full-rebuild-20260511/patch/ros-humble-ouster-ros.patch . |
Co-authored-by: Silvio Traversaro <silvio@traversaro.it>
ayushgnv
changed the title
Changed the IGNORE_CACHE_AND_DO_FULL_REBUILD setting to 'true' to force a full rebuild. Removed outdated cache cleanup comments.
Updated override versions for urdfdom and pinocchio packages to ensure compatibility with conda-forge.
Changed IGNORE_CACHE_AND_DO_FULL_REBUILD to 'false' to prevent full rebuild.
Member
|
For the robot state publisher problem, I guess we can forwardport the change https://github.com/RoboStack/ros-humble/pull/407/changes . |
Contributor
In general I think we have to get better in syncing the different distributions somehow .. I had one attempt with GitHub Agents |
Author
|
@Tobias-Fischer I noticed you merged main into this branch recently. Wondering if there were any related fixes in main branch that were merged in? I have some additional patches I added after bf1f5a5 pipeline ran with partial failures. Should I still push my changes or wait for this latest merge commit to go through the pipeline? Summary of my changes (pending):
|
Contributor
|
You can push them now. |
osx test with ros-humble#407
- foxglove-bridge.win.patch: drop /WX on MSVC (C4456/C4267
fail
foxglove_bridge_component; --compile-no-warning-as-error
doesn't
override per-target /WX).
- robot-state-publisher test: broaden osx carve-out, add
ROS_LOCALHOST_ONLY=1, pull in rcl-interfaces + rclpy.
Contributor
we’ve had this before, I can’t remember what the solution is .. |
osx clang bumped 18→19 in 463d6f7; pin in patch/dependencies.yaml became unsatisfiable, breaking osx-arm64 env resolution.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Addressing Issue 211: #211