Hide Forgot
=> vdsm-4.9.3.2-0.fc17.src.rpm => vdsm-cli-4.9.3.2-0.fc17.noarch in fedora-development-i386 File conflict with: vdsm-4.9.3.2-0.fc17.i686 /usr/share/vdsm/SecureXMLRPCServer.pyc /usr/share/vdsm/SecureXMLRPCServer.pyo /usr/share/vdsm/vdscli.pyc /usr/share/vdsm/vdscli.pyo [semi-automated bug report]
We didn't have any other report about this in an year. The problem was most likely a package conflict between different repositories. Feel free to reopen adding more information (e.g. what repositories you are using) if you still experience the issue.
D'oh! Every details you would need was present in the ticket when it was opened. Even the repo name. You could have asked _much_ earlier in case you didn't understand the report. A year later, the files in the packages have been moved or replaced. It may be that this has resolved the conflict. A future run of the conflicts checker will tell.
And no, it was not "a package conflict between different repositories". It was a solely a conflict between subpackages built from the vdsm src.rpm. All details have been in the ticket.
(In reply to comment #3) > And no, it was not "a package conflict between different repositories". It > was a solely a conflict between subpackages built from the vdsm src.rpm. All > details have been in the ticket. This has been resolved in vdsm-4.10.0-7.fc17 moving the files into a separate subpackage called vdsm-python. This bug was never reported (other than from you) as there's no kvm support on i686 and vdsm-cli-4.9.3.2-0.fc17.noarch wasn't conflicting with vdsm-4.9.3.2-0.fc17.x86_64. Than you for reporting the bug.