Description of problem: Yum update on 2009-02-25 on x86-64 system encountered following error: Transaction Check Error: file /usr/lib64/libmarblewidget.so.4 conflicts between attempted installs of kdeedu-libs-4.1.2-2.fc10.x86_64 and kdeedu-marble-4.2.0-7.fc10.x86_64 How reproducible: I believe this will only occur if you have digikam-libs installed. Additional info: Remove digikam-libs first, then do the update and the kdeedu libs conflict goes away. digikam-libs cannot be reinstalled after this.
Seth, any ideas why yum isn't including kdeedu-libs-4.2.0 in the tranaction when installing/upgrading kdeedu-marble-4.2.0? (I'll go double check to see if we have any horked Obsoletes or something). I'd really hate to have to put into kdeedu-marble: Conflicts: kdeedu-libs < 4.2.0
I suspect there's simply some broken mirror which does not have the current kdeedu-libs package.
Maybe has something to do with kdeedu-libs-4.1.x and kdeedu-marble-4.2.0 both Providing libmarblewidget.so.4
Michael, do you recall what was installed prior to the update? rpm -q kdeedu kdeedu-libs digikam so that I can see if I can reproduce what's going on.
Unfortunately I don't. That's also the only 64bit box I have installed at the moment. If I run the rpm query now I just get that none of those packages are currently installed. I have one other F10 box at home that has not been updated yet and that has digikam installed but no kdeedu libs. It reports: mjhammel(tty1)$ rpm -q kdeedu kdeedu-libs digikam package kdeedu is not installed package kdeedu-libs is not installed digikam-0.10.0-0.12.beta8.fc10.i386 If you check the URL for this report it points to my blog entry about this issue. You'll find a link to the German FedoraForum entry where I found the tip about removing digikam. The person who posted there might have additional information on how they figured out it was digikam that needed to be removed.
Minimal reproducer: install kdeedu-libs-4.1.2 , from f10 release yum install digikam pulls latest digikam, kdeedu-marble into transaction -> boom. I can't find any scenario where just: yum update fails.
shrug, the forum posts seem inconclusive, mentioning even that the problem went away in subsequent reboots/updates, so let's consider the matter closed... unless we see any new evidence to the contrary.
*** Bug 487815 has been marked as a duplicate of this bug. ***
reopening, got details in #fedora-kde today. An initial f10 kde install with kdeedu will exhibit this. [14:20] <Tuju_> Transaction Check Error: [14:20] <Tuju_> file /usr/lib/kde4/plugins/marble/CompassFloatItem.so conflicts between attempted installs of kdeedu-marble-4.2.0-7.fc10.i386 and kdeedu-libs-4.1.2-2.fc10.i386 [14:20] <Tuju_> inchi i386 1.0.2-0.3.fc9 fedora 563 k [14:20] <Tuju_> kdeedu-libs i386 4.1.2-2.fc10 fedora 998 k [14:20] <Tuju_> kdeedu-marble i386 4.2.0-7.fc10 updates 18 M [14:20] <Tuju_> libmsn i386 4.0-0.10.beta4.fc10 updates 316 k Not sure how/why yum isn't trying to update kdeedu-libs-4.2.0 as well here. A workaround is to first: yum update yum Seth, would adding Conflicts: kdeedu-libs < 4.2.0 to kdeedu-marble help f10's stock yum resolve this?
Details are that we split marble into a subpackage (in kde-4.2.0 update) so that other apps could depend on it, see bug #470577
Shrug, workaround known (comment #9, "yum update yum" first) and, I'll add the Conflicts mentioned there too (not sure if it'll help...) for the upcoming kde-4.2.2 update.
Maybe a less-bad solution (which I'll try first) is to add to -marble: Requires: kdeedu-libs = %{version}-%[release} at the expense of adding (almost) ~2mb of not-strictly-required bloat
reopen, pending update.
kdeedu-4.2.1-2.fc10.1 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kdeedu-4.2.1-2.fc10.1
kdeedu-4.2.1-2.fc9.1 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/kdeedu-4.2.1-2.fc9.1
kdeedu-4.2.1-2.fc10.1 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kdeedu'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3059
gpsd-2.39-3.fc10, kdeedu-4.2.1-3.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gpsd kdeedu'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3059
kdeedu-4.2.1-2.fc9.1 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
kdeedu-4.2.1-2.fc10.1 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
I just installed Fedora 10 X64 and after installation wanted to do a yum update but was still bitten by this bug.
*** Bug 497915 has been marked as a duplicate of this bug. ***
rats, it's down to yum not handling the update, our only/best workaround is to yum update yum first, before doing subsequent updating.
I have a similar bug where just "yum update" breaks: $ yum update kdeedu-marble-4.2.1-2.fc10.1.x86_64 from updates has depsolving problems --> kdeedu-marble conflicts with kdeedu-libs Error: kdeedu-marble conflicts with kdeedu-libs $ rpm -qa | egrep kdeedu [no output] $ rpm -q digikam digikam-0.10.0-0.11.beta7.fc10.x86_64 However, this seems to be nondeterministic. I have a few global excludes which ought to be irrelevant: exclude=xorg-x11-server-Xorg xorg-x11-drv-* kmod-* kernel* cups* but if I use a yum config which omits this line (and is otherwise identical) then it manages to solve the dependencies. It's weirder than that. With the exact same config file (including the exclusions), "yum -d7 update" fails but "yum -d8 update" succeeds. I'll attach the logs of those two commands - they are remarkably dissimilar. Would "obsoletes" not be better than "conflicts"?
OK, I won't attach the logs because I've just read comment #22. # yum list yum Loaded plugins: refresh-packagekit Excluding Packages in global exclude list Finished Installed Packages yum.noarch 3.2.20-5.fc10 installed Available Packages yum.noarch 3.2.21-2.fc10 updates As it seems to be fixed in the newer version of yum I guess not much point in worrying about it.
I hit this issue with on Fedora 10 installs. My kickstart enables the update repo and installs the KDE desktop, which causes an installation error due to the above conflicts. As a workaround, I've removed KDE from kickstart and install it later. Not ideal but it works.
You can --exclude one of the two conflicting packages, maybe? Put the --exclude in the "repo" configuration directive.
great...fantastic...however I have no idea what a kickstart is and I need to install F10...I had no such problem during the last install of F10 I tried leaving off kdedu from the install menu to no avail. What can I leave off to allow F10 to install??? Ive tried 5-6 times already
Landon - Not sure if you have been successful in installing Fedora 10. Here is what I did. During the install sequence deselect the Fedora 10 updates repository and complete the install. Once the system is running you can execute 'yum update yum' in a terminal. The system should prompt you to update automatically which seems to add the packages in the Fedora 10 updates repository. Note that if you do not execute the 'yum update yum' prior to the system update, you get the same error. Anyway, worked for me.
simple : I just selected "configure later" and downloaded KDE later! after much work, I have Fedora 10 as it was before the mess and for that matter even better.