package reports not installed but it is

[wilburunion]

I get this on a current CentOS Linux 7.6.1810 when trying to erase Percona-Server-shared-56-5.6.42-rel84.2.el7.x86_64.rpm

[root@main ~]# yum list installed | grep percona
Percona-Server-shared-56.x86_64 5.6.42-rel84.2.el7 @percona-release-x86_64
percona-release.noarch 1.0-3 @percona-release-noarch
[root@main ~]# rpm -e Percona-Server-shared-56-5.6.42-rel84.2.el7.x86_64.rpm
error: package Percona-Server-shared-56-5.6.42-rel84.2.el7.x86_64.rpm is not installed
[root@main ~]#

these are the files it has

[root@main ~]# rpm -qlp https://repo.percona.com/centos/7/RPMS/ ... x86_64.rpm
/etc/my.cnf
/usr/lib64/libmysqlclient.so.18.1.0
/usr/lib64/libmysqlclient_r.so.18.1.0
[root@main ~]#

and the files are still there . . . as thus

lrwxrwxrwx 1 root root 17 Jan 4 09:50 libmysqlclient_r.so.18.0.0 -> libmysqlclient.so
lrwxrwxrwx 1 root root 24 Nov 29 07:40 libmysqlclient_r.so.18.1.0 -> libmysqlclient.so.18.1.0 <<<===
lrwxrwxrwx 1 root root 13 Jan 4 09:50 libmysqld.a -> libmariadbd.a

I do not see it is a dependency of mariadb, but in an earlier version - 10.1 it was installed claiming mariadb-libs was obsoleted, but NOW allegedly MariaDB-10.3.11-centos73-x86_64-compat.rpm replaces it . . . as . . .

This is what one gets if they upgrade from mariadb 5.5

MariaDB-compat x86_64 10.3.10-1.el7.centos mariadb 2.8 M
replacing mariadb-libs.x86_64 1:5.5.60-1.el7_5
MariaDB-server x86_64 10.3.10-1.el7.centos mariadb

( See e.g. https://www.zerostopbits.com/how-to-upg ... -7-5-1804/ )

Is this an RPM database error or bug anyone has seen and knows how to correct ??

[TrevorH]

The name of the package is "Percona-Server-shared-56", it's version/release number is 5.6.42-rel84.2.el7.x86_64 and the .rpm is the extension given to the file that contains that package. You need to specify the .rpm only if installing it using rpm or using yum outside of a repo. Once it is installed the name you need to use to do things with it is just "Percona-Server-shared-56".

[wilburunion]

Ok thanks . . . it did not occur to me it was a package name issue . . . I searched the issue of rpm and name and found the command line usage is " rpm -qi <package> " for installed packages for my future use - or others who come by with the same question and for non-installed rpm is " rpm -qipl <rpm_name.rpm> " (including as a link to the rpm) will give the info including the proper name and files of it