Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I came across this problem while trying to get the 32-bit version of Firefox running on my Athlon64 laptop. I needed to install the 32-bit version of "xorg-x11-deprecated-libs"; however, when I checked the version that I already had, I noticed that I had two versions installed, both of which were x86_64. Here's what yum list installed "xorg-x11-deprecated-libs*"
said...
After asking someone on the 'net, he gave me the following command to list all packages on my system which have duplicates: rpm -aq --queryformat "%{NAME}\n" | sort | uniq -c | grep -v -E " *1 " . The output of that command is as follows...
The number before each package shows how many versions of each package is installed. Apparently, only a few packages (i.e. kernel) are supposed to have duplicates. Why, then, might I have so many multiple packages installed on my system? More importantly, how can I fix this?
I do all of my updating through yumex, and use the default Fedora mirrors. Also, I've never had the system crash during an update.
well since you are running x86_64 you will end up with two sets of libraries the 32 bit and 64 bit. The 64 bit system gives you the option to run programs in either mode.
I'm running FC4 x86_64, but since flash, media codecs, and jre are not supported on 64 bit browsers, then I had to either download 32bit binaries or end up compiling in 32 bit mode. This is the reason why you have two sets of libraries. In case you need to compile in 32 bit mode, and run 32 bit programs you will already have the libraries installed.
Of course your hard drive will be larger than a 32 bit one. If saving hard drive space is needed then you should probably run a 32 bit system.
I see what you're saying about having both 32- and 64-bit libraries installed for sake of compatibility. That's actually what I'd *like* to have going on here, but that's not what is happening. You'll notice in the first CODE box I listed, what I actually have is multiple versions of the same 64-bit libraries installed. It's as though, when I update, yum installs the new packages but fails to remove the old ones.
I have the same problems using yum.
My nightly install gives me the same list of dupicated packages and I assume that's right as I use both architectures. The error lines say:
W: There are multiple versions of "gnome-vfs2" in your system.
This package won't be cleanly updated, unless you leave
only one version. To leave multiple versions installed,
you may remove that warning by setting the following
option in your configuration file:
RPM::Allow-Duplicated { "^gnome-vfs2$"; };
To disable these warnings completely set:
RPM::Allow-Duplicated-Warning "false";
However, RPM:: etc. is a command to set in apt-conf not in yum.conf IMHO, so I don't know how to solve it.
It may well be that some botched upgrade has not removed all old versions from the database but I cannot remove it as it's a problem of the RPM database. Locate gives you only 2 names in 2 different directories with the same name e.g. with alsa I see /usr/alsalib/ and /usr/lib64/alsalib/ and and with gnome-vfs2 only one package is installed.
Is the RPM::... command to be set in yum.conf?
Joep
found a wonderful program called smart that removed 300 dups in one setting from the command line... GREAT program for upgrades that leave junk.... did a good clean job of rpms too
here is the link... they have rpms for different disttros
Thanks,
I will look into it. In the mean time I have completely reorganized my system and done a complete new installation of FC5 and SMART may well become a good replacement of yum.
Joep
I just had the same problem on Fedora Core 5 32-bit. I did a clean install and ran my special setup script (because I setup a lot of systems). I think the problem was that I removed the SELinux utilities but didn't reboot immediately, so that when I ran yum upgrade, rpm had an error on setting the SELinux context of files. Then, rpm decided to keep both the old and new packages. You might get the same effect anytime by removing SELinux utilities, running in SELinux mode, and upgrading a lot of packages. At least, that's my guess.
Anyway, running "smart fix *" is currently fixing the problem quickly and saving me 1.5 GB. Thanks for that tip.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
