Created attachment 705005 [details] Output from 'yum check-update', 'yum update' and 'yum update --skip-broken'. Description of problem: After running 'yum update --skip-broken' I have some remaining packages, that aren't possible to update: Packages skipped because of dependency problems: 1:compiz-0.8.8-17.fc17.i686 from updates pyldb-1.1.6-1.fc17.i686 from updates python-tdb-1.2.10-15.fc17.i686 from updates 2:samba-3.6.12-1.fc17.1.i686 from updates 2:samba-client-3.6.12-1.fc17.1.i686 from updates 2:samba-common-3.6.12-1.fc17.1.i686 from updates 2:samba4-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-client-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-common-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-dc-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-dc-libs-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-libs-4.0.0-60alpha18.fc17.i686 from updates 2:samba4-python-4.0.0-60alpha18.fc17.i686 from updates Version-Release number of selected component (if applicable): $ rpm -q yum compiz samba samba4 yum-3.4.3-30.fc17.noarch compiz-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.i686 samba-3.6.6-91.fc17.1.i686 samba4-4.0.0-57alpha18.fc17.i686 How reproducible: yum update --skip-broken Steps to Reproduce: 1.yum update --skip-broken 2. 3. Actual results: Can't update with 'yum update' or 'gpk-update-viewer'. Expected results: No packages to update. Additional info: Message from gpq-update-viewer (Failed to process request): samba4-common conflicts with 2:samba-common-3.6.12-1.fc17.1.i686 samba4-client conflicts with 2:samba-client-3.6.12-1.fc17.1.i686 compiz-gtk-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.i686 requires compiz = 0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16 samba4 conflicts with 2:samba-3.6.12-1.fc17.1.i686 compiz-gtk-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.i686 requires libopengl.so compiz-gtk-0.9.5.92.1-0.2.gite676f1b12eb8db3a76978eed5bfc7c2cf9a0b6ce.fc16.i686 requires libcomposite.so : Success - empty transaction
*** This bug has been marked as a duplicate of bug 916415 ***