Issues about Rubygems

ruby-talk
1

Hello,

I am a new user of the one-click installer (1.8.2-15).

I use the rubygems included in the distro. and it doesn't work. I tried
running the command "gem update" in command line and it displays:
C:\>gem update

C:\>"c:\ruby\bin\ruby.exe" "c:\ruby\bin\gem" update

Upgrading installed gems...
Updating Gem source index for: http://gems.rubyforge.org

and then it takes forever to load, and it never loads.
Since there is no such problem with another machine I have in my
office, it only get stuck with the one at my home.

Please help.

Itsnotvalid

2

Hey there-
     I've seen this problem on Windows a bunch of times come up on the list. Most of the time it is because you are running ZoneAlarm. ZoneAlarm does some funky stuff with how windows handles sockets. So it is not enough to just turn ZoneAlarm off. You must uninstall it completely and then gems should work for you. If you don't have ZoneAlarm then there must be some other issue. HTH
-Ezra

···

On Jul 29, 2005, at 4:21 AM, Itsnotvalid wrote:

Hello,

I am a new user of the one-click installer (1.8.2-15).

I use the rubygems included in the distro. and it doesn't work. I tried
running the command "gem update" in command line and it displays:
C:\>gem update

C:\>"c:\ruby\bin\ruby.exe" "c:\ruby\bin\gem" update

Upgrading installed gems...
Updating Gem source index for: http://gems.rubyforge.org

and then it takes forever to load, and it never loads.
Since there is no such problem with another machine I have in my
office, it only get stuck with the one at my home.

Please help.

Itsnotvalid

-Ezra Zygmuntowicz
Yakima Herald-Republic
WebMaster
509-577-7732
ezra@yakima-herald.com

3

I don't have ZoneAlarm, but I have other sorts of client firewalls
installed. Thanks for your suggestion. I would somewhat uninstall my
firewall and try again.

4

Itsnotvalid 寫道：

I don't have ZoneAlarm, but I have other sorts of client firewalls
installed. Thanks for your suggestion. I would somewhat uninstall my
firewall and try again.

I am also partly disappointed that there is no error message because of
a socket error, or a timeout message because of the connection.