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 2000056 - ruby 3.0: User-installed rubygems plugins are not being loaded [RHEL8]
Summary: ruby 3.0: User-installed rubygems plugins are not being loaded [RHEL8]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ruby
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jarek Prokop
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On: 2096346
Blocks: 2110981
TreeView+ depends on / blocked
 
Reported: 2021-09-01 09:42 UTC by Jarek Prokop
Modified: 2023-08-21 15:01 UTC (History)
0 users

Fixed In Version: ruby-3.0-8060020220810162001.ad008a3a
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2110981 (view as bug list)
Environment:
Last Closed: 2023-08-21 14:58:56 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 RHELPLAN-95853 0 None None None 2022-10-03 16:57:09 UTC

Description Jarek Prokop 2021-09-01 09:42:49 UTC
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


Note You need to log in before you can comment on or make changes to this bug.