> ssh-krb5 was built a while ago using libssl0.9.6. libldap2 will shortly
> be uploaded and links against libssl0.9.7. ssh-krb5 ends up linked
> against libldap2 though libpam-ldap and the PAM modules (or libnss-ldap
> and the nsswitch.conf, either way). The ssh-krb5 process ends up linked
> against 0.9.6 and 0.9.7 and segfaults. How would your 'solution'
> prevent that? Often libraries are updated before programs are updated
> to that library. Sure, you may not be able to rebuild ssh-krb5 but that
> doesn't really matter unless you attempt to rebuild every binary every
> time a new library is uploaded and remove all the FTBFS packages.
> Needless to say, I don't think that would work very well.
Build-Dependencies will not be satisfied until they are fixed,
and when they are fixed, they won't be linked with the wrong
libraries, so the problem will not happen.
Consider libpng2/3 problem, and see if it possible to
still possible to cause problem while following libpkg-guide.
regards,
junichi
