It seems the problem is already solved, as noted in the external
source: http://permalink.gmane.org/gmane.comp.lang.ruby.rails/264228
It was a network problem.
On 2 feb, 05:35, Mirage2008 wrote:
> Actually it wasn't trivial. It helped me :0)
>
> After the RubyGem/Bundler update mess yesterday,
Actually it wasn't trivial. It helped me :0)
After the RubyGem/Bundler update mess yesterday, I was afraid there
was yet another problem with my set up. Turns out my Time Machine's 5
GHz network was insanely unstable and caused the error. If it weren't
for your post, I would have spent hours sea
I know that sounds trivial, and the thread is two weeks old, but are you
sure you are connected to the Internet during that tests? It took me
yesterday 2 hours to find that problem on my local staging environment. Due
to configuration problems I could connect via ssh and remote control, but my
netw
On Sun, Jan 9, 2011 at 4:28 PM, djangst wrote:
> rubygems.org is (again) the definitive source:
>
> http://update.gemcutter.org/2010/02/20/rubygems-org-move-complete.html
Ah, crap. Guess I missed that memo :-)
Never mind, then, and sorry for the noise.
--
Hassan Schroeder ---
Hassan,
rubygems.org is (again) the definitive source:
http://update.gemcutter.org/2010/02/20/rubygems-org-move-complete.html
gemcutter.org redirects to rubygems.org.
On Jan 9, 7:01 pm, Hassan Schroeder
wrote:
> The reference to rubygems.org is out of date.
--
You received this message beca
5 matches
Mail list logo
