Bug 453913 - unixODBC-devel-2.2.11-1.RHEL4.1.ppc64.rpm signed with redhat-beta key
unixODBC-devel-2.2.11-1.RHEL4.1.ppc64.rpm signed with redhat-beta key
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: redhat-release (Show other bugs)
4.7
All Linux
low Severity low
: rc
: ---
Assigned To: Daniel Mach
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-03 03:57 EDT by Alexander Todorov
Modified: 2008-07-24 16:04 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHEA-2008-0769
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-24 16:04:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2008-07-03 03:57:23 EDT
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 03:59:16 EDT
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 04:15:52 EDT
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 16:04:45 EDT
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

Note You need to log in before you can comment on or make changes to this bug.