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:
User-installed rubygems plugins are not being loaded correctly.
Version-Release number of selected component (if applicable):
ruby-3.0.{0,1,2}
How reproducible:
Always
Steps to Reproduce:
1. gem install geminabox --user-install
2. gem inabox --help
Actual results:
~~~
$ gem inabox --help
ERROR: While executing gem ... (Gem::CommandLineError)
Unknown command inabox
~~~
Expected results:
~~~
$ gem inabox --help
Usage: gem inabox GEM [options]
Options:
-c, --configure Configure GemInABox
-g, --host HOST Host to upload to.
-o, --overwrite Overwrite Gem.
-p, --port Sets port
Common Options:
-h, --help Get help on this command
-V, --[no-]verbose Set the verbose level of output
-q, --quiet Silence command progress meter
--silent Silence RubyGems output
--config-file FILE Use this config file instead of default
--backtrace Show stack backtrace on errors
--debug Turn on Ruby debugging
--norc Avoid loading any .gemrc file
Arguments:
GEM built gem to push up
Summary:
Push a gem up to your GemInABox
Description:
Push a gem up to your GemInABox
~~~
Additional info:
A possible workaround is pre-loading the gem, like so
`$ RUBYOPT=-r<gem> gem <command>`
Or specifying $GEM_HOME:
`$ GEM_HOME=/builddir/.local/share/gem/ruby/3.0.0 gem <command>`
The issue was fixed upstream: https://github.com/rubygems/rubygems/pull/4829
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 (new packages: ruby), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2637
Description of problem: User-installed rubygems plugins are not being loaded correctly. Version-Release number of selected component (if applicable): ruby-3.0.{0,1,2} How reproducible: Always Steps to Reproduce: 1. gem install geminabox --user-install 2. gem inabox --help Actual results: ~~~ $ gem inabox --help ERROR: While executing gem ... (Gem::CommandLineError) Unknown command inabox ~~~ Expected results: ~~~ $ gem inabox --help Usage: gem inabox GEM [options] Options: -c, --configure Configure GemInABox -g, --host HOST Host to upload to. -o, --overwrite Overwrite Gem. -p, --port Sets port Common Options: -h, --help Get help on this command -V, --[no-]verbose Set the verbose level of output -q, --quiet Silence command progress meter --silent Silence RubyGems output --config-file FILE Use this config file instead of default --backtrace Show stack backtrace on errors --debug Turn on Ruby debugging --norc Avoid loading any .gemrc file Arguments: GEM built gem to push up Summary: Push a gem up to your GemInABox Description: Push a gem up to your GemInABox ~~~ Additional info: A possible workaround is pre-loading the gem, like so `$ RUBYOPT=-r<gem> gem <command>` Or specifying $GEM_HOME: `$ GEM_HOME=/builddir/.local/share/gem/ruby/3.0.0 gem <command>` The issue was fixed upstream: https://github.com/rubygems/rubygems/pull/4829