Bug 1368657

Summary: jboss-logmanager: Update to 2.0.4.Final
Product: [Fedora] Fedora Reporter: gil cattaneo <puntogil>
Component: jboss-logmanagerAssignee: Marek Goldmann <mgoldman>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: java-sig-commits, mgoldman, puntogil
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: jboss-logmanager-2.0.4-1.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-12 13:21:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1181081    

Description gil cattaneo 2016-08-20 12:38:29 UTC
Latest upstream release: 2.0.4.Final
Current version/release in rawhide: 2.0.3-2.fc25
URL: https://github.com/jbossas/jboss-vfs/tags

Required by wildfly 10+

Comment 1 gil cattaneo 2016-08-20 12:44:27 UTC
URL: https://github.com/jboss-logging/jboss-logmanager/tags

Comment 2 Fedora Update System 2016-09-07 10:50:58 UTC
jboss-logmanager-2.0.4-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4600439251

Comment 3 Fedora Update System 2016-09-09 06:28:46 UTC
jboss-logmanager-2.0.4-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4600439251

Comment 4 Fedora Update System 2016-09-12 13:21:37 UTC
jboss-logmanager-2.0.4-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.