Bug 135658
Summary: | error: V3 DSA signature: BAD, key ID db42a60e | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Muralidharan <lidhar2k1> |
Component: | rpmdb-redhat | Assignee: | Tim Powers <timp> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | shillman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-15 14:28:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Muralidharan
2004-10-14 06:25:41 UTC
Where did the glibc-debug rpm come from? It might really be that the signature is bad. You need to make sure that you have the gpg keys imported into RPM that the package is signed with. The GPG signatures are located on disc1, and can be imported by invoking: rpm --import <gpg-key> |