Bug 184199
Summary: | It is not possible to build noarch ruby packages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Lutterkort <lutter> |
Component: | ruby | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED RAWHIDE | QA Contact: | Bill Huang <bhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | florin, hbrock, jos, mattdm, mitr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.8.4-6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-17 10:52:09 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: | 180066 |
Description
David Lutterkort
2006-03-07 05:24:01 UTC
Discussion about various ways to address this bug: https://www.redhat.com/archives/fedora-extras-list/2006-March/msg01264.html I'm working on this and just made a testing package. can you guys test it if it works/is buildable properly for any ruby packages? Testing packages are available on http://people.redhat.com/tagoh/ruby/. TIA (In reply to comment #0) > Also, $: probably needs to be initialized a little differently to ensure that > 64bit binaries receive preference over 32bit binaries on multilib. I believe the > following would be a better order: [ sitearchdir, sitelibdir, sitedir, archdir, > rubylibdir, "." ] I disagree. it will makes incompatible behavior between 32bit and 64bit. even if we change it for all archs, it's still incompatible between ours and upstream, and other distros too. I've put another testing package on the same place that includes adding the deprecated path to the search path, providing ruby(abi) etc. If there are any issues on this testing package, I'm planning to push it next Monday. Fixed in 1.8.4-6 |