Mike Corbeil wrote:
> You might also want to include -vv for extra verbostity in this
> --test, and you might want to run rpm -K or rpm -K --nopgpg
That's --nopgp instead of --nopgpg. Added the extra g unintentionally.
Try without --nopgpg, first. If it reports that no pgp key file is
available, then try with --nopgpg. ALSO, read the available documentation
on rpm related to pgp encryption, first, before installing anything with
rpm.
I downloaded many rpm packages to update or upgrade my RH 5.1 system, to
5.2, and some of the files obtained from the RH download ftp page had
Unknown signatures, which is considered problematic, at least potentially
dangerous.
You can and should read the rpm man page
% man rpm
and Linux Documentation Project documentation on rpm, to become familiar
with rpm and everything the version of rpm you have can do and all of the
options.
When you don't know a command, you should always check the man page or what
ever documentation is available for the command, before executing the
command. man pages, info pages, and Linux Documentation Project (LDP)
pages should always be verified, before doing anything, especially with
respect to adding or upgrading.
The person who told you to run
rpm -Uvh
on the .rpm package wasn't wrong. This will need to be done.
However, you should also always check and test rpm'ing, before actually
doing it or trying to do it. Do the --test and -K tests, first.
Caution, with respect to rpm, never costs more than seconds, usually just a
few.
mike
