Red Hat Bugzilla – Bug 475619
[LTC 5.4 FEAT] libspe2 and elfspe2 maintenance from upstream 
Last modified: 2015-05-04 21:34:22 EDT
Emily J. Ratliff <firstname.lastname@example.org> -
1. Feature Overview:
Feature Id: 
a. Name of Feature: libspe2 and elfspe2 maintenance from upstream
b. Feature Description
Update the SPE Runtime Management Library libspe2 and elfspe2 in RHEL5.4 to the latest level made
available upstream at http://sourceforge.net/projects/libspe which is currently (as of 11/2008)
2. Feature Details:
Arch Specificity: Purely Arch Specific Code
Delivery Mechanism: Backport
Request Type: Package - Update Version
d. Upstream Acceptance: Accepted
Sponsor Priority 1
f. Severity: High
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: http://sourceforge.net/projects/libspe
3. Business Case
Maintain currency and include fixes and updates for libspe2 and elfspe2 to improve customer experience.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Hanns-Joachim Uhl, email@example.com, 49-7031-16-4198
Hanns-Joachim Uhl, firstname.lastname@example.org
IBM is signed up to test and provide feedback.
Hello Red Hat,
with the code due date for RHEL5.4 at 1/26 in mind I would like to ask you for your advise
whether you plan to update the libspe2 and elfspe2 package directly from upstream (as originally requested in this RHEL5.4 feature request) or whether we should provide you a patch which upgrades the libspe2 and elfspe2 packages as contaiend in RHEL5.3 to the upstream level ...
... please advise.
Thanks for your support.
Whichever method is fine by me, there's really no difference packaging-wise, compatibility concerns are the same, etc. I can rebase easily given the three acks get resolved. The 26/1 deadline is related to scoping phase, acks will appear after that. I will fetch the latest code that you have upstream when I do the packaging.
thanks for the quick response ..
... yes, please fetch the most current code from upstream and please keep us informed in case of any question.
Thanks for your support.
fyi ... the most current -135 version of libspe2 can be downloaded from
Thanks for your support.
This enhancement request was evaluated by the full Red Hat Enterprise Linux
team for inclusion in a Red Hat Enterprise Linux minor release. As a
result of this evaluation, Red Hat has tentatively approved inclusion of
this feature in the next Red Hat Enterprise Linux Update minor release.
While it is a goal to include this enhancement in the next minor release
of Red Hat Enterprise Linux, the enhancement is not yet committed for
inclusion in the next minor release pending the next phase of actual
code integration and successful Red Hat and partner testing.
~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~
RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should
be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner!
If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks!
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
SPE Runtime Management Libraries were updated to latest available upstream release. Updated package includes fixes, enhancements, and ADA programming language bindings.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
------- Comment From email@example.com 2009-07-09 04:37 EDT-------
Verified in RHEL 5.4 Beta .. closing Bugzilla
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.