Source: ros-bond-core Version: 1.7.18-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170805 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu' > [ 9%] Generating Lisp code from bond/Status.msg > [ 18%] Generating C++ code from bond/Status.msg > [ 27%] Generating Python from MSG bond/Constants > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python > /usr/lib/genlisp/gen_lisp.py /<<PKGBUILDDIR>>/bond/msg/Status.msg > -Ibond:/<<PKGBUILDDIR>>/bond/msg -Istd_msgs:/usr/share/std_msgs/cmake/../msg > -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/bond/msg > [ 36%] Generating Lisp code from bond/Constants.msg > [ 45%] Generating Python from MSG bond/Status > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py > /<<PKGBUILDDIR>>/bond/msg/Status.msg -Ibond:/<<PKGBUILDDIR>>/bond/msg > -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/include/bond -e > /usr/share/gencpp/cmake/.. > [ 54%] Generating C++ code from bond/Constants.msg > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py > /<<PKGBUILDDIR>>/bond/msg/Constants.msg -Ibond:/<<PKGBUILDDIR>>/bond/msg > -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python > /usr/lib/genlisp/gen_lisp.py /<<PKGBUILDDIR>>/bond/msg/Constants.msg > -Ibond:/<<PKGBUILDDIR>>/bond/msg -Istd_msgs:/usr/share/std_msgs/cmake/../msg > -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/share/common-lisp/ros/bond/msg > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py > /<<PKGBUILDDIR>>/bond/msg/Status.msg -Ibond:/<<PKGBUILDDIR>>/bond/msg > -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg > cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/bond && > ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/gencpp/gen_cpp.py > /<<PKGBUILDDIR>>/bond/msg/Constants.msg -Ibond:/<<PKGBUILDDIR>>/bond/msg > -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o > /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/devel/include/bond -e > /usr/share/gencpp/cmake/.. > Traceback (most recent call last): > File "/usr/lib/genpy/genmsg_py.py", line 44, in <module> > import genpy.generator > File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in > <module> > from . message import Message, SerializationError, DeserializationError, > MessageException, struct_I > File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in > <module> > import yaml > ImportError: No module named yaml > Traceback (most recent call last): > File "/usr/lib/genpy/genmsg_py.py", line 44, in <module> > import genpy.generator > File "/usr/lib/python2.7/dist-packages/genpy/__init__.py", line 34, in > <module> > from . message import Message, SerializationError, DeserializationError, > MessageException, struct_I > File "/usr/lib/python2.7/dist-packages/genpy/message.py", line 44, in > <module> > import yaml > ImportError: No module named yaml > bond/CMakeFiles/bond_generate_messages_py.dir/build.make:66: recipe for > target 'devel/lib/python2.7/dist-packages/bond/msg/_Constants.py' failed > make[3]: *** [devel/lib/python2.7/dist-packages/bond/msg/_Constants.py] Error > 1 The full build log is available from: http://aws-logs.debian.net/2017/08/05/ros-bond-core_1.7.18-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
