From: hemant <gethemant@...>
Date: 2008-02-12T01:53:12+09:00
Subject: Re: Problems with Rubygems

On Mon, Feb 11, 2008 at 8:40 PM, Ken Bloom <kbloom@gmail.com> wrote:
>
> On Sun, 10 Feb 2008 20:34:10 -0500, Ali Panick wrote:
>
>  > hemant wrote:
>  >> Hi,
>  >>
>  >> I am facing some issues with Rubygems on my ubuntu gutsy machine, where
>  >> Ruby 1.8.6 p111 is compiled and installed with:
>  >>
>  >> ./configure --prefix=/usr/local
>  >>
>  >> ruby executable is not symlinked and I have /usr/local/bin in path.
>  >>
>  >> Recently I started to notice that, gem executables while installing
>  >> gems aren't getting created anywhere in path. I thought, it could be a
>  >> rubygems version issue and I ran:
>  >>
>  >> sudo gem update --system
>  >>
>  >> which seems to have updated to rubygems version 1.0.1, and yet when i
>  >> run:
>  >>
>  >> gem --version
>  >> 0.9.5
>  >>
>  >> So definitely something fishy going on here!
>  >>
>  > this is a simple and maybe stupid reply. I encountered the same problem
>  > yesterday installing rubygems on my vps.
>  >
>  > I logged out and problem was fixed.
>
>  If logging out fixed it, the problem probably wasn't fixed. What probably
>  happened was that when you updated with gem update --system, it installed
>  rubygems 1.0.1 into a different location. Since your shell (probably
>  bash) had hashed the location of rubygems so it wouldn't have to go
>  searching, it continued to use the old binary until you logged out and
>  logged back in. Run
>  $ whereis gem
>  make sure you don't have extra copies of rubygems hanging around
>  somewhere, and clean up the mess if you do.
>

Well for me, logging out doesn't resolve the problem and the problem
persists. I don't have any rubygems installation hanging around. I do
have Ruby1.9 compiled and installed, but its not in path and I
generally use aliases ruby2 and gem2 to run my programs with Ruby1.9.