Did these updates complete successfully?

Zembower, Kevin kzembowe at jhuccp.org
Thu Nov 20 12:23:19 CST 2008


A private correspondent suggested:
==========================================================
-----Original Message-----
Sent: Tuesday, November 18, 2008 10:58 AM
To: Zembower, Kevin
Subject: RE: Did these updates complete successfully?

No they didn't. Because the signature couldn't be verified, the action
was aborted.

You'll need to do an "rpm --import RPM-GPG-KEY-something.txt" first.
They key should be on Dell's repository. You could use the web interface
and your browser to get it, if needed.
==========================================================
I only found one RPM-GPG-KEY file on the repository, and it seemed to install correctly. However, it didn't seem to fix the problem:

-bash-3.00# rpm --import http://linux.dell.com/repo/firmware/RPM-GPG-KEY-fwupdate
-bash-3.00# up2date --update
http://linux.dell.com/repo/software/mirrors.pl?osname=el4&basearch=x86_64
using mirror: http://linux.dell.com/repo/community/content/el4-x86_64
<snip>
dell-dup-1.1.2-1.14.el4.noa ########################## Done.
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 1d4949e5
The package dell-dup-1.1.2-1.14.el4 is signed, but with an unknown GPG key. Aborting...
Package dell-dup-1.1.2-1.14.el4 has a unknown GPG signature.
 Aborting...
-bash-3.00#

Can anyone suggest anything else I might try?

Thanks, again, for your help and advice.

-Kevin




More information about the Linux-PowerEdge mailing list