Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 453913

Summary:	unixODBC-devel-2.2.11-1.RHEL4.1.ppc64.rpm signed with redhat-beta key
Product:	Red Hat Enterprise Linux 4	Reporter:	Alexander Todorov <atodorov>
Component:	redhat-release	Assignee:	Daniel Mach <dmach>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	4.7	CC:	dmach
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHEA-2008-0769	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-24 20:04:45 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 Alexander Todorov 2008-07-03 07:57:23 UTC

Description of problem:
package unixODBC-devel-2.2.11-1.RHEL4.1.ppc64.rpm signed with redhat-beta key
while it should not be.

Version-Release number of selected component (if applicable):
RHEL4-U7-re20080702.0

How reproducible:
Always

Comment 2 Alexander Todorov 2008-07-03 07:59:16 UTC

Tom, Daniel,
please advise which is the proper component to use for this issue. It's clearly
a problem with rel-eng not development.

Comment 3 Daniel Mach 2008-07-03 08:15:52 UTC

I think that releng component is the right place for such issues.
Reassigining to myself.

This package is inherited from rhel-4.3 and that rpm has never been signed with
gold key.
Now it's fixed for next compose.

Comment 8 errata-xmlrpc 2008-07-24 20:04:45 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2008-0769.html