Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Write an article for LinuxForums Today! Win Great Prizes!
Usually when I run yum update it runs to completion and there aren't any updates left over. But the current update has been completely different.
Usually I just run "yum -y update" in a terminal. This time I did that. It downloaded about 300 packages and then started a "transaction check" and then it gave a single error message about a conflict.
This is the output of "kyum" a GUI for "yum". I was seeing what the output would be if I tried to update "bind". I ran this later:
***Transaction Check Error: file /etc/named.conf from install of bind-9.3.2-33.fc5 conflicts with file from package caching-nameserver-7.3-5.FC5
Finished Transaction Test
Process exited normally with code 1.
A good install ends with 0, even though it says "exited normally" this is an error message. It's really lousy that a single error can mess up a whole update.
There were several "packages" that wouldn't update. The biggest bunch were "kde. . ." packages but they all had varying error messages. Again this is output from "kyum":
(Command being executed: yum -y update kdebase).
Loading "kernel-module" plugin
Loading "fedorakmod" plugin
Loading "fastestmirror" plugin
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package kdebase.x86_64 6:3.5.4-0.5.fc5 set to be updated
---> Downloading header for kdebase to pack into transaction set.
---> Package kdebase.i386 6:3.5.4-0.5.fc5 set to be updated
--> Running transaction check
--> Processing Dependency: kdelibs >= 6:3.5.4 for package: kdebase
--> Processing Dependency: htdig for package: kdebase
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please
.
.
.
*** file /usr/share/servicetypes/renamedlgplugin.desktop from install of kdelibs-3.5.4-0.3.fc5 conflicts with file from package kdelibs-3.5.1-2.3
*** file /usr/share/servicetypes/scriptinterface.desktop from install of kdelibs-3.5.4-0.3.fc5 conflicts with file from package kdelibs-3.5.1-2.3
Process exited normally with code 1.
I don't even know what to ask except does anyone know what's going on?
Looks like your yum database is getting a little out of step. If a 'yum clean' doesn't work, then I suggest you try uninstalling and reinstalling the offending packages. This may take some time, but could be worth it.
The only drawback is that it's a KDE package, so you'll probably want to fire up the Gnome desktop while you do this.
Start by uninstalling kdelibs-3.5.1-2.3 with:
Code:
rpm -e kdelibs-3.5.1-2.3
It could be that you've installed KDE on that system from a non-Fedora source or you've upgraded from an earlier version of fedora, and rpm is complaining about it; the Fedora Core 5 stuff should end with ...fc5. Once that package is gone, it should smooth things out.
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe