Bug 1271235
| Summary: | [epel7s390x] rubygem-eventmachine SRPM does not build correctly on s390x | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | IBM Bug Proxy <bugproxy> | ||||
| Component: | rubygem-eventmachine | Assignee: | Nobody's working on this, feel free to take it <nobody> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | epel7 | CC: | dan, dhorak, hannsj_uhl, jkachuck, mastahnke | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | s390x | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-04-14 11:04:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1267648 | ||||||
| Attachments: |
|
||||||
|
Description
IBM Bug Proxy
2015-10-13 12:51:57 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>' Created attachment 1082409 [details]
rubygem-eventmachine_build_log
------- 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. |