Hide Forgot
Description of problem: Apparently, the RPM dependency of the package is "=", should probably be >= [root@master-vds9 yum.repos.d]# yum deplist libvirt-lock-sanlock-0.9.4-17.el6.x86_64 |grep libvirt package: libvirt-lock-sanlock.x86_64 0.9.4-17.el6 dependency: config(libvirt-lock-sanlock) = 0.9.4-17.el6 provider: libvirt-lock-sanlock.x86_64 0.9.4-17.el6 dependency: libvirt = 0.9.4-17.el6 Version-Release number of selected component (if applicable): libvirt-lock-sanlock-0.9.4-17.el6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
> Apparently, the RPM dependency of the package is "=", should probably be >= No, that is intentional. Any libvirt plugins *must* come from exactly the same build. The brew build has all necessary packages: http://download.devel.redhat.com/brewroot/packages/libvirt/0.9.4/17.el6/x86_64/ So this dependency problem is either caused by a mis-configured local yum install, or by pointing at a yum repository which has been misbuilt & is missing RPMs.
It clearly is a bug with *something* since Yaniv is pointing to an official repo. Reopening so we can figure out where the problem is and get it resolved by someone.
No, as suggested above, it was a local yum repo mis-configuration. RHEL has 2 separate channels (the base & optional) and only the base was configured, hence there was no repo for updating the sanlock plugin