Kurt Roeckx <k...@roeckx.be> writes: > This might be related to sudo failing with this message: > /usr/bin/ld: warning: libgssapi_krb5.so.2, needed by > /usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../../../lib/libldap.so, not found > (try using -rpath or -rpath-link) > /usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../../../lib/libldap.so: undefined > reference to `gss_release_n...@gssapi_krb5_2_mit' > [...]
That's disturbing. Is the libgssapi_krb5.so.2 file truly not present? > That's with libldap-2.4-2 2.4.15-1. libldap-2.4-2 itself does not > depend on libgssapi-krb5-2, but it depends on libkrb53 (>= 1.6.dfsg.2) > and libkrb53 in turn depends on libgssapi-krb5-2. Yes, we're in the middle of a library transition in which libkrb53 was broken apart into its constituent libraries so that they can be more easily managed going forward. But the symbols provided by the library didn't change, so as long as all the dependencies are satisfied, all of the applications should be happy. > If this is intentional, maybe libldap-2.4-2 should depend on a > higher version of libkrb53 instead. I'm not sure I understand how that would fix this, but I'm mystified by this error and how it could be happening. Oh, hm, could the buildd have installed libkrb53 and libgssapi-krb5-2, then removed libgssapi-krb5-2 and somehow left an older version of libkrb53 installed that didn't depend on libgssapi-krb5-2, so that the dependency is satisfied but the libraries are missing because of the removal of a package that Replaced them? I can't imagine this happening unless the buildd for some reason had a mixed set of libkrb53 and libgssapi-krb5-2 packages from different krb5 releases installed, though. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
