Source: ros-rviz Version: 1.11.10+dfsg-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160728 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 > '/«BUILDDIR»/ros-rviz-1.11.10+dfsg/obj-x86_64-linux-gnu' > [ 98%] Running SIP generator for rviz_sip Python bindings... > cd /«BUILDDIR»/ros-rviz-1.11.10+dfsg/src/python_bindings/sip && > /usr/bin/python /usr/share/python_qt_binding/cmake/sip_configure.py > /«BUILDDIR»/ros-rviz-1.11.10+dfsg/obj-x86_64-linux-gnu/devel/bin/sip/rviz_sip > rviz.sip > /«BUILDDIR»/ros-rviz-1.11.10+dfsg/obj-x86_64-linux-gnu/devel/lib/python2.7/dist-packages/rviz > "/«BUILDDIR»/ros-rviz-1.11.10+dfsg/src /usr/include /usr/include/opencv > /usr/include/xmlrpcpp /usr/include/eigen3 /usr/include/python2.7" "rviz" > "/«BUILDDIR»/ros-rviz-1.11.10+dfsg/obj-x86_64-linux-gnu/devel/lib/x86_64-linux-gnu" > > "-Wl,-rpath,\"/«BUILDDIR»/ros-rviz-1.11.10+dfsg/obj-x86_64-linux-gnu/devel/lib/x86_64-linux-gnu\"" > qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake': No such file > or directory > Traceback (most recent call last): > File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 47, in > <module> > config = Configuration() > File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 16, in > __init__ > ['qmake', '-query'], env=env, universal_newlines=True) > File "/usr/lib/python2.7/subprocess.py", line 574, in check_output > raise CalledProcessError(retcode, cmd, output=output) > subprocess.CalledProcessError: Command '['qmake', '-query']' returned > non-zero exit status 1 > make[3]: *** [devel/bin/sip/rviz_sip/Makefile] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/28/ros-rviz_1.11.10+dfsg-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.
