Bug 1289004 - epel7 qt5-qtconfiguration fails to rebuild
Summary: epel7 qt5-qtconfiguration fails to rebuild
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: qt5-qtconfiguration
Version: epel7
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7aarch64
TreeView+ depends on / blocked
 
Reported: 2015-12-07 08:27 UTC by Yaakov Selkowitz
Modified: 2016-06-13 13:21 UTC (History)
8 users (show)

Fixed In Version: qt5-qtconfiguration-0.3.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 16:20:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Yaakov Selkowitz 2015-12-07 08:27:30 UTC 
epel7 qt5-* have been upgraded to 5.5, but qt5-qtconfiguration-0.3.0-2.el7 fails to compile with that version of Qt5.  It would seem a rebase is in order to 0.3.1 as in f22+.
Comment 1 Than Ngo 2015-12-07 12:21:21 UTC 
it's fixed in qt5-qtconfiguration-0.3.0-3.el7
Comment 2 Fedora Update System 2015-12-07 12:46:54 UTC 
qt5-qtconfiguration-0.3.0-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-354457e768
Comment 3 Fedora Update System 2015-12-08 07:21:12 UTC 
qt5-qtconfiguration-0.3.0-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'yum --enablerepo=epel-testing update qt5-qtconfiguration'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-354457e768
Comment 4 Yaakov Selkowitz 2016-05-16 20:48:26 UTC 
Any reason this can't be pushed to stable?
Comment 5 Fedora Update System 2016-05-19 16:20:54 UTC 
qt5-qtconfiguration-0.3.0-3.el7 has been pushed to the Fedora EPEL 7 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.