Bug 1305292 - Fix rawhide build error and update memkind to upstream 0.3.0 latest patches
Summary: Fix rawhide build error and update memkind to upstream 0.3.0 latest patches
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: memkind
Version: rawhide
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Rafael Aquini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1282868
Blocks: 1305355 1305359 1305360 1305361
TreeView+ depends on / blocked
 
Reported: 2016-02-06 19:19 UTC by Rafael Aquini
Modified: 2016-02-23 01:25 UTC (History)
2 users (show)

Fixed In Version: memkind-0.3.0-5.fc24 memkind-0.3.0-5.el7 memkind-0.3.0-5.fc23
Clone Of: 1282868
: 1305355 (view as bug list)
Environment:
Last Closed: 2016-02-22 23:58:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Rafael Aquini 2016-02-06 19:19:35 UTC 
memkind  RPM is failing to build on fc24 with GCC 6: 
http://koji.fedoraproject.org/koji/taskinfo?taskID=12843129
Comment 1 Rafael Aquini 2016-02-06 19:21:21 UTC 
http://koji.fedoraproject.org/koji/buildinfo?buildID=733775
Comment 2 Fedora Update System 2016-02-06 19:29:53 UTC 
memkind-0.3.0-4.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-04c59dd6db
Comment 3 Fedora Update System 2016-02-06 19:40:21 UTC 
memkind-0.3.0-4.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5e1ff16b1d
Comment 4 Fedora Update System 2016-02-07 06:53:53 UTC 
memkind-0.3.0-4.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2016-5e1ff16b1d
Comment 5 Fedora Update System 2016-02-07 07:22:21 UTC 
memkind-0.3.0-4.fc23 has been pushed to the Fedora 23 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-04c59dd6db
Comment 6 Fedora Update System 2016-02-07 15:31:17 UTC 
memkind-0.3.0-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-d2be268902
Comment 7 Fedora Update System 2016-02-07 15:41:13 UTC 
memkind-0.3.0-5.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e54be2efdf
Comment 8 Rafael Aquini 2016-02-07 15:54:27 UTC 
http://koji.fedoraproject.org/koji/buildinfo?buildID=733890
Comment 9 Fedora Update System 2016-02-08 03:48:37 UTC 
memkind-0.3.0-5.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2016-d2be268902
Comment 10 Fedora Update System 2016-02-08 04:19:55 UTC 
memkind-0.3.0-5.fc23 has been pushed to the Fedora 23 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-e54be2efdf
Comment 11 Fedora Update System 2016-02-22 23:57:56 UTC 
memkind-0.3.0-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
Comment 12 Fedora Update System 2016-02-23 01:25:04 UTC 
memkind-0.3.0-5.fc23 has been pushed to the Fedora 23 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.