robotpkg/graphics/rcpdf bulk build results
Log for rcpdf-0.2r2 on CentOS-7-x86_64: bulk.log (Back)
=> Checking for clear installation
===> Installing bootstrap dependencies for rcpdf-0.2r2
=> 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 rcpdf-0.2r2
=> 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 patch>=2.0: patch-2.7.1 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 rcpdf-0.2r2
===> Installing full dependencies for rcpdf-0.2r2
=> Dependency digest-20080510 already installed
=> Required robotpkg package rcpdf-interface>=0.2: N/A
=> 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
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
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 tnftp-20130505~ssl already installed
=> Dependency urdfdom-0.3.0r2 already installed
=> Dependency urdfdom-headers-0.3.0 already installed
===> Deinstalling for rcpdf
Removed digest-20080510
Removing dependency collada-dom-2.3.1r2
Removing dependency orocos-kdl-1.3.0
Removing dependency ros-angles-1.9.9
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-console-bridge-0.4.2
Removing dependency ros-geometric-shapes-0.4.1
Removing dependency ros-geometry-1.11.3r1
Removing dependency ros-pluginlib-1.10.1
Removing dependency ros-resource-retriever-1.11.5
Removing dependency ros-ros-1.11.4
Removing dependency ros-srdfdom-0.2.7
Removing dependency urdfdom-0.3.0r2
Removing dependency urdfdom-headers-0.3.0
Removing dependency
Removed ros-robot-model-1.11.5
Removed tnftp-20130505~ssl