robotpkg/wip/sot-hrprtc-hrp2 bulk build results
Log for sot-hrprtc-hrp2-1.2.2 on CentOS-7-x86_64: bulk.log (Back)
=> Checking for clear installation
===> Installing bootstrap dependencies for sot-hrprtc-hrp2-1.2.2
=> 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 sot-hrprtc-hrp2-1.2.2
=> 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 sot-hrprtc-hrp2-1.2.2
===> Installing full dependencies for sot-hrprtc-hrp2-1.2.2
=> Dependency digest-20080510 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-2.5.7.tgz
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/dynamic-graph-bridge-2.0.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
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 dynamic-graph-bridge-msgs-0.2.0 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/hrp2-14-1.9.3.tgz
=> Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/hrp2-14-description-1.0.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
=> Installing /opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/CentOS-7-x86_64/All/hrp2-bringup-1.0.6.tgz
=> Dependency hrp2-computer-monitor-1.0.2 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/hrp2-dynamics-1.5.3.tgz
=> Dependency hrp2-machine-1.0.2 already installed
=> Dependency jrl-mal-1.19.6r1~jrl-mathtools already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/openrtm-aist-1.1.1r1.tgz
=> Dependency py27-dynamic-graph-2.5.6r1 already installed
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/py27-sot-application-1.0.0r3.tgz
=> Dependency py27-sot-tools-1.0.1 already installed
=> Dependency ros-comm-1.11.20 already installed
=> Dependency ros-message-runtime-0.4.12 already installed
=> Dependency ros-realtime-tools-1.9.2 already installed
=> Dependency ros-std-msgs-0.5.9 already installed
=> Dependency sot-core-2.9.10 already installed
=> Dependency sot-dynamic-2.9.2 already installed
ERROR: Required robotpkg package sot-dyninv>=2.0.0: BROKEN
=> Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/CentOS-7-x86_64/All/sot-pattern-generator-2.9.1.tgz
=> Dependency tnftp-20130505~ssl already installed
===> Deinstalling for sot-hrprtc-hrp2
Removed digest-20080510
Removing dependency jrl-mal-1.19.6r1~jrl-mathtools
Removing dependency
Removing dependency py27-dynamic-graph-2.5.6r1
Removing dependency sot-core-2.9.10
Removing dependency sot-pattern-generator-2.9.1
Removing dependency py27-sot-tools-1.0.1
Removing dependency sot-dynamic-2.9.2
Removing dependency py27-sot-application-1.0.0r3
Removing dependency dynamic-graph-bridge-2.0.9
Removed dynamic-graph-2.5.7
Removed hrp2-14-1.9.3
Removing dependency robot-capsule-urdf-1.0.1r2
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-std-msgs-0.5.9
Removing dependency ros-xacro-1.9.2
Removing dependency urdfdom-0.3.0r2
Removing dependency
Removing dependency hrp2-bringup-1.0.6
Removed hrp2-14-description-1.0.5
Removing dependency jrl-dynamics-1.25.0r1
Removing dependency
Removed hrp2-dynamics-1.5.3
Removing dependency ace-6.4.6
Removing dependency
Removed openrtm-aist-1.1.1r1
Removed tnftp-20130505~ssl