Description of problem: Loaded plugins: refresh-packagekit Setting up Upgrade Process Resolving Dependencies --> Running transaction check ---> Package qt.i386 1:4.4.0-1.fc10 set to be updated --> Finished Dependency Resolution Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Updating: qt i386 1:4.4.0-1.fc10 koji 2.8 M Transaction Summary ============================================================================= Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s) Total size: 2.8 M Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : qt ######################### [1/2]Error unpacking rpm package 1:qt-4.4.0-1.fc10.i386 error: unpacking of archive failed on file /usr/lib/qt4/bin: cpio: rename Version-Release number of selected component (if applicable): To: qt-4.4.0-1.fc10 From: qt-4.3.4-11.fc9 How reproducible: 100% Steps to Reproduce: 1. yum -y upgrade qt Actual results: See above Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=xulrunner-cpio
Ugh, the ages-old RPM directory/symlink glitch? :-( This probably needs a pretrans hack or some ugliness like that. Rex, do you still think the change to use %{_bindir} as the %{_qt4_bindir} was a good idea? IMHO we should revert this change, which will instantly make this bug disappear, and also make Qt 3 apps using qmake build again.
Actually I reverted this right now, hopefully in time for the imminent Rawhide push. Should be fixed in 4.4.0-2.fc10 which is now building. Rex, if you still want this change, we'll have to find a way to make it happen without breaking upgrades from Qt 4.3!
Wierd, I had tested upgrades locally, and it seemed to work ok for me. ?? I agree with the revert, looks like it needs more love/testing before trying again.
The build completed at 11:49 UTC, the Rawhide push starts at 12:00 UTC, with newRepo and stuff, this was probably too late. :-( So we probably have a broken Qt in the first F10 Rawhide, fun...
qt 1:4.4.0-2.fc10 seems good to me :)
Turns out my tests worked, because that was before I relented and put in a questionable backwards-compat symlink at the old location. simply omitting the symlink would work too.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
No, no.. this is on rawhide (see my comment 0)