From: Bret Weinraub <bretweinraub@...>
Date: 2010-02-17T02:19:21+09:00
Subject: Re: All attempts to install gems hang

Evan Dorn wrote:
> Bret Weinraub wrote:
>> I've managed to get some progress (I can actually install a gem) if I 
>> specify --ignore-dependencies.
> 
> 
> Interesting, I may have to try that.
> 
> I did in fact get gems working just by using Apple's pre-install Ruby 
> and Gems.
> 
> I couldn't do that with 10.5, because the pre-installed Ruby was 1.8.6 
> rather than 1.8.7, and I had compatibility problems with some of my 
> plugins under 1.8.6.  But so far it's working for Snow Leopard.
> 
> It's frustrating, though, that building my own Ruby would cause such a 
> problem.  It works just fine on on my desktop (Mac Pro) - it's only on 
> the laptop where it's been a problem.

Although I never actually was able to put my finger on something that 
fully did not work, I was able to resolve my problem via voodoo rites.

Basically this Ubuntu instance was running in Virtual Box on a Win7 
machine.  Now virtual box (like a lot of virtualization software) 
generally defaults to NAT (network address translation) for network 
connectivity.

Switching to "Bridged" on the interface pretty much cleared up the 
problem; even though heavy network users like "apt-get" functioned just 
fine.  Whatever flakiness exists in the network only manifested itself 
with "gem install".  Bridged gives you a real address on your network, 
instead of your packets being rewritten by the "host" machine.

I've seen of this with some VPN software; just will not function over a 
NAT-ed interface.  Switch to bridged, and its all good.

Probably should be a bug report for rubygems; it won't run off a NAT-ed 
VM.
-- 
Posted via http://www.ruby-forum.com/.