Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1279213 - epel7 dragonegg SRPM needs to exclude s390x, aarch64
Summary: epel7 dragonegg SRPM needs to exclude s390x, aarch64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: dragonegg
Version: epel7
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Eric Smith
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7s390x epel7aarch64
TreeView+ depends on / blocked
 
Reported: 2015-11-08 16:11 UTC by IBM Bug Proxy
Modified: 2015-12-26 23:24 UTC (History)
7 users (show)

Fixed In Version: dragonegg-3.4-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-26 23:24:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 132869 0 None None None Never

Description IBM Bug Proxy 2015-11-08 16:11:45 UTC
Comment 1 IBM Bug Proxy 2015-11-08 16:11:48 UTC 
The EPEL 7 SRPM for dragonegg 
https://dl.fedoraproject.org/pub/epel/7/SRPMS/d/dragonegg-3.4-4.el7.src.rpm
contains CPU architecture specific code and therefore cannot be built on Mock on s390x.

s390x needs to be listed in "ExcludeArch" in spec file.
Comment 2 Yaakov Selkowitz 2015-12-01 03:18:33 UTC 
Same for aarch64; this should probably be ExclusiveArch whichever architectures it actually works on.
Comment 3 Fedora Update System 2015-12-15 12:58:42 UTC 
dragonegg-3.4-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-a6569ea17b
Comment 4 Fedora Update System 2015-12-26 23:24:24 UTC 
dragonegg-3.4-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.
Note You need to log in before you can comment on or make changes to this bug.