robotpkg/wip/dynamic-graph-bridge-v3 bulk build results

Log for dynamic-graph-bridge-v3-3.1.0 on CentOS-7-x86_64: bulk.log (Back)

=> Checking for clear installation ===> Installing bootstrap dependencies for dynamic-graph-bridge-v3-3.1.0 => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/digest-20080510.tgz => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/tnftp-20130505~ssl.tgz ===> Checking bootstrap dependencies for dynamic-graph-bridge-v3-3.1.0 => Required robotpkg package digest>=20080510: digest-20080510 found => Required robotpkg package tnftp>=20091122: tnftp-20130505~ssl found => Required system package gzip: gzip-1.5 found => Required system package pax and tar archivers: pax found => Required system package pkg_install>=20110805.9: pkg_install-20110805.9 found ===> Done bootstrap-depends for dynamic-graph-bridge-v3-3.1.0 ===> Installing full dependencies for dynamic-graph-bridge-v3-3.1.0 => Dependency digest-20080510 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-bridge-msgs-0.2.0.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-v3-3.1.0.tgz => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/hpp-fcl-0.6.0.tgz => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/pinocchio-1.2.9r1.tgz => Dependency ros-catkin-0.6.9r2 already installed => Dependency ros-comm-1.11.20 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-common-msgs-1.11.4.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-geometry-1.11.3r1.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-geometry2-0.5.15 already installed => Dependency ros-message-runtime-0.4.12 already installed => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-realtime-tools-1.9.2.tgz To use ros, the following environment variables must contain those values: ROS_MASTER_URI http://localhost:11311 ROS_PACKAGE_PATH /opt/openrobots/share PYTHONPATH /opt/openrobots/lib/python2.7/site-packages PATH /opt/openrobots/bin As an alternative to the above configuration, commands can be executed by using the `env.sh' wrapper. For instance, roscore can be started like so: /opt/openrobots/etc/ros/env.sh roscore In Bourne shell scripts, the following file can be sourced instead: /opt/openrobots/etc/ros/setup.sh => Dependency ros-roscpp-core-0.5.4r1 already installed => Dependency ros-rospack-2.2.4 already installed => Dependency ros-std-msgs-0.5.9 already installed => Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/sot-core-v3-3.2.0.tgz => Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/sot-dynamic-pinocchio-v3-3.1.8.tgz => Dependency tnftp-20130505~ssl already installed => Dependency urdfdom-0.3.0r2 already installed ===> Checking build options for dynamic-graph-bridge-v3-3.1.0 => Building with no option. ===> Checking alternatives for dynamic-graph-bridge-v3-3.1.0 => Use the GNU C++ compiler: c++-compiler provided by g++>=3 => Use the GNU C compiler: c-compiler provided by gcc>=3 => Use python-2.7: python>=2.5<3.7 provided by python27>=2.7<2.8 => Use ros indigo: ros>=groovy ros>=hydro ros>=hydro provided by ros-indigo ===> Checking dependencies for dynamic-graph-bridge-v3-3.1.0 => Required system package bullet>=2.75: bullet-2.82 found => Required system package cmake>=2.8.3: cmake-2.8.12.2 found => Required system package eigen3>=3.0.0: eigen3-3.2.5 found => Required system package g++>=3: g++-4.8.5 found => Required system package gcc>=3: gcc-4.8.5 found => Required system package googletest: googletest found => Required system package libstdc++: libstdc++ found => Required system package pkg-config>=0.22: pkg-config-0.27.1 found => Required system package py27-empy>=3: py27-empy-3.3.2 found => Required system package py27-nose>=0.10: py27-nose-1.3.7 found => Required system package python27>=2.7<2.8: python27-2.7.5 found => Required system package tinyxml>=2: tinyxml-2.6.2 found => Required robotpkg package dynamic-graph-bridge-msgs>=0.2.0: dynamic-graph-bridge-msgs-0.2.0 found => Required robotpkg package dynamic-graph-v3>=3.0.0: dynamic-graph-v3-3.1.0 found => Required robotpkg package hpp-fcl>=0.5: hpp-fcl-0.6.0 found => Required robotpkg package pinocchio>=1.2.8: pinocchio-1.2.9r1 found => Required robotpkg package ros-catkin>=0.6<0.7: ros-catkin-0.6.9r2 found => Required robotpkg package ros-comm>=1.11<1.12: ros-comm-1.11.20 found => Required robotpkg package ros-common-msgs>=1.11<1.12: ros-common-msgs-1.11.4 found => Required robotpkg package ros-geometry>=1.11<1.12: ros-geometry-1.11.3r1 found => Required robotpkg package ros-geometry2>=0.5<0.6: ros-geometry2-0.5.15 found => Required robotpkg package ros-message-runtime>=0.4<0.5: ros-message-runtime-0.4.12 found => Required robotpkg package ros-realtime-tools>=1.8.2: ros-realtime-tools-1.9.2 found => Required robotpkg package ros-roscpp-core>=0.5<0.6: ros-roscpp-core-0.5.4r1 found => Required robotpkg package ros-rospack>=2.2<2.3: ros-rospack-2.2.4 found => Required robotpkg package ros-std-msgs>=0.5: ros-std-msgs-0.5.9 found => Required robotpkg package sot-core-v3>=3.0.0: sot-core-v3-3.2.0 found => Required robotpkg package sot-dynamic-pinocchio-v3>=3.1.1: sot-dynamic-pinocchio-v3-3.1.8 found => Required robotpkg package urdfdom>=0.2.8<1: urdfdom-0.3.0r2 found WARNING: Using urdfdom-0.3.0 in /opt/openrobots WARNING: The following packages may interfere with the build because they WARNING: are located in paths used by other dependencies: WARNING: urdfdom-0.3.0 in /usr ===> Done depends for dynamic-graph-bridge-v3-3.1.0 ===> Extracting for dynamic-graph-bridge-v3-3.1.0 => SHA1 checksums OK => RMD160 checksums OK ===> Configuring for dynamic-graph-bridge-v3-3.1.0 CMake Warning at cmake/python.cmake:42 (MESSAGE): CMake versions older than 3.2 do not properly find Python. Custom macros are used to find it. Call Stack (most recent call first): CMakeLists.txt:28 (include) libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib libpath/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib cmake_install_bindir is bin -- Doxygen rendering: using MathJax backend ===> Building for dynamic-graph-bridge-v3-3.1.0 In file included from /local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/src/ros_joint_state.cpp:8:0: /opt/openrobots/include/sot-dynamic-pinocchio/dynamic-pinocchio.h:30:20: fatal error: Python.h: No such file or directory #include ^ compilation terminated. make[2]: *** [CMakeFiles/ros_joint_state.dir/src/ros_joint_state.cpp.o] Error 1 make[1]: *** [CMakeFiles/ros_joint_state.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [all] Error 2 An unexpected error occured. The last 10 log lines are shown below. | /usr/bin/cmake -E cmake_progress_report /local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/CMakeFiles 16 17 18 | [ 70%] Built target geometric_simu | Linking CXX shared library lib/ros_publish.so | /usr/bin/cmake -E cmake_link_script CMakeFiles/ros_publish.dir/link.txt --verbose=1 | /usr/bin/g++ -fPIC -pedantic -Wno-long-long -Wall -Wextra -Wcast-align -Wcast-qual -Wformat -Wwrite-strings -Wconversion -pipe -O3 -DNDEBUG -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -ldynamic-graph -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -lsot-core -ldynamic-graph -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -shared -Wl,-soname,ros_publish.so -o lib/ros_publish.so CMakeFiles/ros_publish.dir/src/ros_publish.cpp.o -L/opt/openrobots/lib -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -ldynamic-graph -Wl,-rpath,/opt/openrobots/lib -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -lsot-core -ldynamic-graph -Wl,-rpath,/opt/openrobots/lib -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -Wl,-rpath,/opt/openrobots/lib lib/libros_bridge.so lib/libros_bridge.so -lsot-core -Wl,-rpath,/opt/openrobots/lib -L/opt/openrobots/lib -Wl,-rpath,/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/lib:/opt/openrobots/lib | make[2]: Leaving directory `/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0' | /usr/bin/cmake -E cmake_progress_report /local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0/CMakeFiles 22 => Marking dynamic-graph-bridge-v3-3.1.0 as broken | [ 70%] Built target ros_publish | make[1]: Leaving directory `/local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/dynamic_graph_bridge-3.1.0' | make: *** [all] Error 2 For details or bug reports, check the complete log file in: /local/robotpkg/var/tmp/robotpkg/wip/dynamic-graph-bridge-v3/work/build.log make[3]: *** [do-build] Error 1 make[2]: *** [pkg-check-installed] Error 2 ERROR: make: *** [package] Error 2 ===> Deinstalling for dynamic-graph-bridge-v3 Removed digest-20080510 Removing dependency ros-catkin-0.6.9r2 Removing dependency ros-comm-1.11.20 Removing dependency ros-genlisp-0.4.14 Removing dependency ros-genmsg-0.5.3 Removing dependency ros-message-generation-0.2.10 Removing dependency ros-std-msgs-0.5.9 Removing dependency Removed dynamic-graph-bridge-msgs-0.2.0 Removing dependency py27-dynamic-graph-v3-3.1.0 Removing dependency sot-core-v3-3.2.0 Removing dependency sot-tools-v3-2.1.0 Removing dependency py27-sot-core-v3-3.2.0 Removing dependency py27-sot-tools-v3-2.1.0 Removing dependency sot-dynamic-pinocchio-v3-3.1.8 Removed dynamic-graph-v3-3.1.0 Removing dependency py27-catkin-pkg-0.2.4 Removing dependency Removing dependency ros-orocos-kdl-1.3.0 Removing dependency ros-angles-1.9.9 Removing dependency ros-rospack-2.2.4 Removing dependency ros-roscpp-core-0.5.4r1 Removing dependency ros-genmsg-0.5.3 Removing dependency ros-ros-1.11.4 Removing dependency ros-genpy-0.5.3 Removing dependency ros-message-runtime-0.4.12 Removing dependency ros-genlisp-0.4.14 Removing dependency ros-gencpp-0.5.2 Removing dependency ros-message-generation-0.2.10 Removing dependency ros-std-msgs-0.5.9 Removing dependency ros-common-msgs-1.11.4 Removing dependency ros-comm-msgs-1.11.2r1 Removing dependency ros-comm-1.11.20 Removing dependency ros-realtime-tools-1.9.2 Removing dependency ros-actionlib-1.11.9 Removing dependency ros-geometry2-0.5.15 Removing dependency ros-geometry-1.11.3r1 Removed ros-catkin-0.6.9r2 Removed tnftp-20130505~ssl