Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 #22

wep21 · 2025-02-05T09:39:31Z

update after latest sync

traversaro · 2025-02-05T09:56:35Z

@wep21 the full rebuild can take some time, do you have a package in particular you want to update?

wep21 · 2025-02-05T10:08:13Z

@traversaro I'm sorry, but I want to just try to update rosdistro, there is no particular package that I want to use urgently.

traversaro · 2025-02-05T10:26:14Z

@traversaro I'm sorry, but I want to just try to update rosdistro, there is no particular package that I want to use urgently.

Ok! Do you have any particular timeline for getting a rebuild? I have a few improvements that I would like to do in the next rebuild (use conda-forge-pinnings, devendor), but I am not sure when I will be able toto do it. In the past we seldomly did rebuilds, but as long as the build works (and we do not have problem of space on robostack-jazzy channel) we could even consider doing more frequenct rebuilds, but I guess it is something we need to be aligned with @Tobias-Fischer and @wolfv .

traversaro · 2025-02-05T10:26:43Z

Anyhow, I guess there is quite a job in patch cleanup to do now, so if you are willing to do it that would be great!

Tobias-Fischer · 2025-02-05T11:16:28Z

I'd be very happy to do more frequent rebuilds - it's just a capacity issue on the (current) maintainer team side I guess, if someone has the time to fix up the problems that arise and we just need to provide minimal input, that'd be amazing :)

traversaro · 2025-02-05T11:26:09Z

I'd be very happy to do more frequent rebuilds - it's just a capacity issue on the (current) maintainer team side I guess, if someone has the time to fix up the problems that arise and we just need to provide minimal input, that'd be amazing :)

Great! At this point then there is no problem for me either. If I am able to add some improvements in this rebuild that is great, otherwise I will do it in the next rebuild.

traversaro · 2025-02-05T13:04:01Z

By the way, I guess migrating https://github.com/RoboStack/ros-jazzy/blob/main/check_patches_clean_apply.py to rattler-build could be helpful to quickly go through failing patches.

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

traversaro · 2025-02-06T09:57:05Z

@wep21 for a full rebuild, you need several steps (copy&pasting from discord):

No, basically to update the packages we need to do a so-called "full rebuild", i.e. roughly speaking (as far as I know):

Refresh the rosdistro_snapshot.yaml by running vinca snapshot (this is the only step that actually queries rosdistro, directly from the repo and indipendently from sync)

Refresh the conda_build_config.yaml file to reflect the current status of conda-forge plus migrations that are basically finished even if not updated in conda-forge-pinnings

Bump the build_number in vinca_*.yaml files to a version higher then any existing build number (now also considering the overriden build numbers in pkg_additional_info.yaml)

Bump the minor number of the mutex_package in vinca_*.yaml

Remove any build_number override in pkg_additional_info.yaml

At this point, we can run pixi run build and check if there was any failure. For example, during the last full rebuild I upstreamed also several patches, so I imagine that we would need to drop several patches, and if some new version of a package introduced problems we need to patch them

I guess so that you need to also bump the minor version of the mutex packages.

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

traversaro · 2025-02-06T11:47:11Z

vinca_win.yaml

@@ -6,7 +6,7 @@ conda_index:
  - packages-ignore.yaml

 # Reminder for next full rebuild, the next build number should be 4
-build_number: 1
+build_number: 4

 mutex_package: ros2-distro-mutex 0.6.* jazzy_*


I guess you need to update the mutex version also here.

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 · 2025-02-06T12:20:20Z

Error: 
  × Failed to resolve dependencies: Cannot solve the request because of: ros-
  │ jazzy-ros-workspace * cannot be installed because there are no viable
  │ options:
  │ └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
  │    └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were found.
  │ 
  ╰─▶ Cannot solve the request because of: ros-jazzy-ros-workspace * cannot be
      installed because there are no viable options:
      └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
         └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were
      found.

How can I fix this error? Do I still miss something?

wep21 · 2025-02-06T13:24:44Z

On my local PC, libcap dependencies cannot be satisfied when running pixi run build.

Error: 
  × Failed to resolve dependencies: Cannot solve the request because of: The following packages are incompatible
  │ ├─ ros-jazzy-controller-manager * cannot be installed because there are no viable options:
  │ │  ├─ ros-jazzy-controller-manager 4.25.0 would require
  │ │  │  └─ ros-jazzy-realtime-tools *, which cannot be installed because there are no viable options:
  │ │  │     ├─ ros-jazzy-realtime-tools 3.3.0 would require
  │ │  │     │  └─ libcap >=2.73,<2.74.0a0, which cannot be installed because there are no viable options:
  │ │  │     │     └─ libcap 2.73, which conflicts with the versions reported above.
  │ │  │     └─ ros-jazzy-realtime-tools 3.1.0 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
  │ │  └─ ros-jazzy-controller-manager 4.23.0 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
  │ └─ ros-jazzy-gz-sim-vendor * cannot be installed because there are no viable options:
  │    ├─ ros-jazzy-gz-sim-vendor 0.0.7 would require
  │    │  └─ ros-jazzy-gz-rendering-vendor *, which cannot be installed because there are no viable options:
  │    │     ├─ ros-jazzy-gz-rendering-vendor 0.0.5 would require
  │    │     │  └─ ros-jazzy-gz-ogre-next-vendor *, which cannot be installed because there are no viable options:
  │    │     │     ├─ ros-jazzy-gz-ogre-next-vendor 0.0.5 would require
  │    │     │     │  └─ sdl2 >=2.30.10,<3.0a0, which cannot be installed because there are no viable options:
  │    │     │     │     └─ sdl2 2.30.10 would require
  │    │     │     │        └─ pulseaudio-client >=17.0,<17.1.0a0, which cannot be installed because there are no viable options:
  │    │     │     │           └─ pulseaudio-client 17.0 would require
  │    │     │     │              └─ libsystemd0 >=255, which cannot be installed because there are no viable options:
  │    │     │     │                 ├─ libsystemd0 256.9 | 256.9 | 256.9 | 256.9 | 257.2 would require
  │    │     │     │                 │  └─ libcap >=2.71,<2.72.0a0, which cannot be installed because there are no viable options:
  │    │     │     │                 │     └─ libcap 2.71, which conflicts with the versions reported above.
  │    │     │     │                 └─ libsystemd0 255 | 255 | 256.5 | 256.6 | 256.7 | 256.7 would require
  │    │     │     │                    └─ libcap >=2.69,<2.70.0a0, which cannot be installed because there are no viable options:
  │    │     │     │                       └─ libcap 2.69, which conflicts with the versions reported above.
  │    │     │     └─ ros-jazzy-gz-ogre-next-vendor 0.0.5 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-
  │ jazzy/'
  │    │     └─ ros-jazzy-gz-rendering-vendor 0.0.5 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
  │    └─ ros-jazzy-gz-sim-vendor 0.0.6 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
  │ 
  ╰─▶ Cannot solve the request because of: The following packages are incompatible
      ├─ ros-jazzy-controller-manager * cannot be installed because there are no viable options:
      │  ├─ ros-jazzy-controller-manager 4.25.0 would require
      │  │  └─ ros-jazzy-realtime-tools *, which cannot be installed because there are no viable options:
      │  │     ├─ ros-jazzy-realtime-tools 3.3.0 would require
      │  │     │  └─ libcap >=2.73,<2.74.0a0, which cannot be installed because there are no viable options:
      │  │     │     └─ libcap 2.73, which conflicts with the versions reported above.
      │  │     └─ ros-jazzy-realtime-tools 3.1.0 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
      │  └─ ros-jazzy-controller-manager 4.23.0 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
      └─ ros-jazzy-gz-sim-vendor * cannot be installed because there are no viable options:
         ├─ ros-jazzy-gz-sim-vendor 0.0.7 would require
         │  └─ ros-jazzy-gz-rendering-vendor *, which cannot be installed because there are no viable options:
         │     ├─ ros-jazzy-gz-rendering-vendor 0.0.5 would require
         │     │  └─ ros-jazzy-gz-ogre-next-vendor *, which cannot be installed because there are no viable options:
         │     │     ├─ ros-jazzy-gz-ogre-next-vendor 0.0.5 would require
         │     │     │  └─ sdl2 >=2.30.10,<3.0a0, which cannot be installed because there are no viable options:
         │     │     │     └─ sdl2 2.30.10 would require
         │     │     │        └─ pulseaudio-client >=17.0,<17.1.0a0, which cannot be installed because there are no viable options:
         │     │     │           └─ pulseaudio-client 17.0 would require
         │     │     │              └─ libsystemd0 >=255, which cannot be installed because there are no viable options:
         │     │     │                 ├─ libsystemd0 256.9 | 256.9 | 256.9 | 256.9 | 257.2 would require
         │     │     │                 │  └─ libcap >=2.71,<2.72.0a0, which cannot be installed because there are no viable options:
         │     │     │                 │     └─ libcap 2.71, which conflicts with the versions reported above.
         │     │     │                 └─ libsystemd0 255 | 255 | 256.5 | 256.6 | 256.7 | 256.7 would require
         │     │     │                    └─ libcap >=2.69,<2.70.0a0, which cannot be installed because there are no viable options:
         │     │     │                       └─ libcap 2.69, which conflicts with the versions reported above.
         │     │     └─ ros-jazzy-gz-ogre-next-vendor 0.0.5 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-
      jazzy/'
         │     └─ ros-jazzy-gz-rendering-vendor 0.0.5 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'
         └─ ros-jazzy-gz-sim-vendor 0.0.6 is excluded because due to strict channel priority not using this option from: 'https://conda.anaconda.org/robostack-jazzy/'

traversaro · 2025-02-06T14:25:17Z

vinca_osx.yaml


-mutex_package: ros2-distro-mutex 0.6.* jazzy_*
+mutex_package: ros2-distro-mutex 0.7777777.* jazzy_*


is this a typo?

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

traversaro · 2025-02-06T15:33:55Z

Error: 
  × Failed to resolve dependencies: Cannot solve the request because of: ros-
  │ jazzy-ros-workspace * cannot be installed because there are no viable
  │ options:
  │ └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
  │    └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were found.
  │ 
  ╰─▶ Cannot solve the request because of: ros-jazzy-ros-workspace * cannot be
      installed because there are no viable options:
      └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
         └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were
      found.

How can I fix this error? Do I still miss something?

That is strange, it seems like ros-workspace recipe is not generated. Can you check if it is generated in the recipes directory?

traversaro · 2025-02-06T15:40:02Z

Error: 
  × Failed to resolve dependencies: Cannot solve the request because of: ros-
  │ jazzy-ros-workspace * cannot be installed because there are no viable
  │ options:
  │ └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
  │    └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were found.
  │ 
  ╰─▶ Cannot solve the request because of: ros-jazzy-ros-workspace * cannot be
      installed because there are no viable options:
      └─ ros-jazzy-ros-workspace 1.0.3 | 1.0.3 would require
         └─ ros2-distro-mutex 0.6.* jazzy_*, for which no candidates were
      found.

How can I fix this error? Do I still miss something?

That is strange, it seems like ros-workspace recipe is not generated. Can you check if it is generated in the recipes directory?

I think the problem is ros-workspace is still in pkg_additional_info.yaml . Can you check to follow all steps in #22 (comment), including the "Remove any build_number override in pkg_additional_info.yaml" ?

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 · 2025-02-11T14:01:45Z

pixi v0.41.2 introduces this error.

pixi install -e beta --frozen
  /home/runner/.pixi/bin/pixi install -e beta --frozen --manifest-path pixi.toml --color always
  Error: 
    × beta: error installing/updating PyPI dependencies
    ╰─▶ base path is not absolute:

traversaro · 2025-02-11T14:26:27Z

pixi v0.41.2 introduces this error.

pixi install -e beta --frozen
  /home/runner/.pixi/bin/pixi install -e beta --frozen --manifest-path pixi.toml --color always
  Error: 
    × beta: error installing/updating PyPI dependencies
    ╰─▶ base path is not absolute:

Can you open a issue in pixi or investigate if there is an issue already open? Thanks! fyi @wolfv @ruben-arts

wep21 · 2025-02-11T14:33:59Z

Can you open a issue in pixi or investigate if there is an issue already open? Thanks! fyi @wolfv @ruben-arts

prefix-dev/pixi#3111 will fix the issue.

traversaro · 2025-02-11T14:36:10Z

Can you open a issue in pixi or investigate if there is an issue already open? Thanks! fyi @wolfv @ruben-arts

prefix-dev/pixi#3111 will fix the issue.

Thanks!

ruben-arts · 2025-02-11T15:43:16Z

Sorry 😓

traversaro · 2025-02-11T15:51:05Z

Sorry 😓

Thanks for looking into the issue!

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 · 2025-02-12T09:31:43Z

@traversaro windows ci seems to also reach actions time limit.

traversaro · 2025-02-12T10:07:14Z

@traversaro windows ci seems to also reach actions time limit.

Great. I will run the rest of the build locally as I noticed some local failures, then we can merge.

traversaro · 2025-02-13T13:05:17Z

@wep21 I bumped a bit the pinned dependencies to align with the conda-forge pinnings, and to me the PR is ready to review. Can I modify the title to be a bit more descriptive?

wep21 · 2025-02-13T14:12:47Z

Can I modify the title to be a bit more descriptive?

@traversaro No problem!

wep21 · 2025-02-15T16:17:10Z

@traversaro The packages which are rebuilt seem to depend on ros2-distro-mutex 0.7.0, while ones which are not rebuilt seem to still depend on ros2-distro-mutex 0.6.0. How can I fix these conflicts?

~/workspace/ros2_pixi
❯ pixi add ros-jazzy-ur-client-library
✔ Added ros-jazzy-ur-client-library >=1.6.0,<2

~/workspace/ros2_pixi 15s
❯ pixi add ros-jazzy-desktop
Error: 
  × failed to solve the conda requirements of 'default' 'osx-arm64'
  ╰─▶ Cannot solve the request because of: The following packages are incompatible
      ├─ ros-jazzy-desktop * can be installed with any of the following options:
      │  └─ ros-jazzy-desktop 0.11.0 would require
      │     └─ ros2-distro-mutex >=0.6.0,<0.7.0a0, which can be installed with any of the following options:
      │        └─ ros2-distro-mutex 0.6.0
      └─ ros-jazzy-ur-client-library >=1.6.0,<2 cannot be installed because there are no viable options:
         └─ ros-jazzy-ur-client-library 1.6.0 | 1.6.0 would require
            └─ ros2-distro-mutex >=0.7.0,<0.8.0a0, which cannot be installed because there are no viable options:
               ├─ ros2-distro-mutex 0.7.0, which conflicts with the versions reported above.
               └─ ros2-distro-mutex 0.7.0, which conflicts with the versions reported above.

traversaro · 2025-02-15T16:58:18Z

The only way is to also rebuild missing packages for ros2-distro-mutex 0.7.0. Do you have any idea why ros-jazzy-ur-client-library was not rebuild?

wep21 · 2025-02-15T23:31:44Z

I guess ros-jazzy-ur-client-library was rebuilt because its version has changed from 1.5.0 to 1.6.0 while other packages whose version hasn't change wasn't rebuilt.

wep21 · 2025-02-15T23:39:46Z

pixi search says ros-jazzy-desktop depends on ros2-distro-mutex 0.7.0, but when adding as pixi deps, it fails.

❯ pixi search ros-jazzy-desktop
Using channels: robostack-jazzy, conda-forge

ros-jazzy-desktop-0.11.0-np126py311h8b30c37_4 (+ 1 build)
---------------------------------------------------------

Name                ros-jazzy-desktop  
Version             0.11.0
Build               np126py311h8b30c37_4
Size                22326              
License             BSD-3-Clause       
Subdir              osx-arm64          
File Name           ros-jazzy-desktop-0.11.0-np126py311h8b30c37_4.conda
URL                 https://conda.anaconda.org/robostack-jazzy/osx-arm64/ros-jazzy-desktop-0.11.0-np126py311h8b30c37_4.conda
MD5                 d819e10a27ad126af66b4b3e2497ae09
SHA256              9c4aa1f2c8a78225468e9c881fbf38ecc3d3f334a1fab1f6f19da382c0d5c093

Dependencies:
 - python
 - ros-jazzy-action-tutorials-cpp
 - ros-jazzy-action-tutorials-interfaces
 - ros-jazzy-action-tutorials-py
 - ros-jazzy-angles
 - ros-jazzy-composition
 - ros-jazzy-demo-nodes-cpp
 - ros-jazzy-demo-nodes-cpp-native
 - ros-jazzy-demo-nodes-py
 - ros-jazzy-depthimage-to-laserscan
 - ros-jazzy-dummy-map-server
 - ros-jazzy-dummy-robot-bringup
 - ros-jazzy-dummy-sensors
 - ros-jazzy-examples-rclcpp-minimal-action-client
 - ros-jazzy-examples-rclcpp-minimal-action-server
 - ros-jazzy-examples-rclcpp-minimal-client
 - ros-jazzy-examples-rclcpp-minimal-composition
 - ros-jazzy-examples-rclcpp-minimal-publisher
 - ros-jazzy-examples-rclcpp-minimal-service
 - ros-jazzy-examples-rclcpp-minimal-subscriber
 - ros-jazzy-examples-rclcpp-minimal-timer
 - ros-jazzy-examples-rclcpp-multithreaded-executor
 - ros-jazzy-examples-rclpy-executors
 - ros-jazzy-examples-rclpy-minimal-action-client
 - ros-jazzy-examples-rclpy-minimal-action-server
 - ros-jazzy-examples-rclpy-minimal-client
 - ros-jazzy-examples-rclpy-minimal-publisher
 - ros-jazzy-examples-rclpy-minimal-service
 - ros-jazzy-examples-rclpy-minimal-subscriber
 - ros-jazzy-image-tools
 - ros-jazzy-intra-process-demo
 - ros-jazzy-joy
 - ros-jazzy-lifecycle
 - ros-jazzy-logging-demo
 - ros-jazzy-pcl-conversions
 - ros-jazzy-pendulum-msgs
 - ros-jazzy-quality-of-service-demo-cpp
 - ros-jazzy-quality-of-service-demo-py
 - ros-jazzy-ros-base
 - ros-jazzy-ros-workspace
 - ros-jazzy-rqt-common-plugins
 - ros-jazzy-rviz-default-plugins
 - ros-jazzy-rviz2
 - ros-jazzy-teleop-twist-joy
 - ros-jazzy-teleop-twist-keyboard
 - ros-jazzy-topic-monitor
 - ros-jazzy-turtlesim
 - ros2-distro-mutex 0.7.* jazzy_*
 - libcxx >=18
 - __osx >=11.0
 - ros2-distro-mutex >=0.7.0,<0.8.0a0
 - numpy >=1.26.4,<2.0a0
 - python_abi 3.11.* *_cp311

❯ pixi add ros-jazzy-desktop
Error: 
  × failed to solve the conda requirements of 'default' 'osx-arm64'
  ╰─▶ Cannot solve the request because of: The following packages are incompatible
      ├─ ros-jazzy-desktop * can be installed with any of the following options:
      │  └─ ros-jazzy-desktop 0.11.0 would require
      │     └─ ros2-distro-mutex >=0.6.0,<0.7.0a0, which can be installed with any of the following options:
      │        └─ ros2-distro-mutex 0.6.0
      └─ ros-jazzy-ur-client-library >=1.6.0,<2 cannot be installed because there are no viable options:
         └─ ros-jazzy-ur-client-library 1.6.0 | 1.6.0 would require
            └─ ros2-distro-mutex >=0.7.0,<0.8.0a0, which cannot be installed because there are no viable options:
               ├─ ros2-distro-mutex 0.7.0, which conflicts with the versions reported above.
               └─ ros2-distro-mutex 0.7.0, which conflicts with the versions reported above.

wep21 marked this pull request as draft February 5, 2025 09:41

wep21 added 2 commits February 6, 2025 18:22

chore: update snapshot

c33268c

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

update build number in vinca yaml

35ae2b4

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 force-pushed the update-snapshot branch from a018bbf to 35ae2b4 Compare February 6, 2025 09:23

wep21 force-pushed the update-snapshot branch from c87d257 to bafffc0 Compare February 6, 2025 11:19

update hardware interface

5ebc9f1

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 force-pushed the update-snapshot branch from bafffc0 to 5ebc9f1 Compare February 6, 2025 11:25

traversaro reviewed Feb 6, 2025

View reviewed changes

bump distro mutex

55aec27

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

traversaro reviewed Feb 6, 2025

View reviewed changes

fix typo

feb0cff

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 added 6 commits February 7, 2025 01:17

remove pkg additional info

4d43fe5

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

remove gripper controllers patch

b81e9ad

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

add libcap into conda build config

270f1bd

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

update plotjuggler patch

b11063c

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

remove realtime tools win patch

84d7084

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

update realtime tools osx patch

20d4f97

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

wep21 force-pushed the update-snapshot branch from f66508c to 20d4f97 Compare February 7, 2025 07:06

wep21 and others added 4 commits February 11, 2025 12:16

remove smclib win patch

b373fad

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

Delete patch/ros-jazzy-forward-command-controller.win.patch

8937ffa

remove ackermann steering controller win patch

fafd0c9

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

pin pixi version

5917d56

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

Remvoe outdated positions-controllers win patch

16c5978

remove rviz common win patch

67032d6

Signed-off-by: wep21 <daisuke.nishimatsu1021@gmail.com>

traversaro added 3 commits February 12, 2025 17:04

Update with latest patches

11a66b4

Refresh conda_build_config.yaml

d6d5d3a

Bump libprotobuf

f68574e

traversaro closed this Feb 12, 2025

traversaro reopened this Feb 12, 2025

wep21 marked this pull request as ready for review February 13, 2025 14:15

traversaro changed the title ~~chore: update snapshot~~ Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 Feb 15, 2025

traversaro mentioned this pull request Feb 15, 2025

feat: add grid map into linux and osx #24

Merged

traversaro merged commit fe4749d into RoboStack:main Feb 15, 2025
3 of 10 checks passed

wep21 deleted the update-snapshot branch February 17, 2025 23:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 #22

Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 #22

wep21 commented Feb 5, 2025

traversaro commented Feb 5, 2025

wep21 commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 5, 2025

Tobias-Fischer commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 6, 2025

traversaro Feb 6, 2025

wep21 commented Feb 6, 2025

wep21 commented Feb 6, 2025 •

edited

Loading

traversaro Feb 6, 2025

wep21 Feb 6, 2025

traversaro commented Feb 6, 2025

traversaro commented Feb 6, 2025

wep21 commented Feb 11, 2025

traversaro commented Feb 11, 2025

wep21 commented Feb 11, 2025

traversaro commented Feb 11, 2025

ruben-arts commented Feb 11, 2025

traversaro commented Feb 11, 2025

wep21 commented Feb 12, 2025

traversaro commented Feb 12, 2025

traversaro commented Feb 13, 2025

wep21 commented Feb 13, 2025 •

edited

Loading

wep21 commented Feb 15, 2025

traversaro commented Feb 15, 2025

wep21 commented Feb 15, 2025

wep21 commented Feb 15, 2025 •

edited

Loading


		mutex_package: ros2-distro-mutex 0.6.* jazzy_*
		mutex_package: ros2-distro-mutex 0.7777777.* jazzy_*

Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 #22

Full Rebuild February 2024: bump ros2-distro-mutex to 0.7.0 and build_number to 4 #22

Conversation

wep21 commented Feb 5, 2025

traversaro commented Feb 5, 2025

wep21 commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 5, 2025

Tobias-Fischer commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 5, 2025

traversaro commented Feb 6, 2025

traversaro Feb 6, 2025

Choose a reason for hiding this comment

wep21 commented Feb 6, 2025

wep21 commented Feb 6, 2025 • edited Loading

traversaro Feb 6, 2025

Choose a reason for hiding this comment

wep21 Feb 6, 2025

Choose a reason for hiding this comment

traversaro commented Feb 6, 2025

traversaro commented Feb 6, 2025

wep21 commented Feb 11, 2025

traversaro commented Feb 11, 2025

wep21 commented Feb 11, 2025

traversaro commented Feb 11, 2025

ruben-arts commented Feb 11, 2025

traversaro commented Feb 11, 2025

wep21 commented Feb 12, 2025

traversaro commented Feb 12, 2025

traversaro commented Feb 13, 2025

wep21 commented Feb 13, 2025 • edited Loading

wep21 commented Feb 15, 2025

traversaro commented Feb 15, 2025

wep21 commented Feb 15, 2025

wep21 commented Feb 15, 2025 • edited Loading

wep21 commented Feb 6, 2025 •

edited

Loading

wep21 commented Feb 13, 2025 •

edited

Loading

wep21 commented Feb 15, 2025 •

edited

Loading