Source: ufc Version: 2.0.5-3 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for `preinstall'. > make[2]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "Release" > -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/ufc.h > -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/include/swig/ufc.i > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc/_ufc.so > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc/ufc.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc/__init__.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/build.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/integrals.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/function.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/form.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/finite_element.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/dofmap.py > -- Installing: > /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/ufc_utils/__init__.py > -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/ufc/UFCConfig.cmake > -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/share/ufc/UFCConfigVersion.cmake > -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/pkgconfig/ufc-1.pc > make[1]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' > touch debian/stamp-makefile-install > Adding cdbs dependencies to debian/ufc.substvars > dh_installdirs -pufc > Adding cdbs dependencies to debian/ufc-doc.substvars > dh_installdirs -pufc-doc > dh_installdocs -pufc ./README ./TODO ./AUTHORS README AUTHORS TODO > dh_installexamples -pufc > dh_installman -pufc > dh_installinfo -pufc > dh_installmenu -pufc > dh_installcron -pufc > dh_installinit -pufc > dh_installdebconf -pufc > dh_installemacsen -pufc > dh_installcatalogs -pufc > dh_installpam -pufc > dh_installlogrotate -pufc > dh_installlogcheck -pufc > dh_installchangelogs -pufc ./ChangeLog > dh_installudev -pufc > dh_lintian -pufc > dh_bugfiles -pufc > dh_install -pufc > dh_link -pufc > dh_installmime -pufc > dh_installgsettings -pufc > dh_installdocs -pufc-doc ./README ./TODO ./AUTHORS README AUTHORS TODO > dh_installexamples -pufc-doc > dh_installman -pufc-doc > dh_installinfo -pufc-doc > dh_installmenu -pufc-doc > dh_installcron -pufc-doc > dh_installinit -pufc-doc > dh_installdebconf -pufc-doc > dh_installemacsen -pufc-doc > dh_installcatalogs -pufc-doc > dh_installpam -pufc-doc > dh_installlogrotate -pufc-doc > dh_installlogcheck -pufc-doc > dh_installchangelogs -pufc-doc ./ChangeLog > dh_installudev -pufc-doc > dh_lintian -pufc-doc > dh_bugfiles -pufc-doc > dh_install -pufc-doc > dh_link -pufc-doc > dh_installmime -pufc-doc > dh_installgsettings -pufc-doc > dh_strip -pufc > dh_compress -pufc > dh_fixperms -pufc > dh_makeshlibs -pufc > dh_strip -pufc-doc > dh_compress -pufc-doc > dh_fixperms -pufc-doc > dh_makeshlibs -pufc-doc > dh_installdeb -pufc > dh_perl -pufc > dh_shlibdeps -pufc > dh_installdeb -pufc-doc > dh_perl -pufc-doc > dh_shlibdeps -pufc-doc > dh_gencontrol -pufc > dh_md5sums -pufc > dh_builddeb -pufc > dpkg-deb: building package `ufc' in `../ufc_2.0.5-3_all.deb'. > dh_gencontrol -pufc-doc > dh_md5sums -pufc-doc > dh_builddeb -pufc-doc > dpkg-deb: building package `ufc-doc' in `../ufc-doc_2.0.5-3_all.deb'. > Adding cdbs dependencies to debian/python-ufc.substvars > dh_installdirs -ppython-ufc > cd obj-x86_64-linux-gnu && rm CMakeCache.txt && \ > cmake -D PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python2.7 \ > -D PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython2.7.so \ > -D PYTHON_INCLUDE_DIR:PATH=/usr/include/python2.7 \ > -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_C_COMPILER:FILEPATH="cc" > -DCMAKE_CXX_COMPILER:FILEPATH="g++" -DCMAKE_C_FLAGS="-g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall > -D_FORTIFY_SOURCE=2" -DCMAKE_CXX_FLAGS="-g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall > -D_FORTIFY_SOURCE=2" -DCMAKE_SKIP_RPATH=ON -DCMAKE_VERBOSE_MAKEFILE=ON -D > SWIG_EXECUTABLE:FILEPATH=/usr/bin/swig2.0 .. > SWIG_MODULE_LOCATION /«PKGBUILDDIR»/obj-x86_64-linux-gnu/_ufc.so > CMake Error: The following variables are used in this project, but they are > set to NOTFOUND. > Please set them or make sure they are set and tested correctly in the CMake > files: > PYTHON_INCLUDE_DIR2 (ADVANCED) > used as include directory in directory /«PKGBUILDDIR» > > -- Configuring incomplete, errors occurred! > You have changed variables that require your cache to be deleted. > Configure will be re-run and you may have to reset some variables. > The following variables have changed: > CMAKE_C_COMPILER= cc > CMAKE_CXX_COMPILER= g++ > > -- Generating done > CMake Warning: > Manually-specified variables were not used by the project: > > CMAKE_C_FLAGS > > > -- Build files have been written to: /«PKGBUILDDIR»/obj-x86_64-linux-gnu > make: *** [install-stamp-python2.7] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/ufc_2.0.5-3_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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
