Source: ros-ros-comm
Version: 1.12.6-2
Severity: serious
Tags: buster sid
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64


During a rebuild of all packages in sid, your package failed to build on

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/build'
> cd /<<PKGBUILDDIR>>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
> /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/tools/topic_tools /<<PKGBUILDDIR>>/build 
> /<<PKGBUILDDIR>>/build/tools/topic_tools 
> /<<PKGBUILDDIR>>/build/tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/DependInfo.cmake
>  --color=
> [  9%] Generating Lisp code from roscpp/Logger.msg
> cd /<<PKGBUILDDIR>>/build/clients/roscpp && 
> ../../catkin_generated/ /usr/bin/python 
> /usr/lib/genlisp/ /<<PKGBUILDDIR>>/clients/roscpp/msg/Logger.msg 
> -Iroscpp:/<<PKGBUILDDIR>>/clients/roscpp/msg -p roscpp -o 
> /<<PKGBUILDDIR>>/build/devel/share/common-lisp/ros/roscpp/msg
> Traceback (most recent call last):
>   File "/usr/lib/genpy/", line 44, in <module>
>     import genpy.generator
>   File "/usr/lib/python2.7/dist-packages/genpy/", line 34, in 
> <module>
>     Scanning dependencies of target topic_tools_generate_messages_py
> from . message import Message, SerializationError, DeserializationError, 
> MessageException, struct_I
>   File "/usr/lib/python2.7/dist-packages/genpy/", line 44, in 
> <module>
>     import yaml
> ImportError: No module named yaml
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
> make -f 
> tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/build.make 
> tools/topic_tools/CMakeFiles/topic_tools_generate_messages_py.dir/build
> clients/roscpp/CMakeFiles/roscpp_generate_messages_py.dir/build.make:69: 
> recipe for target 'devel/lib/python2.7/dist-packages/roscpp/msg/' 
> failed
> make[3]: *** [devel/lib/python2.7/dist-packages/roscpp/msg/] Error 1

The full build log is available from:

A list of current common problems and possible solutions is available at . 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.

debian-science-maintainers mailing list

Reply via email to