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.
Description of problem:
ruby193-ruby has packaging issues. According the the errata tool, versions should be specified on a Requires. For example:
ruby193-ruby-devel - Subpackage ruby193-ruby-devel on i686 consumes library libruby.so.1.9 from subpackage ruby193-ruby-libs but does not have explicit package version requirement.<br/>Please add Requires: ruby193-ruby-libs = %{version}-%{release} to ruby193-ruby-devel in the specfile to avoid the need to test interoperability between the various combinations of old and new subpackages.
Version-Release number of selected component (if applicable):
ruby193-ruby-1.9.3.194-23.el6
https://errata.devel.redhat.com/rpmdiff/show/69324?result_id=1366705
Judging from brew, bkabrda is the one who does all the ruby193 builds.
Comment 7Bohuslav "Slavek" Kabrda
2012-11-05 07:43:47 UTC
Yes, I'm the maintainer of this package, thanks for reporting.
I see where this problem may show up. Note however, that for some of the mentioned subpackages, this is not true - for example ruby193-ruby-devel has:
Requires: %{?scl_prefix}%{pkg_name}%{?_isa} = %{version}-%{release}
and %{?scl_prefix}%{pkg_name}%{?_isa} (which is ruby193-ruby) has:
Requires: %{?scl_prefix}%{pkg_name}-libs%{?_isa} = %{version}-%{release}
so transitively, ruby-devel has the right require.
I will add the proper Requires during next update of the package, it that's ok (ruby193 SCL doesn't have any real releases or associated product right now, so I'm not sure how that will work with the 3ack procedure etc...)
Description of problem: ruby193-ruby has packaging issues. According the the errata tool, versions should be specified on a Requires. For example: ruby193-ruby-devel - Subpackage ruby193-ruby-devel on i686 consumes library libruby.so.1.9 from subpackage ruby193-ruby-libs but does not have explicit package version requirement.<br/>Please add Requires: ruby193-ruby-libs = %{version}-%{release} to ruby193-ruby-devel in the specfile to avoid the need to test interoperability between the various combinations of old and new subpackages. Version-Release number of selected component (if applicable): ruby193-ruby-1.9.3.194-23.el6 https://errata.devel.redhat.com/rpmdiff/show/69324?result_id=1366705