Red Hat ENTERPRISE LINUX 5 - DEPLOYMENT Deployment Manual page 149

Preparing...
1:foo
As you can see, RPM prints out the name of the package and then prints a succession of hash marks
as a progress meter while the package is installed.
The signature of a package is checked automatically when installing or upgrading a package. The
signature confirms that the package was signed by an authorized party. For example, if the verification
of the signature fails, an error message such as the following is displayed:
error: V3 DSA signature: BAD, key ID 0352860f
If it is a new, header-only, signature, an error message such as the following is displayed:
error: Header V3 DSA signature: BAD, key ID 0352860f
If you do not have the appropriate key installed to verify the signature, the message contains the word
NOKEY such as:
warning: V3 DSA signature: NOKEY, key ID 0352860f
Section 10.3, "Checking a Package's Signature"
Refer to
package's signature.
Warning
If you are installing a kernel package, you should use rpm -ivh instead. Refer to
Chapter 40, Manually Upgrading the Kernel
10.2.2.1. Package Already Installed
If a package of the same name and version is already installed, the following output is displayed:
Preparing...
package foo-1.0-1 is already installed
However, if you want to install the package anyway, you can use the --replacepkgs option, which
tells RPM to ignore the error:
rpm -ivh --replacepkgs foo-1.0-1.i386.rpm
This option is helpful if files installed from the RPM were deleted or if you want the original
configuration files from the RPM to be installed.
10.2.2.2. Conflicting Files
If you attempt to install a package that contains a file which has already been installed by another
package, the following is displayed:
########################################### [100%]
########################################### [100%]
########################################### [100%]
for more information on checking a
for details.
Installing
123