robotpkg/wip/talos-pal-gazebo-plugins bulk build results
Log for talos-pal-gazebo-plugins-1.1.6 on CentOS-7-x86_64: bulk.log (Back)
=> Checking for clear installation
===> Installing bootstrap dependencies for talos-pal-gazebo-plugins-1.1.6
=> 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 talos-pal-gazebo-plugins-1.1.6
=> 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.7: pkg_install-20110805.7 found
===> Done bootstrap-depends for talos-pal-gazebo-plugins-1.1.6
===> Installing full dependencies for talos-pal-gazebo-plugins-1.1.6
=> Dependency digest-20080510 already installed
ERROR: Required robotpkg package pal-msgs>=0.11.3: BROKEN
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-actionlib-1.11.9.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
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-catkin-0.6.9r2 already installed
=> Dependency ros-comm-1.11.20 already installed
=> Dependency ros-common-msgs-1.11.4 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-control-toolbox-1.13.2r1.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
=> Dependency ros-genmsg-0.5.3 already installed
=> 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
=> Dependency ros-message-generation-0.2.10 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-pluginlib-1.10.1.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
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/ros-robot-model-1.11.5.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
=> Dependency ros-ros-1.11.4 already installed
=> Dependency ros-std-msgs-0.5.9 already installed
=> Dependency tnftp-20130505~ssl already installed
===> Deinstalling for talos-pal-gazebo-plugins
Removed digest-20080510
Removing dependency ros-catkin-0.6.9r2
Removing dependency ros-comm-1.11.20
Removing dependency ros-common-msgs-1.11.4
Removing dependency ros-genmsg-0.5.3
Removing dependency ros-message-generation-0.2.10
Removing dependency ros-message-runtime-0.4.12
Removing dependency ros-std-msgs-0.5.9
Removing dependency
Removing dependency ros-geometry2-0.5.15
Removing dependency ros-geometry-1.11.3r1
Removing dependency ros-robot-model-1.11.5
Removed ros-actionlib-1.11.9
Removing dependency py27-catkin-pkg-0.2.4
Removing dependency
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-comm-msgs-1.11.2r1
Removing dependency ros-comm-1.11.20
Removing dependency ros-realtime-tools-1.9.2
Removing dependency ros-dynamic-reconfigure-1.5.37
Removing dependency ros-control-toolbox-1.13.2r1
Removed ros-catkin-0.6.9r2
Removed tnftp-20130505~ssl