Gem update

Hi,

I’m behind a firewall. How can I update ruby modules?

If I try to do a

gem update --system

I get the following error:

ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
getaddrinfo: no address associated with hostname.(SocketError)

PS: Windows XP SP3 - Ruby 1.8.6

Thanks!

On Fri, Jul 11, 2008 at 8:52 AM, José Cruz [email protected]
wrote:

ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
getaddrinfo: no address associated with hostname.(SocketError)

PS: Windows XP SP3 - Ruby 1.8.6

Thanks!

Posted via http://www.ruby-forum.com/.

Can you ping http://gems.rubyforge.org?


“Hey brother Christian with your high and mighty errand, Your actions
speak
so loud, I can’t hear a word you’re saying.”

-Greg Graffin (Bad Religion)

No!

Glen H. wrote:

On Fri, Jul 11, 2008 at 8:52 AM, José Cruz [email protected]
wrote:

ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
getaddrinfo: no address associated with hostname.(SocketError)

PS: Windows XP SP3 - Ruby 1.8.6

Thanks!

Posted via http://www.ruby-forum.com/.

Can you ping http://gems.rubyforge.org?


“Hey brother Christian with your high and mighty errand, Your actions
speak
so loud, I can’t hear a word you’re saying.”

-Greg Graffin (Bad Religion)

José Cruz wrote:

Hi,

I’m behind a firewall. How can I update ruby modules?

If I try to do a

gem update --system

I get the following error:

ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
getaddrinfo: no address associated with hostname.(SocketError)

PS: Windows XP SP3 - Ruby 1.8.6

Thanks!

Hi,

if its a proxy problem u can try to set an environment variable in
windows
via
HTTP_PROXY = http://usr:pwd@myproxy:port

it worked for me :wink:

On Fri, Jul 11, 2008 at 9:34 AM, José Cruz [email protected]
wrote:


“Hey brother Christian with your high and mighty errand, Your actions
speak
so loud, I can’t hear a word you’re saying.”

-Greg Graffin (Bad Religion)


Posted via http://www.ruby-forum.com/.

Sounds like it is either your firewall or DNS/Routing problems then. In
other words it’s more of a system/network problem than a ruby one. You
could try downloading and installing it manually if you can get to the
gem
to download it.

http://www.ghostonthird.com/2007/12/17/manually-downloading-and-installing-gems/


“Hey brother Christian with your high and mighty errand, Your actions
speak
so loud, I can’t hear a word you’re saying.”

-Greg Graffin (Bad Religion)