Bug#880277: cantor: FTBFS: dh_install: missing files, aborting
Source: cantor
Version: 4:16.08.3-1
Severity: serious
Tags: buster sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20171030 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[2]: Entering directory '/<<PKGBUILDDIR>>'
> dh_install
> dh_install: Cannot find (any matches for) "etc/xdg/cantor_python3.knsrc" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-python3 missing files: etc/xdg/cantor_python3.knsrc
> dh_install: Cannot find (any matches for) "usr/bin/cantor_python3server" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-python3 missing files: usr/bin/cantor_python3server
> dh_install: Cannot find (any matches for) "usr/lib/*/qt5/plugins/cantor/backends/cantor_python3backend.so" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-python3 missing files: usr/lib/*/qt5/plugins/cantor/backends/cantor_python3backend.so
> dh_install: Cannot find (any matches for) "usr/share/config.kcfg/python3backend.kcfg" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-python3 missing files: usr/share/config.kcfg/python3backend.kcfg
> dh_install: Cannot find (any matches for) "usr/lib/*/qt5/plugins/cantor/backends/cantor_luabackend.so" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-lua missing files: usr/lib/*/qt5/plugins/cantor/backends/cantor_luabackend.so
> dh_install: Cannot find (any matches for) "usr/share/config.kcfg/luabackend.kcfg" (tried in ., debian/tmp)
>
> dh_install: cantor-backend-lua missing files: usr/share/config.kcfg/luabackend.kcfg
> dh_install: missing files, aborting
> debian/rules:12: recipe for target 'override_dh_install' failed
> make[2]: *** [override_dh_install] Error 25
The full build log is available from:
http://aws-logs.debian.net/2017/10/30/cantor_16.08.3-1_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.
Reply to: