Source: ktp-accounts-kcm Version: 15.08.3-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160707 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 --fail-missing > dh_install: Cannot find (any matches for) > "usr/share/accounts/providers/*.provider" (tried in "." and "debian/tmp") > dh_install: kde-config-telepathy-accounts missing files: > usr/share/accounts/providers/*.provider > dh_install: Cannot find (any matches for) > "usr/share/accounts/services/*.service" (tried in "." and "debian/tmp") > dh_install: kde-config-telepathy-accounts missing files: > usr/share/accounts/services/*.service > dh_install: usr/share/accounts/services/kde/ktp-haze-yahoo-im.service exists > in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-haze-aim-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-sipe-haze-im.service exists > in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-sipe-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-generic-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-haze-gadugadu-im.service > exists in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-jabber-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-haze-sametime-im.service > exists in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-morse-telegram-im.service > exists in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-kde-talk-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/google-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/services/kde/ktp-haze-icq-im.service exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-sipe.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-haze-icq.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-haze-sametime.provider > exists in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-haze-aim.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-morse-telegram.provider > exists in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-gadugadu.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-jabber.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-haze-yahoo.provider exists > in debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-sipe-haze.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-generic.provider exists in > debian/tmp but is not installed to anywhere > dh_install: usr/share/accounts/providers/kde/ktp-kde-talk.provider exists in > debian/tmp but is not installed to anywhere > dh_install: missing files, aborting > make[2]: *** [override_dh_install] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/07/ktp-accounts-kcm_15.08.3-2_unstable_reb.normal.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.
