------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170628-214240 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] pypy (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * [2] ruby22 (with Rubygems)
Created attachment 479918 [details] emerge-info.txt
Created attachment 479920 [details] dev-ros:tf2_sensor_msgs-0.5.15:20170702-115932.log
Created attachment 479922 [details] emerge-history.txt
Created attachment 479924 [details] environment
Created attachment 479926 [details] etc.portage.tbz2
Created attachment 479928 [details] logs.tbz2
ERROR: Unable to contact my own server at [http://mr-fox:42367/]. This usually means that the network is not configured properly. A common cause is that the machine cannot ping itself. Please check for errors by running: ping mr-fox For more tips, please see http://www.ros.org/wiki/ROS/NetworkSetup please check that; ros requires that $(hostname) resolves to local ip (usually 127.0.0.1)
Hhn, my IN- firewall is very restrictive, (just 3 IN ports are open). I set the IN policy to ACCEPT, furthermore added both to the ipv4 and ipv6 firewall the host ip addresses respectively - but the package still fails. Within the chroot image I can ping : # host mr-fox mr-fox.zwiebeltoralf.de has address 5.9.158.75 mr-fox.zwiebeltoralf.de has IPv6 address 2a01:4f8:190:514a::2 # ping -c3 mr-fox PING mr-fox.zwiebeltoralf.de (5.9.158.75) 56(84) bytes of data. 64 bytes from tor-relay.zwiebeltoralf.de (5.9.158.75): icmp_seq=1 ttl=64 time=0.025 ms 64 bytes from tor-relay.zwiebeltoralf.de (5.9.158.75): icmp_seq=2 ttl=64 time=0.036 ms 64 bytes from tor-relay.zwiebeltoralf.de (5.9.158.75): icmp_seq=3 ttl=64 time=0.033 ms # ping6 -c3 mr-fox PING mr-fox(tor-relay.zwiebeltoralf.de) 56 data bytes 64 bytes from tor-relay.zwiebeltoralf.de: icmp_seq=1 ttl=64 time=0.061 ms 64 bytes from tor-relay.zwiebeltoralf.de: icmp_seq=2 ttl=64 time=0.069 ms 64 bytes from tor-relay.zwiebeltoralf.de: icmp_seq=3 ttl=64 time=0.057 ms
*** Bug 623700 has been marked as a duplicate of this bug. ***
