ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

My package added to shadow-fixed repository with bloom is installed into a wrong path

asked 2018-11-08 06:48:26 -0500

MoriKen254 gravatar image


  • OS: Ubuntu 16.04
  • ROS distro: Kinetic
  • bloom version: 0.6.7
  • catkin_pkg version: 0.4.9
  • rosdep version: 0.12.2
  • rosdistro version: 0.6.9
  • vcstools version: 0.1.40

What I'm working on

I've just added my created package timed_roslaunch into shadow-fixed repository according to bloom turorial.

Recently merged rosdistro/kinetic/distribution.yamlrelated to timed_roslaunch is here.

I firstly tested sudo apt install ros-kinetic-timed-roslaunch after switching repository from ros to ros-shadow-fixed by referring to ShadowRepository Wiki Page and the install command was successfully completed.

What's wrong

However, the package files were installed into directly under / not opt/ros/kinetic/

For example, launch files in gazebo_ros are installed as the following directory configuration.

  • /
    • opt/
      • ros/
        • kinetic/
          • share/
            • gazebo_ros/
              • launch/

On the other hand, in case of timed_roslaunch, launch files are installed as follows.

  • /
    • launch/

Also, I directly download and checked deb package named ros-kinetic-timed-roslaunch_0.1.1-3xenial-20181107-003648-0800_amd64.deb from ros-shadow-fixed repository to find the launch directory is already set ot just under root /.

This causes any ros commands such as roscd, roslaunch and so on cannot find timed_roslaunch even after source /opt/ros/kinetic/setup.bash

I want to change the install directory from / to opt/ros/kinetic/ same as gazebo_ros.

Do I have to change anything when I use bloom? Does anyone know how can it be fixed?


edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-11-08 09:22:43 -0500

Dirk Thomas gravatar image

That sounds like your CMake is installing files to the wrong location. Looking into your repository it seems you have short tried to fix the problem in this commit::

But since then you haven't released a new version yet (the commit is one after the 0.1.1 tag). Therefore I would suggest to create a release 0.1.2 and run bloom for that one. The new Debian package might already look better.

edit flag offensive delete link more


Thank you so much. I didn't realize my fixing CMakeFile wasn't applied to 0.1.1. I released 0.1.2 n will let you know if it succeeds. BTW I don't get yet why copying dir fails like before the fix

MoriKen254 gravatar image MoriKen254  ( 2018-11-08 11:31:00 -0500 )edit

Thank you! any problems mentioned here have been fixed!

MoriKen254 gravatar image MoriKen254  ( 2018-11-09 09:12:37 -0500 )edit

Question Tools

1 follower


Asked: 2018-11-08 06:48:26 -0500

Seen: 436 times

Last updated: Nov 08 '18