Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Tank you for your report. The ruby-lib.e686 are not in best condition. This reminds me bug #624029.
However, could you please enlighten me why do you need ruby-libs.i686 on you machine at all?
Looks that this problem appears when somebody tries to build 32b and 64b versions of subversion in one buildroot. So the workaround is to build them independently.
Comment 5Marcela Mašláňová
2011-02-04 09:54:53 UTC
This will be postponed into next minor release, because the solution was not tested yet.
Comment 6Jaroslav Škarvada
2011-02-04 13:09:52 UTC
Created attachment 477001[details]
libdir fix
It seems to be a problem in wrong libdir path. The attached patch solved the problem for me.
Comment 7Jaroslav Škarvada
2011-02-07 08:14:18 UTC
Comment on attachment 477001[details]
libdir fix
The proposed patch installs noarch files twice in multilib - this is not optimal. Probably better to use the patch from bug 624029, comment 7 which also worked for me.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1581.html
Description: # yum install ruby ruby-devel ... Installed: ruby.x86_64 0:1.8.7.299-5.el6_0.1 ruby-devel.x86_64 0:1.8.7.299-5.el6_0.1 Dependency Installed: ruby-libs.x86_64 0:1.8.7.299-5.el6_0.1 # ruby -r mkmf -e 'exit(have_func("rb_hash_foreach") ? 0 : 1)' checking for rb_hash_foreach()... yes # yum install ruby-libs.i686 ... Installed: ruby-libs.i686 0:1.8.7.299-5.el6_0.1 # ruby -r mkmf -e 'exit(have_func("rb_hash_foreach") ? 0 : 1)' mkmf.rb can't find header files for ruby at /usr/lib/ruby/ruby.h The subversion build relies on this, and it is breaking if the 32-bit ruby-libs is installed on a 64-bit machine. s390/s390x is showing the same issue.