Installing virt-manager from updates-newkey on a fully updated Fedora 9 install currently fails because it is looking for libvirt-0.4.5-2 and libvirt-python-0.4.5-2, yet the version in the updates-newkey repositories on all mirrors tried are 0.4.6-2. Here is the full dependency chain reported by yum: Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: virt-manager i386 0.5.4-4.fc9 updates-newkey 1.2 M Installing for dependencies: bridge-utils i386 1.2-4.fc9 fedora 28 k gnome-python2-gnomekeyring i386 2.22.0-4.fc9 updates-newkey 20 k gtk-vnc i386 0.3.7-2.fc9 updates-newkey 79 k gtk-vnc-python i386 0.3.7-2.fc9 updates-newkey 13 k iscsi-initiator-utils i386 6.2.0.870-0.0.fc9 updates-newkey 587 k libvirt i386 0.4.5-2.fc9 updates-newkey 1.2 M libvirt-python i386 0.4.5-2.fc9 updates-newkey 89 k python-virtinst noarch 0.300.3-7.fc9 updates-newkey 193 k xen-libs i386 3.2.0-15.fc9 updates-newkey 160 k
Either your mirror is carrying bogus repodata, or your yum client has cached old repodata. The mirror I used has 0.4.6 and the repodata shows 0.4.6 # yum list | grep libvirt | grep newkey libvirt.i386 0.4.6-2.fc9 updates-newkey libvirt-devel.i386 0.4.6-2.fc9 updates-newkey libvirt-java.i386 0.2.1-1.fc9 updates-newkey libvirt-java-devel.i386 0.2.1-1.fc9 updates-newkey libvirt-java-javadoc.i386 0.2.1-1.fc9 updates-newkey libvirt-python.i386 0.4.6-2.fc9 updates-newkey ocaml-libvirt-devel.i386 0.4.1.1-3.fc9 updates-newkey In any case this isn't a virt-manager bug - report it to Fedora infrastructure if you have problems with repositories
OK, sorry for the noise, it was a local cache; first time this has happened to me so I didn't think to look there. 'yum clean all' and another install attempt did it. Thanks for the fast and decisive response.