Project

General

Profile

Actions

Bug #11971

closed

Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when both GEM_HOME and GEM_PATH has seted

Added by personnel (Am I Who) over 8 years ago. Updated over 8 years ago.

Status:
Third Party's Issue
Assignee:
-
Target version:
-
ruby -v:
ruby 2.3.0p0 (2015-12-25 revision 53290) [x64-mingw32]
[ruby-core:72783]

Description

Version: ruby 2.3.0 and gem 2.5.1

Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when both GEM_HOME and GEM_PATH has been set
So require stdlib like 'test-unit' or 'rake' will raise 'LoadError'

But ruby 2.2.3 and gem 2.5.1 no this problem

Updated by personnel (Am I Who) over 8 years ago

  • Description updated (diff)

Updated by personnel (Am I Who) over 8 years ago

  • Description updated (diff)

Updated by nobu (Nobuyoshi Nakada) over 8 years ago

  • Status changed from Open to Feedback
$ GEM_PATH=/ ruby2.3 -e 'p Gem.path'
["/", "/opt/local/lib/ruby2.3/gems/2.3.0"]
$ GEM_HOME=/ ruby2.3 -e 'p Gem.path'
["/Users/nobu/.gem/ruby/2.3.0", "/opt/local/lib/ruby2.3/gems/2.3.0", "/"]

Seems present.

Updated by personnel (Am I Who) over 8 years ago

  • Description updated (diff)

Updated by personnel (Am I Who) over 8 years ago

  • Subject changed from Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when GEM_HOME or GEM_PATH has seted to Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when GEM_HOME and GEM_PATH has seted

Updated by personnel (Am I Who) over 8 years ago

Nobuyoshi Nakada wrote:

$ GEM_PATH=/ ruby2.3 -e 'p Gem.path'
["/", "/opt/local/lib/ruby2.3/gems/2.3.0"]
$ GEM_HOME=/ ruby2.3 -e 'p Gem.path'
["/Users/nobu/.gem/ruby/2.3.0", "/opt/local/lib/ruby2.3/gems/2.3.0", "/"]

Seems present.

Sorry for my fault, It needs both GEM_HOME and GEM_PATH has seted.

Updated by personnel (Am I Who) over 8 years ago

  • Subject changed from Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when GEM_HOME and GEM_PATH has seted to Gem.path lost default path '[installdir]/lib/ruby/gems/2.3.0' when both GEM_HOME and GEM_PATH has seted
  • Description updated (diff)

Updated by nobu (Nobuyoshi Nakada) over 8 years ago

  • Status changed from Feedback to Third Party's Issue

Thank you, confirmed with all of 1.9..trunk.
It is an issue of rubygems.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0