Red Hat Bugzilla – Bug 200332
Need the 1.4.2_11 version of the SDK
Last modified: 2007-11-30 17:07:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20060313 Fedora/22.214.171.124-9 Firefox/126.96.36.199
Description of problem:
Our JBoss division is already building and testing with BEA 1.4.2_11 and the latest one we have is 1.4.2_08. We need the newer 1.4.2_11 to go with our next JBoss release (which is being built and tested with it), so we need to make sure it is in our next Update batch ans also need it in advance so we can test with the same version.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the latest java-1.4.2-bea from the LACD channel
Re-assigning to Georges. Georges, any chance we can get a new 1.4.2_11 SRPM
from BEA ASAP?
It will take us a couple of weeks before we can get to producing SRPMs for this
because of conflicts with work the engineer who does this has which are on the
critical path for our next release.
If you would prefer, we can get you the the payload portion quickly, which
you can use to replace the previous payload for a new SRPM yourself.
Let me know what your preference is!
(In reply to comment #2)
> Let me know what your preference is!
Please send the payload portion on its own. We need this fix ASAP.
Fernando and Tom, let's take the upload offline in normal Red Hat / BEA forums.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Yes, we can do this one. Please devel_ack.
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 the 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.