Comment 10 for bug 911592

As far as I could tell it's just evolution doing it wrong -- we can certainly see firefox and chromium appear to be fine. I couldn't check curl simply (libcurl3-nss uses libnss3). I couldn't see a list of certificate authorities in Pidgin but deleting the certificates and disconnecting/reconnecting I saw them re-added and no pop-up telling me they couldn't be validated. I haven't looked at the other reverse-build-depends of libnss3-dev.

It seemed clear that the way of looking for nssckbi in evolution was "wrong", but I still need to check to be sure if it's debian-specific or general to have a libdir for the actual nss libraries and an extra directory nss/ under that libdir for the "modules" and nssckbi. Maybe there's a better way to fix this, but I can't think of how in nss (unless we were to start shipping an extra variable in nss.pc specifically for nssckbi's path).

In other words, to make this better we could ship an extra var in nss.pc for the nssckbi path, but it looks like it was just evolution affected here; there's more investigation needed to certain whether it's worth it. libdir itself can't really be changed, since it needs to point to the actual location of the nss libraries.