Source: sssd Version: 2.8.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_missing --fail-missing > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/PKG-INFO exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/dependency_links.txt > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/top_level.txt exists > in debian/tmp but is not installed to anywhere > dh_missing: error: missing files, aborting > The following debhelper tools have reported what they installed (with > files per package) > * dh_install: libipa-hbac-dev (3), libipa-hbac0 (2), libnss-sss (1), > libpam-sss (4), libsss-certmap-dev (3), libsss-certmap0 (3), libsss-idmap-dev > (3), libsss-idmap0 (2), libsss-nss-idmap-dev (3), libsss-nss-idmap0 (2), > libsss-simpleifp-dev (4), libsss-simpleifp0 (2), libsss-sudo (1), > python3-libipa-hbac (1), python3-libsss-nss-idmap (1), python3-sss (5), sssd > (0), sssd-ad (3), sssd-ad-common (3), sssd-common (96), sssd-dbus (5), > sssd-idp (4), sssd-ipa (3), sssd-kcm (6), sssd-krb5 (4), sssd-krb5-common > (2), sssd-ldap (3), sssd-proxy (2), sssd-tools (14) > * dh_installdocs: libipa-hbac-dev (0), libipa-hbac0 (0), libnss-sss > (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), > libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), > libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), > libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), > python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), > sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), > sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0) > * dh_installexamples: libipa-hbac-dev (0), libipa-hbac0 (0), > libnss-sss (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), > libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), > libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), > libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), > python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), > sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), > sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0) > If the missing files are installed by another tool, please file a bug > against it. > When filing the report, if the tool is not part of debhelper itself, > please reference the > "Logging helpers and dh_missing" section from the "PROGRAMMING" guide > for debhelper (10.6.3+). > (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) > Be sure to test with dpkg-buildpackage -A/-B as the results may vary > when only a subset is built > If the omission is intentional or no other helper can take care of this > consider adding the > paths to debian/not-installed. > make[1]: *** [debian/rules:102: override_dh_missing] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/sssd_2.8.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
