rpm insane?

[Mistoffeles]

Is rpm insane in RHEL5, or is it just me?

I downloaded and installed Bastille and the per-Curses module it needs, now I am getting this:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[root@asterix src]# rpm -i Bastille*
package Bastille-3.2.1-0.1.noarch is already installed
[root@asterix src]# rpm -q Bastille*
package Bastille-3.2.1-0.1.noarch.rpm is not installed
[root@asterix src]#

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Is it wrong to be frustrated when rpm can't even agree with itself as to whether a package is installed or not?

[bigtomrodney]

When using rpm to query a package you must exclude the rpm extension, as you are searching for the package, not the file.

rpm -q Bastille-3.2.1-0.1

When you are installing, avoid installing rpm files directly. Always stick to your package manager, in this case Yum. That will manage dependencies and also retrieve applications directly for you saving you individual downloads and installing one package at a time.

[Mistoffeles]

If there was a Bastille package in the RHEL5 repositories, I surely would have used it, but there is not. My choice is to use rpm or source.

[daark.child]

What is the output of running

rpm -qa | grep -i bastille

Seems like you are using the wrong syntax to query for installed packages.

[Mistoffeles]

Seems like a bit of a waste to query for all packages then grep out the one desired, when the rpm program is perfectly capable of searching for a specific package on its own.

I any case, the point is moot, as Bastille is no longer being maintained and does not work properly post-RHEL 5.1, so I get to manually go through the CIS SCB. So much for having a fully functional Zimbra server by the weekend.

[HROAdmin26]

Please reread bigtomrodney's and daark.child's posts...

You have already installed the RPM, so that trying to install results in:

package Bastille-3.2.1-0.1.noarch is already installed

When you query, you need to specify the PACKAGE name, not some FILE name. You could have a file name of ricksappinstall.rpm and once installed, the RPM database knows this application as package bigappfrommars-4.1.5.

If you query RPM using ricksappinstall.rpm, you will not find the app.

Using -qa and grep -i is the best method when you do not know the *exact* package name as tracked by the RPM database. Assuming that "bastille" is somewhere in the package name, the best query has been pointed out by daark.child.

You would also likely find it with:

rpm -q bastille

Seems like a bit of a waste to query for all packages then grep out the one desired, when the rpm program is perfectly capable of searching for a specific package on its own.

Yes, and works just that way when used correctly.