Description of problem: The past week there were updates for glib2, pango, and qt. When I attempted to update the first time, PackageKit notified me that there was a transaction error: Test Transaction Errors: file /usr/share/qt4/translations/assistant_adp_de.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_adp_ja.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_adp_pl.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_adp_zh_CN.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_adp_zh_TW.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_de.qm from install of qt-1:4.5.2-1.fc11.x86_64 conflicts with file from package qt-1:4.5.1-13.fc11.i586 file /usr/share/qt4/translations/assistant_pl.qm from install of qt-1:4.5.2-1... This sort of error reproduces on glib2 and pango as well. If I uncheck glib2, pango, and qt from updating the first update completes successfully. Immediately when the update completes, PackageKit tells me there are more updates. This time it shows glib2, pango, and qt for both arches and this second update pass completes successfully. Version-Release number of selected component (if applicable): PackageKit-0.4.8-2.fc11.x86_64 qt-4.5.1-13.fc11.x86_64 qt-4.5.1-13.fc11.i586 glib2-2.20.3-1.fc11.x86_64 glib2-2.20.3-1.fc11.i586 pango-1.24.2-1.fc11.x86_64 pango-1.24.2-1.fc11.i586 How reproducible: Always Steps to Reproduce: 1. Have one of the following versions of qt, glib2, or pango with both arches installed and at least one other package to update. 2. Perform update. 3. Get transaction error. 4. Uncheck qt/glib2/pango. 5. Update successfully. 6. Perform second update. Actual results: Two updates had to be performed. Expected results: One update to be performed. Additional info: This has happened to me on two 64-bit installs. Also another user has reported[1] it on the fedora-test list. Unchecking the updates led me to find bug 513856. [1] https://www.redhat.com/archives/fedora-test-list/2009-July/msg00492.html
I'm seeing the same thing. The last few times PackageKit failed to update the system due to multi-lib dependency problems but issuing a "yum update" from the shell worked.
Just wanted to add a "me too". Same exact problem on the same packages.
Richard, any ideas on this? -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 514459 has been marked as a duplicate of this bug. ***
*** Bug 515128 has been marked as a duplicate of this bug. ***
*** Bug 513752 has been marked as a duplicate of this bug. ***
*** Bug 515150 has been marked as a duplicate of this bug. ***
*** Bug 517674 has been marked as a duplicate of this bug. ***
Richard any movement on this issue? -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've not run into this issue for a few weeks -- so I'm not sure.
Can any of the reporters or commenters advise if this is still an issue? -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
There was a gtk2 update a week ago that ran successfully, so I suppose this has been fixed somewhere along the way. With no mention of code changes that could have led to this being fixed, I'm not sure I trust closing this bug as fixed.
After seeing several multi-arch updates succeed over the past two months I'm satisfied enough to close this.