Description of problem: Rpm doesn't appear to trigger on dependencies properly. [root@Waves ~]# rpm -q --requires calibre |grep popp libpoppler.so.13()(64bit) [root@Waves ~]# rpm -q poppler calibre poppler-0.16.3-1.fc15.x86_64 calibre-0.7.44-3.fc15.x86_64 [root@Waves ~]# rpm -qf /usr/lib64/libpoppler* poppler-glib-0.16.3-1.fc15.x86_64 poppler-glib-0.16.3-1.fc15.x86_64 poppler-0.16.3-1.fc15.x86_64 poppler-0.16.3-1.fc15.x86_64 [root@Waves ~]# rpm -q --whatrequires poppler poppler-utils-0.16.3-1.fc15.x86_64 poppler-glib-0.16.3-1.fc15.x86_64 [root@Waves ~]# rpm -qf /usr/lib64/libpoppler* --whatrequires no package triggers /usr/lib64/libpoppler-glib.so.6 no package triggers /usr/lib64/libpoppler-glib.so.6.0.0 no package triggers /usr/lib64/libpoppler.so.13 no package triggers /usr/lib64/libpoppler.so.13.0.0
Heh, interesting quirk. The deal with "no package triggers..." is that --whatrequires and -f don't make sense (to rpm, although I think I see what you're trying to do) together. Rpm used to give "one type of query/verify may be performed at a time" error on that but the sanity check has apparently gotten broken somewhere along the way, and it ends up doing something rather bogus. Will fix. The other aspect of this is that --whatrequires doesn't work quite the way you think: --whatrequires expects "capability name" as its argument, and returns the packages that depend on that exact "capability" string. So 'rpm -q --whatrequires poppler' only returns packages which have an explicit "Requires: poppler" in them, not all packages that depend on something poppler happens to provide (such as library sonames). See bug 142651 for suggestions how to work around this.
Sweet, And you're right, that's pretty much what I've been doing previously, I only stumbled on this was due to some very odd things with dependencies making yum very very sad. Turned out to be a broken mirror, ( Stale "updates" repo that didn't get ..updates..) And #142651 is just a function that'll be useful.
Yup, there have been broken dependencies around poppler in F15 updates[-testing] for quite some time, apparently finally fixed now... For mostly my own referece: the sanity check got broken between rpm 4.6.x and 4.7.x in commit 2e672f3fae9d8ff7ee64ae13cfa2fe65272c2ede.
Fixed upstream...
Cheers, how is that coming along downstream?
In rawhide now as of rpm-4.9.1, F15 will get this sooner than later.
rpm-4.9.1.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/rpm-4.9.1.1-1.fc15
Package rpm-4.9.1.1-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rpm-4.9.1.1-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/rpm-4.9.1.1-1.fc15 then log in and leave karma (feedback).
appears to work well there.
rpm-4.9.1.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.