Source: msxpertsuite Version: 5.7.3-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64
Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > cd /<<PKGBUILDDIR>>/debian/build/libmass && /usr/bin/c++ -DQT_CORE_LIB > -DQT_GUI_LIB -DQT_SCRIPT_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB > -DQT_XML_LIB -I/<<PKGBUILDDIR>>/debian/build/libmass > -I/<<PKGBUILDDIR>>/libmass > -I/<<PKGBUILDDIR>>/debian/build/libmass/mass_autogen/include > -I/<<PKGBUILDDIR>>/debian/build -I/<<PKGBUILDDIR>> -I/usr/include/pwiz > -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem > /usr/include/x86_64-linux-gnu/qt5/QtScript -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g > -Wno-unknown-pragmas -fPIC -Wall -g -O0 -fopenmp -fPIC -std=c++11 -o > CMakeFiles/mass.dir/MassSpectrum.cpp.o -c > /<<PKGBUILDDIR>>/libmass/MassSpectrum.cpp > /<<PKGBUILDDIR>>/libmass/MassSpectrum.cpp:50:10: fatal error: > pwiz/data/msdata/MSDataFile.hpp: No such file or directory > #include <pwiz/data/msdata/MSDataFile.hpp> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make[4]: *** [libmass/CMakeFiles/mass.dir/build.make:196: > libmass/CMakeFiles/mass.dir/MassSpectrum.cpp.o] Error 1 The full build log is available from: http://aws-logs.debian.net/2019/03/15/msxpertsuite_5.7.3-1_testing.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.
