Weird duplicates in "rpm -qa" list

kayvan · #1 4th July 2005, 02:55 AM

I have a brand spanking new Fedora Core 4 system, yum updated to the latest.

While I was playing around, I noticed that some RPMs seem to be appearing twice in my list of installed RPMs:

[root@satyr2 ~]# rpm -q mikmod
mikmod-3.1.6-35.FC4
mikmod-3.1.6-35.FC4

[root@satyr2 ~]# rpm -q alchemist
alchemist-1.0.36-1
alchemist-1.0.36-1

What is going on here? Does anyone else see this sort of problem?

Do "rpm -qa | sort | less" to see this sort of thing easily on your system. Most RPMs will only appear once, but some are duplicated.

Any ideas?

---Kayvan

tejas · #2 4th July 2005, 03:10 AM

Did you reinstall these programs?

This sort of thing is common when you install by rpms, especially if you do rpm -i, instead of rpm -U

Jman · #3 4th July 2005, 05:53 AM

The strange thing is that the versions are exactly the same. Are you seeing two copies of installed files?

Perhaps it's time to dig out the ancient but ever popular rpm repair guide. Or just try to reinstall them.

dovla · #4 4th July 2005, 06:54 AM

Try runinng updatedb and rpm query after that. It is very weird to have the same version shown twice - this might be faster way of sorting database.

bytesniper · #5 4th July 2005, 08:09 AM

mine does the same thing.. he's probably running a 64 bit version of FC and what he is seeing are 2 builds of the same package: one is 32bit the other is 64bit. you get that when you install the "legacy package support" in the 64bit FC installer.

kayvan · #6 5th July 2005, 12:23 AM

Quote:

Originally Posted by bytesniper

mine does the same thing.. he's probably running a 64 bit version of FC and what he is seeing are 2 builds of the same package: one is 32bit the other is 64bit. you get that when you install the "legacy package support" in the 64bit FC installer.

Thanks! This is exactly what is going on. I looked closely at the "rpm -qil" output for one of the packages and you are correct. For example: "rpm -qil alchemist" shows files in /usr/lib for the one package and /usr/lib64 in the other package.

Do I even need the legacy package support?

---Kayvan

bytesniper · #7 5th July 2005, 06:10 AM

Quote:

Originally Posted by kayvan

Do I even need the legacy package support?

well.. technically you do not have to have it.. but i would very strongly recommend that you keep it. any 32bit application that you need will not run without it, and with a few things still lacking the 64bit universe it is a very good idea to have.