Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2027099 - Fedora/Rawhide Ruby: Running rubygem-irb in CLI fails with "Could not find 'reline'"
Summary: Fedora/Rawhide Ruby: Running rubygem-irb in CLI fails with "Could not find 'r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2028199 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-28 11:56 UTC by Jarek Prokop
Modified: 2022-05-08 02:01 UTC (History)
11 users (show)

Fixed In Version: ruby-3.0.3-155.fc36 ruby-3.0.4-153.fc35 ruby-3.0.4-153.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-10 18:06:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rubygems rubygems issues 5156 0 None open Default gems on Fedora are not loaded anymore 2021-12-09 16:25:38 UTC

Description Jarek Prokop 2021-11-28 11:56:23 UTC 
Description of problem:
The package ruby-3.0.3-154 does not have a working IRB gem.

Version-Release number of selected component (if applicable):
rubygem-irb-1.3.5-154.fc36.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install the newest ruby and rubygem-irb.
2. run in the shell:
~~~
$ irb
~~~

Actual results:
Fail:

~~~
/usr/share/rubygems/rubygems/specification.rb:1402:in `rescue in block in activate_dependencies': Could not find 'reline' (>= 0.1.5) among 7 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/root/.local/share/gem/ruby:/usr/share/gems:/usr/local/share/gems' at: /usr/share/gems/specifications/irb-1.3.5.gemspec, execute `gem env` for more information
	from /usr/share/rubygems/rubygems/specification.rb:1399:in `block in activate_dependencies'
	from /usr/share/rubygems/rubygems/specification.rb:1388:in `each'
	from /usr/share/rubygems/rubygems/specification.rb:1388:in `activate_dependencies'
	from /usr/share/rubygems/rubygems/specification.rb:1370:in `activate'
	from /usr/share/rubygems/rubygems.rb:299:in `block in activate_bin_path'
	from /usr/share/rubygems/rubygems.rb:298:in `synchronize'
	from /usr/share/rubygems/rubygems.rb:298:in `activate_bin_path'
	from /usr/bin/irb:23:in `<main>'
/usr/share/rubygems/rubygems/dependency.rb:311:in `to_specs': Could not find 'reline' (>= 0.1.5) among 7 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/root/.local/share/gem/ruby:/usr/share/gems:/usr/local/share/gems' , execute `gem env` for more information
	from /usr/share/rubygems/rubygems/specification.rb:1400:in `block in activate_dependencies'
	from /usr/share/rubygems/rubygems/specification.rb:1388:in `each'
	from /usr/share/rubygems/rubygems/specification.rb:1388:in `activate_dependencies'
	from /usr/share/rubygems/rubygems/specification.rb:1370:in `activate'
	from /usr/share/rubygems/rubygems.rb:299:in `block in activate_bin_path'
	from /usr/share/rubygems/rubygems.rb:298:in `synchronize'
	from /usr/share/rubygems/rubygems.rb:298:in `activate_bin_path'
	from /usr/bin/irb:23:in `<main>'
~~~

Expected results:
The IRB launches:

~~~
irb(main):001:0>
~~~

Additional info:
If I load the IRB from a script like so:

~~~
$ ruby -e 'require "irb"; binding.irb'
~~~

instead of calling it through the shell, it works, so there seems to be some problem with the code in the bin script.
Comment 1 Vít Ondruch 2021-12-09 16:25:38 UTC 
I have reported this upstream:

https://github.com/rubygems/rubygems/issues/5156

And I'll try to revert this PR:

https://github.com/rubygems/rubygems/pull/5044
Comment 2 Vít Ondruch 2021-12-09 16:57:38 UTC 
*** Bug 2028199 has been marked as a duplicate of this bug. ***
Comment 3 Fedora Update System 2021-12-10 18:05:02 UTC 
FEDORA-2021-62cd39359e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-62cd39359e
Comment 4 Fedora Update System 2021-12-10 18:06:06 UTC 
FEDORA-2021-62cd39359e has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 5 Fedora Update System 2022-04-27 11:48:38 UTC 
FEDORA-2022-8cf0124add has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8cf0124add
Comment 6 Fedora Update System 2022-04-27 11:55:20 UTC 
FEDORA-2022-82a9edac27 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-82a9edac27
Comment 7 Fedora Update System 2022-04-28 06:09:41 UTC 
FEDORA-2022-8cf0124add has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8cf0124add`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8cf0124add

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2022-04-28 06:29:02 UTC 
FEDORA-2022-82a9edac27 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-82a9edac27`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-82a9edac27

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2022-05-08 01:45:40 UTC 
FEDORA-2022-8cf0124add has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 10 Fedora Update System 2022-05-08 02:01:26 UTC 
FEDORA-2022-82a9edac27 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.