[F13] update failure: nss*

[Michael Schwendt]

On Wed, 15 Sep 2010 08:21:44 -0700, JD wrote:

> 
> 
> On 09/15/2010 03:10 AM, Michael Schwendt wrote:
> > On Tue, 14 Sep 2010 10:43:37 -0700, JD wrote:
> >
> >>> Recently, even the nss.pc pkgconfig file's automatic Provides disappeared
> >>> unexpectedly(?) because of some %global definitions in the spec file for
> >>> specific minimum versions of build requirements.
> >> On my F13, I have
> >> nss-softokn-freebl-3.12.7-3.fc13.i686
> >> nss_ldap-264-10.fc13.i686
> >> nss-3.12.7-4.fc13.i686
> >> nss_db-2.2.3-0.3.pre1.fc13.i686
> >> nss-softokn-devel-3.12.7-3.fc13.i686
> >> nss-mdns-0.10-8.fc12.i686
> >> nss_compat_ossl-0.9.6-1.fc13.i686
> >> nss-util-3.12.7-2.fc13.i686
> >> nss-sysinit-3.12.7-4.fc13.i686
> >> nss-softokn-3.12.7-3.fc13.i686
> >> nss-tools-3.12.7-4.fc13.i686
> >>
> >>
> >> and
> >>
> >> yum check
> >>
> >> does not flag any missing dependenceies .
> > You cannot have any missing dependencies with packages that are
> > installed already.
> Well, that begs the question: how did these packages get installed
> on my system when I did not specifically install them individually?

Rephrasing the question might be helpful. What exactly do you want
to have explained?

Some packages are installed because they are needed by other
packages. Some of them are added as requirements when installing
Updates. You can run some RPM queries to examine the packages (not just
the included files) and ask RPM about what requires them.