Second Full Rebuild (Sync) of November 2025: bump ros2-distro-mutex to 0.13.0 and build_number to 14#126
Second Full Rebuild (Sync) of November 2025: bump ros2-distro-mutex to 0.13.0 and build_number to 14#126Tobias-Fischer wants to merge 14 commits intomainfrom
Conversation
|
Note that I don't have the capacity to push this more. @wep21 @gftabor @traversaro feel free to take over / build on top of this if you're interested :) |
|
Linux failure: |
|
The libcap problem is probably due to conda-forge/conda-forge-pinning-feedstock#7934 . Something I think would help mitigate these kind of problems would be to also capture as a snapshot https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml , and only add our own pinning as an override of the snapshotted conda_build_config.yaml . |
Updated numpy and libzenohc versions, added libcap.
|
Now the build is blocked by conda-forge/pyside2-feedstock#273 that is blocked by conda-forge/qt-webengine-feedstock#76 . |
|
There seems to be an actual boost 1.88-related failure in lanelet2_core: |
Probably we just need to backport fzi-forschungszentrum-informatik/Lanelet2#399 . |
Fixes compilation issues with Boost 1.87 by updating Point.h to remove deprecated rescaling code.
|
Nice, the |
|
I tried to take a look but couldn't follow. The current error is a mismatch between versions of some dependency right? Does that mean a specific pinned version of something needs to be updated or just that a dependency needs to be rebuilt? |
|
blocked by conda-forge/zenoh-cpp-feedstock#36 |
|
@wep21 - why is conda-forge/zenoh-cpp-feedstock#36 a blocker? Can we work around? |
|
I've tried to build with zenoh 1.6.1, but it causes build error with rmw_zenoh. I guess the latest rmw_zenoh requires zenoh 1.6.2. |
This was now merged in conda-forge/zenoh-cpp-feedstock#37 . |
Removed build_number entry for next full rebuild.
No description provided.