Bug 1036920 - Please upgrade mxml to 2.7
Summary: Please upgrade mxml to 2.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mxml
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brendan Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 22:15 UTC by Kevin Fenzi
Modified: 2016-06-11 17:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-11 17:41:39 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Kevin Fenzi 2013-12-02 22:15:20 UTC 
Rawhide has 2.5 in it, and I need at least 2.6 for libnftables. 2.7 has been out since 2011 it looks like: 

http://www.msweet.org/projects.php?Z3

If you prefer I'm happy to do the update.
Comment 1 Brendan Jones 2013-12-04 16:35:44 UTC 
Done in rawhide, f20. No push to testing yet

http://koji.fedoraproject.org/koji/buildinfo?buildID=482686
http://koji.fedoraproject.org/koji/taskinfo?taskID=6256498

Do you need branches through f18?
Comment 2 Kevin Fenzi 2013-12-04 16:40:14 UTC 
Nope. Rawhide only. ;)
Comment 3 Brendan Jones 2013-12-04 16:53:47 UTC 
https://admin.fedoraproject.org/updates/mxml-2.7-1.fc20
Comment 4 Brendan Jones 2013-12-04 16:54:24 UTC 
No probelems, I will stop at f20
Comment 5 Robert Szalai 2014-03-30 13:34:56 UTC 
Better yet, please update to v2.8. This fixes a few more bugs and that would be vital. Thanks.
Comment 6 Jaroslav Reznik 2015-03-03 15:15:13 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 7 Kevin Fenzi 2016-06-11 17:41:39 UTC 
This happened a while back. ;) 

Please reopen if there's anything further to do.
Note You need to log in before you can comment on or make changes to this bug.