Bug 852359 - Updated to upstream version 1.7.1
Summary: Updated to upstream version 1.7.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: stax-ex
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Juan Hernández
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 865787
TreeView+ depends on / blocked
 
Reported: 2012-08-28 09:21 UTC by gil cattaneo
Modified: 2012-12-20 15:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-20 15:22:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Updated to upstream version 1.7.1 (2.27 KB, patch)
2012-08-28 09:21 UTC, gil cattaneo 		no flags Details | Diff
View All

Description gil cattaneo 2012-08-28 09:21:17 UTC 
Created attachment 607453 [details]
Updated to upstream version 1.7.1

Description of problem:
Updated to upstream version 1.7.1
Comment 1 Fedora Update System 2012-10-30 12:08:36 UTC 
stax-ex-1.7.1-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/stax-ex-1.7.1-2.fc17
Comment 2 Fedora Update System 2012-10-30 12:08:46 UTC 
stax-ex-1.7.1-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/stax-ex-1.7.1-2.fc18
Comment 3 Fedora Update System 2012-10-30 20:16:09 UTC 
Package stax-ex-1.7.1-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing stax-ex-1.7.1-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17262/stax-ex-1.7.1-2.fc18
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2012-12-20 15:22:30 UTC 
stax-ex-1.7.1-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.