Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 450915 - New libsdp missing Epoch info
Summary: New libsdp missing Epoch info
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openib
Version: 4.7
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Doug Ledford
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-11 18:02 UTC by Doug Ledford
Modified: 2008-07-24 19:59 UTC (History)
2 users (show)

Fixed In Version: RHEA-2008-0737
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-24 19:59:19 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2008:0737 normal SHIPPED_LIVE openib enhancement and bug fix update 2008-07-24 13:56:22 UTC

Description Doug Ledford 2008-06-11 18:02:04 UTC
+++ This bug was initially created as a clone of Bug #448733 +++

Description of problem:
The libsdp package from RHEL 5.2 (libsdp-1.1.99-9.el5) is "older" then the old
libsdp-1.1.99-6.el5_1.1 due to epoch being set to 1 in the old package (and
missing in the new one).

Version-Release number of selected component (if applicable):
libsdp-1.1.99-9.el5 and libsdp-1.1.99-6.el5_1.1

How reproducible:
Cannot update to new one due to epoch issues.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Solution - add Epoch:1 to libsdp-1.1.99-9.el5 and rebuild.

The same problem exists on the upcoming rhel4.7 libsdp, we need to build a new
one for the errata.  This bug is for that purpose.

Comment 6 errata-xmlrpc 2008-07-24 19:59:19 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.

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