Add -- force -- nodeps, as shown in figure
# Rpm-IVH db4-devel-4.3.29-9.fc6.i386.rpm -- force -- nodeps
This is a strange thing. Previously, RPM files that can be directly installed in the system cannot be installed now. You can double-click them to run them. It will automatically return after waiting for a while.
Come out, so I still come to the terminal to check it!
Rpm-IVH *. rpm
The result is: V3 DSA Signature: Bad, key ID ....
Package *. rpm is not installed
Short Message notification reviewer
It turns out that some of the queries on the Internet are incorrect and need to be re-downloaded. However, it is depressing that the software of the last system is good. How can this happen?
What about the subverification error?
Finally, I saw another method on the Internet: the error solution is to add -- force -- nodeps after the RPM command, that is, force installation.
I have not tried it yet. I don't know if it is useful. I have used it before ....
I tried it when I got home from work, but it still didn't work. It was the same mistake. Later I saw something like this on a website:
Starting from rpm version 4.1, the software package signature is checked during installation or upgrade. If the signature verification fails, you will see the following:
Error message:
Error: V3 DSA Signature: Bad, key ID 0352860f
If it is a new signature only for the file header, you will see the following error message:
Error: Header V3 DSA Signature: Bad, key ID 0352860f
If you do not install a proper key to verify the signature, the message will contain nokey, for example:
Warning: V3 DSA Signature: nokey, key ID 0352860f
When you use Yum to install software in centos, the following message is displayed:
Reference
Warning: rpmts_hdrfromfdno: Header V3 DSA Signature: nokey, key ID *****
This is because the old version of GPG keys is installed in yum. The solution is
Reference
Rpm -- import/etc/pki/rpm-GPG/RPM *
If you install the software again, this error will not be prompted.