# Remote gem install doesn't work anymore

**URL:** <https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492>\
**Category:** Ruby\
**Created:** [November 4, 2008, 4:16pm UTC](https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492 "2008-11-04T16:16:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![forex](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/8491ac/32.png) [@forex](https://www.ruby-forum.com/u/forex)\
**Post date:** [November 4, 2008, 4:16pm UTC](https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492/1 "2008-11-04T16:16:49Z")

</div>

hello,  
i’m under ubuntu hardy with gem v1.1.0 installed  
when i want to install a new gem (ie hpricot), here is the result:

“sudo gem install hpricot  
Bulk updating Gem source index for: [http://gems.rubyforge.org/](http://gems.rubyforge.org/)  
ERROR: could not find hpricot locally or in a repository”

it is the same with every other gem  
and it work locally with no problem

i have to say that i’ve installed different versions of the same gems to  
work on old projects.  
I also want to state that i cannot use wxruby because of what i suppose  
is a $PATH problem (i’m new to linux and ubuntu, so i don’t know how to  
check my $PATH)

thanxs for your help

---

<div class="post-metadata">

**Author:** ![forex](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/8491ac/32.png) [@forex](https://www.ruby-forum.com/u/forex)\
**Post date:** [November 6, 2008, 7:15pm UTC](https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492/2 "2008-11-06T19:15:58Z")

</div>

Forex Forex wrote:

> hello,  
> i’m under ubuntu hardy with gem v1.1.0 installed  
> when i want to install a new gem (ie hpricot), here is the result:
> 
> “sudo gem install hpricot  
> Bulk updating Gem source index for: [http://gems.rubyforge.org/](http://gems.rubyforge.org/)  
> ERROR: could not find hpricot locally or in a repository”
> 
> it is the same with every other gem  
> and it work locally with no problem

I was getting this the other day on Windows when no gem seemed to want  
to install, including gem update. But I’m not there now and can’t retest  
or check versions.

> I also want to state that i cannot use wxruby because of what i suppose  
> is a $PATH problem (i’m new to linux and ubuntu, so i don’t know how to  
> check my $PATH)

Hard to say what’s going wrong without an error message.

The latest version of wxRuby (1.9.9) on Linux requires that you install  
the wxWidgets shared libraries. This should be trivial using your  
package manager (synaptic) - find the wxWidgets 2.8.7 package  
(non-debug) from Hardy and install it.

If it’s not resolved, please post a more detailed description of the  
problem to the wxruby-users mailing list.

[http://rubyforge.org/mailman/listinfo/wxruby-users](http://rubyforge.org/mailman/listinfo/wxruby-users)  
[http://www.ruby-forum.com/forum/36](http://www.ruby-forum.com/forum/36)

a

---

<div class="post-metadata">

**Author:** ![forex](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/8491ac/32.png) [@forex](https://www.ruby-forum.com/u/forex)\
**Post date:** [November 7, 2008, 11:05am UTC](https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492/3 "2008-11-07T11:05:22Z")

</div>

thx for your help

about wxruby, the problem is solved. it seems that you cannot give wx.rb  
to your file.  
in fact i was just trying the tutorial and had given wx.rb to my file.  
after changing filename, everything goes right…

about remote gem install, problem’s still alive

---

<div class="post-metadata">

**Author:** ![forex](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/8491ac/32.png) [@forex](https://www.ruby-forum.com/u/forex)\
**Post date:** [November 7, 2008, 3:20pm UTC](https://www.ruby-forum.com/t/remote-gem-install-doesnt-work-anymore/152492/4 "2008-11-07T15:20:14Z")

</div>

> about remote gem install, problem’s still alive

i finally managed to find a solution.  
hereafter for those interested:

install manually rubygems-update  
then type: sudo update\_rubygems

after, everything works well like before

this was due to a bug in a specific version of rubygems