Ask Your Question

How do I remove a duplicate package?

asked 2016-01-24 18:48:50 -0500

nadnav gravatar image

updated 2016-01-24 21:44:35 -0500

I installed the velodyne driver package using

sudo apt-get install ros-indigo-velodyne

But then I realised that the release version didn't support what I needed.
The current master branch however does.

I cloned the repository to my catkin workspace, made it then installed it.
However, when I try to launch it with

roslaunch velodyne_pointcloud VLP16_points.launch

I get the error

[VLP16_points.launch] is neither a launch file in package [velodyne_pointcloud] nor is [velodyne_pointcloud] a launch file name

I think it's referencing the old package.
How do I remove the old package that I installed using sudo apt-get install?

Edit: Ran source command and outputted ROS_PACKAGE_PATH variable

$ source ~/catkin_ws/devel/setup.bash   

rospack find output

nathan:~/catkin_ws$ rospack find velodyne_pointcloud

catkin_make and catkin_install output

nathan:~/catkin_ws$ catkin_make
Base path: /home/nathan/catkin_ws
Source space: /home/nathan/catkin_ws/src
Build space: /home/nathan/catkin_ws/build
Devel space: /home/nathan/catkin_ws/devel
Install space: /home/nathan/catkin_ws/install
#### Running command: "make cmake_check_build_system" in "/home/nathan/catkin_ws/build"
#### Running command: "make -j4 -l4" in "/home/nathan/catkin_ws/build"
[  0%] Built target std_msgs_generate_messages_cpp
[  0%] Built target std_msgs_generate_messages_lisp
[  0%] Built target std_msgs_generate_messages_py
[  0%] [  0%] Built target _velodyne_msgs_generate_messages_check_deps_VelodyneScan
Built target _velodyne_msgs_generate_messages_check_deps_VelodynePacket
[  0%] Built target _beginner_tutorials_generate_messages_check_deps_Num
[  0%] [  0%] Built target _beginner_tutorials_generate_messages_check_deps_AddToInts
Built target diagnostic_msgs_generate_messages_lisp
[  0%] Built target tf2_msgs_generate_messages_py
[  0%] [  0%] [  0%] Built target tf2_msgs_generate_messages_lisp
Built target roscpp_generate_messages_cpp
[  0%] Built target roscpp_generate_messages_py
Built target roscpp_generate_messages_lisp
[  0%] Built target tf2_msgs_generate_messages_cpp
[  0%] [  0%] Built target rosgraph_msgs_generate_messages_cpp
Built target rosgraph_msgs_generate_messages_lisp
[  0%] Built target rosgraph_msgs_generate_messages_py
[  0%] Built target diagnostic_msgs_generate_messages_cpp
[  0%] Built target diagnostic_msgs_generate_messages_py
[  0%] [  0%] Built target bond_generate_messages_lisp
Built target sensor_msgs_generate_messages_py
[  0%] Built target sensor_msgs_generate_messages_lisp
[  0%] Built target tf_generate_messages_lisp
[  0%] [  0%] [  0%] Built target geometry_msgs_generate_messages_py
Built target tf_generate_messages_cpp
Built target nodelet_generate_messages_lisp
[  0%] Built target bond_generate_messages_py
[  0%] [  0%] Built target nodelet_generate_messages_cpp
Built target nodelet_generate_messages_py
[  0%] Built target sensor_msgs_generate_messages_cpp
[  0%] Built target geometry_msgs_generate_messages_lisp
[  0%] Built target geometry_msgs_generate_messages_cpp
[  0%] Built target tf_generate_messages_py
[  0%] [  0%] Built target actionlib_generate_messages_lisp
Built target bond_generate_messages_cpp
[  0%] [  0%] Built target actionlib_generate_messages_py
Built target actionlib_generate_messages_cpp
[  0%] [  0%] [  0%] Built target actionlib_msgs_generate_messages_py
Built target actionlib_msgs_generate_messages_lisp
Built target actionlib_msgs_generate_messages_cpp
[  8%] Built target velodyne_msgs_generate_messages_py
[ 11%] Built target velodyne_pointcloud_gencfg
[ 17%] Built target velodyne_msgs_generate_messages_lisp
[ 22%] Built target velodyne_msgs_generate_messages_cpp
[ 28%] Built target beginner_tutorials_generate_messages_cpp
[ 34%] Built target beginner_tutorials_generate_messages_lisp
[ 34%] Built target velodyne_msgs_generate_messages
[ 45%] Built target beginner_tutorials_generate_messages_py
[ 45%] Built target beginner_tutorials_generate_messages
[ 48%] Built target velodyne_input
[ 54%] Built target driver_nodelet
[ 60%] Built target velodyne_node
[ 71%] [ 71%] Built target ringcolors_node
Built target velodyne_rawdata
[ 77%] Built target ringcolors_nodelet
[ 94%] [ 94%] [ 94%] Built target cloud_node
Built target transform_node
[100%] Built target transform_nodelet
Built target cloud_nodelet
nathan:~/catkin_ws$ catkin_make install
Base path: /home/nathan/catkin_ws
Source space: /home/nathan/catkin_ws/src
Build space: /home/nathan/catkin_ws/build
Devel space: /home/nathan/catkin_ws/devel
Install space: /home/nathan/catkin_ws/install
#### Running command: "make cmake_check_build_system" in "/home/nathan/catkin_ws/build"
#### Running command: "make install -j4 -l4" in "/home/nathan/catkin_ws/build"
[  0%] [  0%] Built target std_msgs_generate_messages_cpp
Built target std_msgs_generate_messages_lisp
[  0%] Built target std_msgs_generate_messages_py ...
edit retag flag offensive close merge delete

3 Answers

Sort by ยป oldest newest most voted

answered 2016-01-25 08:55:29 -0500

joq gravatar image

If your catkin workspace had been constructed correctly, the driver built from source should overlay the binary package you had installed previously. At this point, you'd probably have to re-create the workspace from scratch, being very careful to source only the ROS distro while doing it.

edit flag offensive delete link more

answered 2016-01-24 19:26:21 -0500

130s gravatar image

updated 2016-01-25 04:28:50 -0500

Did you sourced the setup.*sh file in your Catkin workspace (cf. tutorial)?

If you think you did, we may not have enough info. Edit your question to add echo $ROS_PACKAGE_PATH command output.

UPDATE) If you are using install space, then source ~/catkin_ws/installl/setup.bash.

edit flag offensive delete link more


Yes, I've sourced the setup.bash file. I've also added the source command to my bashrc so it should be running it automatically. However, I just ran the source command again just to be 100% confident. I've edited my original question with the ROS_PACKAGE_PATH variable.

nadnav gravatar image nadnav  ( 2016-01-24 19:41:05 -0500 )edit

How about:

rospack find velodyne_pointcloud

You might want to paste all output when you did "make". Make sure the package was built without outstanding errors.

130s gravatar image 130s  ( 2016-01-24 20:56:21 -0500 )edit

How do I remove the old package that I installed using sudo apt-get install?

Despite that's not even a ROS question, you can remove by apt-get purge %PKGNAME%.

130s gravatar image 130s  ( 2016-01-24 20:56:32 -0500 )edit

I've updated the original post with the rospack find and catkin_make output.

nadnav gravatar image nadnav  ( 2016-01-24 22:33:04 -0500 )edit

answered 2019-08-22 05:50:25 -0500

ermanas gravatar image

I've experienced such a thing like this. I installed rviz from the source and also I clone the rviz repository from the git to my catkin workspace source folder. And I make catkin_make. After that I simply delete the rviz from the workspace but after that the catkin_make didn't clean the rviz completely from the workspace. When I make catkin_make for packages who has rviz dependency, catkin_make gave me error. Infact I had the rviz that I installed from the source(with apt-get install) on my computer. the problem is this catkin_make was searching my catkin workspace.

As a solution, instead of creating a new catkin workspace from scratch, I searched my workspace and I deleted the rviz folders. And when I do catkin_make after that, It worked.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-01-24 18:48:50 -0500

Seen: 6,831 times

Last updated: Aug 22 '19