FC13 nss-softokn-freebl update issues

[Bill Nottingham]

Elio Maldonado (emaldona at redhat.com) said: 
> Not sure but I strongly suspect a change made to nss.spec to be the cause. 
> See https://bugzilla.redhat.com/show_bug.cgi?id=596840#c7 

It's due to the fact that nss-softokn-freebl (actually, *all* the nss/nspr
libraires) do not fit the normal library naming, so it's not explicitly pulled for
multilib. For any update or release set that's composed with a package that explicitly
requires a compat arch of nss-softokn-freebl (such as glibc, libpurple,
pam_pkcs11, etc.), it will get pulled in via dependency resolution. F-13
updates has none of these, so it doesn't.

We could add some hacks to mash to get it pulled in, but I must ask...
why do all the NSS/NSPR libraries version their libraries in the library
name instead of the so version (i.e., libfreebl3.so instead of
libfreebl.so.3)?

Bill