Closed vinnnyr closed 2 years ago
Ok nevermind, I realize what happened. That message is present in the ros2
branch, but not the galactic
branch, and therefore I guess it won't be released for galactic
.
well maybe I can re-open this issue just to ask -- can it be cherry-picked onto the galactic
branch / released for the next galactic sync, or does it break some sort of rule?
Actually, the file does exist in galactic
, but it's not in the CMakeLists.txt message files list. Or at least, it wasn't, until I just pushed it a few minutes ago. Now visible here.
Please let me know if this works for you and we can create another release.
And just FYI, my policy (which I believe is standard for most ROS message packages) is to not make any changes to existing messages on a given distro (because this will change md5sums), but adding new messages is no problem.
yes this works for me now -- thank you!
new release created (3.0.2), PR here: https://github.com/ros/rosdistro/pull/32488
Hi! It seems this issue is present also in foxy.
I'm not able to use BoundingBox2DArray and BoundingBox3DArray. Thank you.
Just made a PR https://github.com/ros-perception/vision_msgs/pull/73
In Galactic,
BoundingBox3DArray
does not show up as a generated message for python, for neither the apt binary, nor when building from source:This occurs in a fresh docker container too, and could be replicated there: https://asciinema.org/a/vtbiRQtrlSXIvhR25SM7cMLS7
If you look at the
__init__.py
for the message (for binary located here:/opt/ros/galactic/lib/python3.8/site-packages/vision_msgs/msg/__init__.py
) you can see that the message is not generated. I am not sure why that may be yet.