Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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
--> 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?
I think the fault may be of mixing incompatible repositories
specially dag.wieers & livna
If you have updated with both these repositories enabled then uninstall all those packages ,disable one of the repositories and install again.
You can go through following links for additional information