Bug#949239: ktp-contact-runner: FTBFS on various archs
Source: ktp-contact-runner
Version: 17.08.3-1
Severity: serious
Tags: ftbfs sid
Justification: FTBFS on various archs
Hi! During a package rebuild your package FTBFS:
<https://buildd.debian.org/status/package.php?p=ktp-contact-runner>
<https://buildd.debian.org/status/fetch.php?pkg=ktp-contact-runner&arch=amd64&ver=17.08.3-1%2Bb1&stamp=1575646292&raw=0>
The error seems to be:
/usr/include/telepathy-qt5/TelepathyQt/_gen/types.h:15:10: fatal error: QDBusArgument: No such file or directory
15 | #include <QDBusArgument>
| ^~~~~~~~~~~~~~~
In file included from /usr/include/telepathy-qt5/TelepathyQt/types.h:30,
from /usr/include/telepathy-qt5/TelepathyQt/Types:8,
from /usr/include/telepathy-qt5/TelepathyQt/presence.h:31,
from /usr/include/telepathy-qt5/TelepathyQt/Presence:8,
from /usr/include/KTp/presence.h:25,
from /usr/include/KTp/Models/presence-model.h:29,
from /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/krunner_ktp_contacts_autogen/UVLADIE3JM/../../../src/contactrunner.h:27,
from /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/krunner_ktp_contacts_autogen/UVLADIE3JM/moc_contactrunner.cpp:9,
from /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/krunner_ktp_contacts_autogen/mocs_compilation.cpp:2:
/usr/include/telepathy-qt5/TelepathyQt/_gen/types.h:15:10: fatal error: QDBusArgument: No such file or directory
15 | #include <QDBusArgument>
| ^~~~~~~~~~~~~~~
compilation terminated.
Thanks for your work, Lisandro.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf
Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: