Bug 1271235 - [epel7s390x] rubygem-eventmachine SRPM does not build correctly on s390x
Summary: [epel7s390x] rubygem-eventmachine SRPM does not build correctly on s390x
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-eventmachine
Version: epel7
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7s390x
TreeView+ depends on / blocked
 
Reported: 2015-10-13 12:51 UTC by IBM Bug Proxy
Modified: 2020-04-14 11:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 11:04:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
rubygem-eventmachine_build_log (37.68 KB, text/plain)
2015-10-13 12:52 UTC, IBM Bug Proxy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 131677 0 None None None 2019-02-21 09:28:17 UTC

Description IBM Bug Proxy 2015-10-13 12:51:57 UTC
Comment 1 IBM Bug Proxy 2015-10-13 12:51:59 UTC 
The EPEL 7 SRPM for rubygem-eventmachine 
https://dl.fedoraproject.org/pub/epel/7/SRPMS/r/rubygem-eventmachine-1.0.6-2.el7.src.rpm
does not build correctly on Mock on s390x. 

The error message when trying to build using mock:

/builddir/build/BUILD/rubygem-eventmachine-1.0.6/usr/share/gems/gems/eventmachine-1.0.6/tests/test_pool.rb:1:in `<top (required)>': uninitialized constant Test (NameError)
        from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
        from -e:1:in `glob'
        from -e:1:in `<main>'
Comment 2 IBM Bug Proxy 2015-10-13 12:52:04 UTC 
Created attachment 1082409 [details]
rubygem-eventmachine_build_log
Comment 3 IBM Bug Proxy 2020-04-14 08:01:47 UTC 
------- Comment From tstaudt.com 2020-04-14 03:51 EDT-------
With no activity in this bug for years, I'm now closing this on the IBM side.
If the problem still needs to be addressed, please re-open or preferably open a new bug.

Thanks.
Note You need to log in before you can comment on or make changes to this bug.