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

Trying to make a debian package

asked 2014-11-17 19:52:29 -0500


I'm working with Rviz/MoveIt! to plan my robots movement. However I want/have to make the use of Rviz/MoveIt! easier for my colleagues and less experienced users. I am aiming at editing the ros-hydro-moveit-ros-visualization package. I already found the source code of the package and I have also found what I wanted to change. However now I'm stuck. To install the changed source code I first have to convert it to a debian package. I tried several methods and how-to's that I've found on google, but none of them give me the desired result. Or I get errors when trying to compile/convert or the build of the .deb file I made doesn't share any similarities to the original .deb file I got from . For example my .deb doesn't install in the /opt/ros/hydro folder. Also my .deb file doesn't have any library files etc. In short the .deb files I managed to make only have the original source code files in it. How do I make a correct .deb file that installs in the correct folder, has the correct library files etc?

edit retag flag offensive close merge delete


A small correction to my question. With less experienced users I mean end-users of the robot. The current Motion Planning plug-in, that is located in the moveit-ros-visualization package, is great for experiment and develop environments, but not for simple end-users.

firebird40 gravatar image firebird40  ( 2014-11-17 21:27:32 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-11-17 20:25:10 -0500

ahendrix gravatar image

updated 2014-11-18 01:22:25 -0500

You really shouldn't try to edit existing debs. You'll confuse anyone who's expecting to have the upstream version, and your changes may be overwritten by an update if the package maintainer releases a new version.

There are a few things that you can try:

  • If you have bugfixes or new features in the upstream package, submit them as a pull request. They'll benefit the rest of the community, in addition to your colleagues.
  • If you're just adding configuration files or launch scripts that don't have to be part of the upstream package, consider creating your own package. You can then distribute or release your package as you see fit.


Once you have your own ROS package that you would like to release (build debs), you can create a release repository with bloom and either release that package to the ROS build farm through bloom, or build debs locally:

edit flag offensive delete link more


I'm not trying to make it a part of the upstream package. As you said I can consider creating my own package. That is what I am doing. But to test it all and everything I first have to know how I can convert the source code to a .deb file so I can install it and try it.

firebird40 gravatar image firebird40  ( 2014-11-17 21:32:34 -0500 )edit

Question Tools

1 follower


Asked: 2014-11-17 19:52:29 -0500

Seen: 167 times

Last updated: Nov 18 '14