yum update problem with file /usr/lib/libpcsclite.so.1.0.0
 

Hi. i am new in the linux community, so far i like the fc6 os.
now to the real problem.
For the last 30 days i am trying to update my fc6 with yum update, but it hangs all the time at this file.

Transaction Check Error: file /usr/lib/libpcsclite.so.1.0.0 from install of libpcsclite1-1.3.2-8.fc6.at conflicts with file from package pcsc-lite-libs-1.3.1-7

[root@admir admir330]# su
[root@admir admir330]# rm -rf /usr/lib/libpcsclite.so.1.0.0
[root@admir admir330]# yum update

and even if i remove it and rerun the YUM UPDATE, it still gives me the same message. so if you have step by step solution with the commands please post it detailed with the full command and switches.(i am new).
thank you all.

I also have that problem when trying to apply the FRYSK update, if you have a graphical evironment you should use the GUI for doing the updates because after it does it's scan for available updates (which could take a few minutes on dial-up) you will get a list of all available updates with check marks next to each one, when you click on APPLY UPDATES, those with check marks will get installed. The package causing the conflict is "pcsc-lite-libs-1.3.1-7.i386.rpm or pcsc-lite-libs-1.3.1-7.x86_64.rpm" which are core packages, this means that an update package you are trying to apply needs this core package as a dependency. How to figure out which update package?
In the GUI which is found by clicking MENU/SYSTEM/SOFTWARE UPDATER when on-line and leave all check marks and click on APPLY UPDATES, the same problem will occur, but a small window pops up telling you there was an arror, click on the DETAILS to find out which update caused the error, un-check it from the list and click APPLY UPDATES again and the rest should install. Once you figure out which update package is the culprit, un-check it and don't try to apply it. You should not try to remove the other files that are conflicting as they are needed, just don't apply the update that causes the problem.

Tip: Select only a few packages at a time incase another update package might do the same although it should be un-likely as you would have been told so in terminal mode of all conflicts.

Before applying updates:
Also....I'm on dial-up and it took a long time also to update mine, if I ever have to re-build Fedora from scratch I would have to spend many days downloading those updates again. So what I do and if you have not done so yet, is change the value of "keepcache=0" to "keepcache=1" without the quotes, in /etc/yum.conf. This will leave all those downloaded updates in their respective cache folder which is in /var/cache/yum/updates/packages for updates, if you install extra packages from core packages they will stay in /var/cache/yum/core/packages, if you install any extras they will stay in /var/cache/yum/extras/packages. Than you would burn them onto a DVD or several CD's to back them up if you ever need them again.
To change the value of keepcache in yum.conf, click on "menu/system/more applications/File manager super user" and type you root password, then navigate to /etc/yum.conf, just click on the yum.conf file, it will open in a window and change that (0) to a (1) and click on FILE/SAVE before applying those updates because after Fedora applies the updates they will get deleted if the value of "keepcache" is set at (0).
And when/if you re-build you would have to select Sofware Updater on a new installation and wait till it searchs for available updates before those folders will show up on a new installation, just pump them into their respective folders (don't worry about the headers, they are small, but you can back them up too if you so desire" before applying any updates. Chances are alot of them may not be good anymore as there might be a more recent update but not all will have new updates and you will save some time.

Thanks for the tips
 

Sup.

Yesterday i removed the file pcsc-lite-libs-1.3.1-7 as SU with command RM -RF, and re-ran the updates. i have a high speed connection of 1.5mb/s, which helps in my case with over 600 updates.
the transaction check went trough, but now my x-server can not start. keeps telling me to look inside the log file to figure out what the problem might be. if i can find the log file i will post it.

thanks.

I'm not sure sure if using the "rm -fr" command did everything you were hoping, all these updates from Fedora are .rpms which are not individual files but more like a package of many files & scripts that once installed can be spread all over the filesystem, by using the "rm -fr" command you may only be removing a small part of the package as a whole. The beauty of the RPM package management system, is that RPM keeps track of everything that is part of a particular package, as well as making sure all dependencies are taken care of to keep your system running smooth (generally) and when using the right commands, you won't make a mess of your system.
For instance: My Mandrake is Red Hat based also, but when it comes to updating the kernel, they only give you a kernel-source package which is properly installed when using the rpm install command and because it is for building a new kernel or building dynamic kernel modules, it will make sure that gcc, make, and other necessary tools required for compiling kernel or modules are also installed as well as making sure to have the right versions of these tools. But you have to go through a complicated process (for a newbie) after to update your kernel with this source package before you can use it to compile modules as the modules version has to match the current running kernel, kernels updated via this route can/and usually will render your OS un-bootable with the new kernel if you make a mistake.
Fedora gives you a kernel update in the form of an .rpm, so all you do is issue one update command and you will succeed with little or no effort in compiling a new kernel because RPM does all the work for you due to scripts contained in the package which automate everything.
Generally there are three forms of commands to use with .rpm packages that will keep your system running smooth, because you will want to do one of three things when dealing with an .rpm ==> INSTALL, UPGRADE, REMOVE.

If I wanted to update/upgrade my kernel to the final current kernel update that I downloaded to my /root directory I issue this command:
[root@localhost ~]#rpm -Uvh kernel-2.6.18-1.2869.fc6.x86_64.rpm (for 64 bit)and everything will be done.

If I wanted to install Bittorrent GUI which is not already installed on my system, downloaded to my /root directory in two .rpm packages I issue this command:
[root@localhost ~]#rpm -ivh bittorrent-4.4.0-2.fc6.noarch.rpm bittorrent-gui-4.4.0-2.fc6.noarch.rpm (there is a space between the two packages listed in that command)(if you were to try and just install the Bittorrent GUI, RPM would tell you it can't because it needs the non-gui bittorent also as a dependency, if you are on-line it will tell you the other package is required, ask you if it is OK to install both, and download/install the dependency if you agree).

If I wanted to remove an .rpm package already install called pcsc-lite-libs... I would issue this command:
[root@localhost ~]#rpm -e pcsc-lite-libs-1.3.1-7.x86_64.rpm (even if both the i586 & x86_64 are installed, RPM will remove both if I just ask it to remove one as it takes care of dependencies when removing also, not leaving anything behind like Windows would do)

The (-Uvh) option represents "upgrade,verbose (let me see what's happening) and print 50 hash marks for the (h)
The (-ivh) is for installing and I want to see what's happening and it will be obvious with the 50 hash marks.
The (-e) stands for erase the package and take care of all dependencies (which could involve removing a more current dependency and replacing it (re-install) the former package required.) You cannot use the -vh option when removing.

The "rm -fr" command is for removing individual files and directories, .rpms are not individual files and are not unpacked/installed as a directory, .rpms are mostly just scripts used by gcc, make and a few other tools to build all necessary files required which are/can be spread through the entire filesystem & you would have your work cut out for you if you want to cleanly un-install an .rpm and take care of all dependencies which is all taken care of with one simple proper RPM command.

Why is your X-server not starting?? could it be because......
OR: If you have an NVIDIA graphics card like mine, you should install the kmod-nvidia .rpm package from www.rpm.livna.org or Fedora extras (make sure to get the right one for your card), I have not installed it yet because I tried it in an earlier installation and could only get 800 x 600 resolution, I have a Intel 915 chipset to which there is a .rpm package available through Fedora extras or livna that takes care of that. For now I just hit "Ctrl-Alt delete" to re-boot when the X-server does'nt start, sometimes I have to do it three or four times in a row, does'nt bother me much right now and I will try both the 915 package and NVIDIA kmod later when I catch up.