------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170625-200344 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems) java-config: The following VMs are available for generation-2:
Created attachment 479804 [details] emerge-info.txt
Created attachment 479806 [details] dev-ros:robot_pose_ekf-1.14.0:20170702-073428.log
Created attachment 479808 [details] emerge-history.txt
Created attachment 479810 [details] environment
Created attachment 479812 [details] etc.portage.tbz2
Created attachment 479814 [details] logs.tbz2
commit 7f354a0c3f96b77f28ea303007b2f7b7d5d53824 Author: Alexis Ballier <aballier@gentoo.org> Date: Thu Jul 6 23:22:18 2017 +0200 ros-catkin.eclass: Use only a single python implementation for all ROS packages. Use only python 2.7: that is the version supported by OSRF. Multi-python the way we did it was not working well, it ended up loading python libs from different interpreters causing weird errors. Add ros-catkin_python_setup function. should have fixed it