This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2223700 - ruby:3.1/rubygem-irb: IRB has hard dependency on rubygem-rdoc [RHEL 8]
Summary: ruby:3.1/rubygem-irb: IRB has hard dependency on rubygem-rdoc [RHEL 8]
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ruby
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: ruby maint
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 14:23 UTC by Jarek Prokop
Modified: 2023-09-20 18:14 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2223704 (view as bug list)
Environment:
Last Closed: 2023-09-20 18:14:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5615 0 None Migrated None 2023-09-20 18:11:52 UTC
Red Hat Issue Tracker RHELPLAN-162617 0 None None None 2023-07-18 14:25:37 UTC

Description Jarek Prokop 2023-07-18 14:23:09 UTC 
Description of problem:
The IRB console throws error when run without rubygem-rdoc installed.

This is not correct, rubygem IRB should not have a hard dependency on RDoc.

Version-Release number of selected component (if applicable):
rubygem-irb-1.4.1-141.module+el8.7.0+15051+29b42f0c

How reproducible:
always

Steps to Reproduce:
1. dnf module enable ruby:3.1-y
2. dnf --setopt=install_weak_deps=False install -y rubygem-irb
(rubygem-rdoc gets pulled in via weak dependencies by default.)
3. echo '' | irb
(  ^ this allows for automated running in e.g. scripts.)

Actual results:
~~~
$ echo '' | irb
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- rdoc (LoadError)
	from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from /usr/share/gems/gems/irb-1.4.1/lib/irb/input-method.rb:17:in `<top (required)>'
	from /usr/share/gems/gems/irb-1.4.1/lib/irb/context.rb:14:in `require_relative'
	from /usr/share/gems/gems/irb-1.4.1/lib/irb/context.rb:14:in `<top (required)>'
	from /usr/share/gems/gems/irb-1.4.1/lib/irb.rb:16:in `require_relative'
	from /usr/share/gems/gems/irb-1.4.1/lib/irb.rb:16:in `<top (required)>'
	from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from /usr/share/gems/gems/irb-1.4.1/exe/irb:9:in `<top (required)>'
	from /usr/bin/irb:25:in `load'
	from /usr/bin/irb:25:in `<main>'
~~~

Expected results:
No error
~~~
$ echo '' | irb
Switch to inspect mode.


~~~

Additional info:
Reported upstream some while back https://github.com/ruby/irb/issues/342
Upstream resolved via:
https://github.com/ruby/irb/commit/54c8df06ff9e161012f89d19a4e3aa2e0e37e1b0
https://github.com/ruby/irb/commit/b24852058fc87c940252c8a711c60ae2eb298082

Fedora's Ruby 3.1 fixed it via these commit that include upstream changes to drop the hard dependency inside IRB:
https://src.fedoraproject.org/rpms/ruby/c/3f106c188ea6368c950ba7d610594f910773a25f?branch=f37
https://src.fedoraproject.org/rpms/ruby/c/bf921512e288965724353ecf73ca9aa6d4975489?branch=f37
Comment 1 RHEL Program Management 2023-09-20 18:09:02 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2 RHEL Program Management 2023-09-20 18:14:10 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.