Bug 1288278

Summary: dragonegg needs to be updated for new GCC in EL 7.2
Product: [Fedora] Fedora EPEL Reporter: Anssi Johansson <rhbugs>
Component: dragoneggAssignee: Eric Smith <spacewar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: jakub, spacewar, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-04 15:47:44 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:

Description Anssi Johansson 2015-12-04 01:14:26 UTC
Description of problem:
dragonegg requires gcc 4.8.3-9.el7, but the gcc in RHEL 7.2 is 4.8.5-4.el7. 

Version-Release number of selected component (if applicable):
3.4-4.el7

Steps to Reproduce:
1. Upgrade to RHEL 7.2
2. yum install dragonegg

Actual results:
See yum complain about a missing dependency

Expected results:
dragonegg gets installed

Additional info:
EPEL7's builders have already been updated to RHEL 7.2.

Comment 1 Anssi Johansson 2018-08-22 14:58:23 UTC
Ping?

Comment 2 Fedora Update System 2018-08-22 17:25:17 UTC
dragonegg-3.4-6.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2431df82d2

Comment 3 Fedora Update System 2018-08-23 10:07:00 UTC
dragonegg-3.4-6.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-2018-2431df82d2

Comment 4 Troy Dawson 2019-04-04 15:47:44 UTC

*** This bug has been marked as a duplicate of bug 1696360 ***