Bug 1289748
Summary: | RHEL6 RPMs: Upgrade wss4j to 1.6.19.redhat-2 | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | nwallace <nwallace> |
Component: | RPMs | Assignee: | nwallace <nwallace> |
Status: | CLOSED ERRATA | QA Contact: | Katerina Odabasi <kanovotn> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4.6 | CC: | nwallace, pgier |
Target Milestone: | CR2 | Keywords: | Rebase |
Target Release: | EAP 6.4.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-04 21:50:26 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
nwallace
2015-12-08 21:17:47 UTC
Source URL: git://git.app.eng.bos.redhat.com/apache/wss4j.git#499953867095c0bd4fead423b1ac17da26bf6dc3 Mead-Build: org.apache.ws.security-wss4j-1.6.19.redhat_1-2 Brew-Build: wss4j-1.6.19-2.redhat_1.2.ep6.el6 Source URL: git://git.app.eng.bos.redhat.com/apache/wss4j.git#499953867095c0bd4fead423b1ac17da26bf6dc3 Mead-Build: org.apache.ws.security-wss4j-1.6.19.redhat_2-1 Brew-Build: wss4j-1.6.19-3.redhat_2.1.ep6.el6 Source URL: git://git.app.eng.bos.redhat.com/apache/wss4j.git#499953867095c0bd4fead423b1ac17da26bf6dc3 Mead-Build: org.apache.ws.security-wss4j-1.6.19.redhat_2-1 Brew-Build: wss4j-1.6.19-3.redhat_2.1.ep6.el6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-0122.html *** Bug 1289730 has been marked as a duplicate of this bug. *** |