How to use repoquery?

[Michael Schwendt]

On Fri, 14 Dec 2012 10:31:59 -0500, Neal Becker wrote:

> Michael Schwendt wrote:
> 
> > On Wed, 12 Dec 2012 11:04:02 -0600, inode0 wrote:
> > 
> >> On Wed, Dec 12, 2012 at 10:46 AM, Neal Becker wrote:
> >> > $ winword
> >> > p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so:
> >> > /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No
> >> > such file or directory
> >> >
> >> > $ repoquery --whatprovides /usr/lib/pkcs11/gnome-keyring-pkcs11.so
> >> > [... silence...]
> > 
> > And "Silence" means what here? That it returned without printing
> > anything? Or that it hasn't returned yet at the time of writing/sending
> > your mail about it?
> > 
> > The former is commonly written as:
> > 
> >   $ repoquery --whatprovides /usr/lib/pkcs11/gnome-keyring-pkcs11.so
> >   $
> > 
> >> > Any ideas?
> >> 
> >> Hrm.
> >> 
> >> Either
> >> 
> >> yum provides */gnome-keyring-pkcs11.so
> >> 
> >> or
> >> 
> >> repoquery --whatprovides */gnome-keyring-pkcs11.so
> >> 
> >> should work although depending on circumstances it may need to be run
> >> as root or with the --plugins option in the latter case. Using the
> >> correct full path should be ok too although it might not return all
> >> things that provide gnome-keyring-pkcs11.so.
> > 
> > If the error message is about a specific path, you would first submit a
> > query about that path. If that doesn't return anything, it can make sense
> > to submit further queries, trying to find out whether the file might be
> > available in some other place. That can lead to false positives, however,
> > depending on what you search for. And btw, searching for RPM Provides isn't
> > trivial on platforms like x86_64:
> > 
> >   $ repoquery --whatprovides /usr/lib64/pkcs11/gnome-keyring-pkcs11.so
> >   gnome-keyring-0:3.6.2-2.fc18.x86_64
> > 
> >   $ repoquery --whatprovides gnome-keyring-pkcs11.so
> >   $
> > 
> > But:
> > 
> >   $ repoquery --whatprovides 'gnome-keyring-pkcs11.so()(64bit)'
> >   gnome-keyring-0:3.6.2-2.fc18.x86_64
> >   gnome-keyring-0:3.6.2-2.fc18.x86_64
> 
> It means this:
> 
> [nbecker at nbecker1 ~]$ repoquery --whatprovides /usr/lib/pkcs11/gnome-keyring-
> pkcs11.so
> [nbecker at nbecker1 ~]$ 

Wrong path. /usr/lib => /usr/lib64 for your x86_64 installation.
As in my example above. ;)

> OTOH, 
> [nbecker at nbecker1 ~]$ repoquery --whatprovides */gnome-keyring-pkcs11.so
> gnome-keyring-0:3.4.1-2.fc17.x86_64
> gnome-keyring-0:3.4.1-4.fc17.x86_64
> 
> 
> repoquery -l gnome-keyring-0:3.4.1-2.fc17.x86_64 | grep gnome-keyring-pkcs11.so
> /usr/lib64/pkcs11/gnome-keyring-pkcs11.so
  ^^^^^^^^^^
  (!)