Conflicting package messages !!

[zonkel]

I'm trying to install our last package and getting conflicting confirmation messages from rpm when I try to confirm the installation:

$ rpm -ivh compat-libstdc++-33-3.2.3-47.3.x86_64.rpm
Preparing... ########################################### [100%]
package compat-libstdc++-33-3.2.3-47.3 is already installed

$ rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' compat-libstdc++
package compat-libstdc++ is not installed

$ rpm -qav | grep compat-libstdc
compat-libstdc++-33-3.2.3-47.3
compat-libstdc++-33-3.2.3-47.3
compat-libstdc++-296-2.96-132.7.2

$ rpm -ev compat-libstdc*
error: package compat-libstdc++-33-3.2.3-47.3.i386.rpm is not installed
error: package compat-libstdc++-33-3.2.3-47.3.ia64.rpm is not installed
error: package compat-libstdc++-33-3.2.3-47.3.x86_64.rpm is not installed

$




Is this package installed or not? Is there some rpm database that may be corrupted?

[matonb]

Hi zonkel,

compat-libstdc++ comes in a few guises, your trying to install the "33" version, odd naming convention never really looked into why it's used though.

try:

$ rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' compat-libstdc++-33

To remove all of the compat-libstdc++ packages (x86_64 and i386) you can use the --allmatches switch

$ rpm -e --allmatches compat-libstdc++-33

[madjak]

Use rpm -qil compat-libstdc++......... to find out where its supposed to be installed and then go and track it down.

You can always use the '--force' option in rpm or rebuild the rpm database if you think its become corrupt.

[zonkel]

OK good deal, adding the -33 does solve this issue, thanks.

[zonkel]

Had to use the -33 with this suggested by mantob but this gives all the details about the package - thnks