Why velodyne_description isn't released for arm64?

asked 2022-05-24 09:09:34 -0500

Kenji Miyake
307 ●3 ●21 ●17

Seeing these URLs, it seems not released.

amd64:

$ docker run --rm -it ros:humble
$ apt update >/dev/null 2>&1 && apt-cache policy ros-humble-velodyne-description
ros-humble-velodyne-description:
  Installed: (none)
  Candidate: 2.0.2-3jammy.20220520.032909
  Version table:
     2.0.2-3jammy.20220520.032909 500
        500 http://packages.ros.org/ros2/ubuntu jammy/main amd64 Packages

arm64:

$ docker run --rm -it arm64v8/ros:humble
$ apt update >/dev/null 2>&1 && apt-cache policy ros-humble-velodyne-description
N: Unable to locate package ros-humble-velodyne-description

Does anyone know the reason? And will this be resolved after a while?

answered 2022-05-24 09:33:11 -0500

Joe28965

1124 ●3 ●73 ●28

updated 2022-05-24 10:12:52 -0500

Interestingly enough, I helped them port it to ROS2, since I needed it myself at the time. It is part of velodyne_simulator.

The reason why it wasn't released might simply be that it hadn't crossed their mind. velodyne_simulator has been released for about a year, so I don't think it'll be resolved if you don't raise the issue.

I think this forum isn't the ~~correct~~ best place to ask though. I suggest creating an issue in the repo that I linked above.

edit flag offensive delete link

Comments

Thank you for your comment! But seeing it's released to Foxy and Galactic, I guess there is some release issue. So I believe ROS Answers or ROS Discourse is the right place to ask this question.

Kenji Miyake ( 2022-05-24 09:50:50 -0500 )edit

It's not released to Rolling as well.

$ docker run --rm -it arm64v8/ros:rolling
$ apt update >/dev/null 2>&1 && apt-cache policy ros-rolling-velodyne-description
N: Unable to locate package ros-rolling-velodyne-description

Kenji Miyake ( 2022-05-24 09:52:48 -0500 )edit

The reason I said it's probably best to ask in the repo is because I don't know if the developers of said package look here a lot. Even if they do, the question might still get buried under other questions.

If you create an issue on their repo, I'm convinced they'll be able to respond easier/faster.

However, I should say that my sentence might have been better had I not used the word 'correct' but instead 'best'. Since I do believe an creating an issue is the best chance for you to get a useful answer.

As to it being released for both Foxy and Galactic, that might have happened at the same time, they both seem to link to the branch foxy-devel. From what I remember, the person who accepted the merge requests and made a Foxy branch wasn't really using ROS 2 ...(more)