tag:help.rubygems.org,2010-01-19:/discussions/problems/51-unable-to-run-gem-update-with-rubygems-136-gem-update-foo-works-howeverRubyGems.org: Discussion 2011-05-27T00:27:37Ztag:help.rubygems.org,2010-01-19:Comment/10752072010-02-21T21:23:09Z2010-02-21T21:23:09ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>What does your gem list say?</p>
<p>Does running gem cleanup first help?</p>
<p>Installing randexp 0.1.0 then running gem update works for me
when randexp 0.1.0 is the only gem in my repository.</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/10752072010-02-21T22:48:58Z2010-02-21T22:49:02ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>I had already run a gem cleanup before updating. I don't think
there's anything special about randexp - this behavior happens for
whatever gem happens to be the first one it attempts to update. I
had already gone through and updated some gems individually after
hitting this snag on gem update (I don't remember all of them, but
at least amqp, merb-gen, merb-core, and haml); in each case, gem
update would time out on the first gem it attempted to update. I do
have a bunch of gems installed, as you can see below.</p>
<pre>
<code>*** LOCAL GEMS ***
abstract (1.0.0)
actionmailer (2.3.5)
actionpack (2.3.5)
activerecord (2.3.5)
activeresource (2.3.5)
activesupport (3.0.pre)
addressable (2.1.1)
amqp (0.6.7)
bcrypt-ruby (2.1.2)
blather (0.4.8)
builder (2.1.2)
bundler (0.9.7)
bunny (0.6.0)
capistrano (2.5.16)
capistrano-ext (1.2.1)
cgi_multipart_eof_fix (2.5.0)
cheat (1.2.1)
columnize (0.3.1)
configatron (2.5.1)
cucumber (0.6.2)
curb (0.6.6.0)
daemon-kit (0.1.7.12)
daemons (1.0.10)
data_objects (0.10.1)
diff-lcs (1.1.2)
dm-aggregates (0.10.2)
dm-constraints (0.10.2)
dm-core (0.10.2)
dm-is-state_machine (0.10.2)
dm-is-tree (0.10.2)
dm-migrations (0.10.2)
dm-serializer (0.10.2)
dm-sweatshop (0.10.2)
dm-timestamps (0.10.2)
dm-types (0.10.2)
dm-validations (0.10.2)
do_mysql (0.10.1)
do_sqlite3 (0.10.1.1)
em-http-request (0.2.7)
erubis (2.6.5)
eventmachine (0.12.10)
extlib (0.9.14)
facets (2.8.1)
fastercsv (1.5.1)
fastthread (1.0.7)
gem_plugin (0.2.3)
git (1.2.5)
haml (2.2.20)
handsoap (1.1.7)
highline (1.5.2)
hoe (2.5.0)
httpclient (2.1.5.2)
idn (0.0.2)
jeweler (1.4.0)
json (1.2.0)
json_pure (1.2.0)
libxml-ruby (1.1.3)
linecache (0.43)
mailfactory (1.4.0)
markup_validity (1.1.0)
memcached (0.18.0)
merb (1.0.15)
merb-action-args (1.0.15)
merb-assets (1.0.15)
merb-auth (1.0.15)
merb-auth-core (1.0.15)
merb-auth-more (1.0.15)
merb-auth-slice-password (1.0.15)
merb-cache (1.0.15)
merb-core (1.0.15)
merb-exceptions (1.0.15)
merb-gen (1.0.15)
merb-haml (1.0.15)
merb-helpers (1.0.15)
merb-mailer (1.0.15)
merb-more (1.0.15)
merb-param-protection (1.0.15)
merb-slices (1.0.15)
merb_datamapper (1.0.15)
merb_jquery (0.9.13)
mime-types (1.16)
mongrel (1.1.5)
net-scp (1.0.2)
net-sftp (2.0.4)
net-ssh (2.0.20)
net-ssh-gateway (1.0.1)
newgem (1.5.2)
nokogiri (1.4.1)
ParseTree (3.0.4)
polyglot (0.3.0)
rack (1.1.0)
rack-test (0.5.3)
rails (2.3.5)
rake (0.8.7)
randexp (0.1.4)
RedCloth (4.2.2)
rspec (1.3.0, 1.2.9)
rubigen (1.5.2)
ruby-debug (0.10.3)
ruby-debug-base (0.10.3)
ruby2ruby (1.2.4)
ruby_parser (2.0.4)
rubyforge (2.0.3)
rubygems-update (1.3.6)
RubyInline (3.8.4)
rvm (0.1.1)
sexp_processor (3.0.3)
soap4r (1.5.8)
stringex (1.1.0)
syntax (1.0.0)
templater (1.0.0)
term-ansicolor (1.0.4)
thor (0.12.3, 0.9.9)
treetop (1.4.3)
uuidtools (2.1.1)
webrat (0.5.3)
wirble (0.1.3)
xmpp4r (0.5)
yajl-ruby (0.6.8)
yamler (0.1.0)
yard (0.5.3)
ZenTest (4.2.1)</code>
</pre></div>Greg Campbelltag:help.rubygems.org,2010-01-19:Comment/10752072010-02-22T19:46:46Z2010-02-22T19:46:46ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>Another report of this...</p>
<p><a href=
"http://gist.github.com/311413">http://gist.github.com/311413</a></p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/10752072010-04-23T04:31:29Z2010-04-23T04:31:51ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>Ive had exactly the same issue and have spent ALL DAY
troubleshooting this.</p>
<p>Are you running something like virtual box?<br>
Im running Ubuntu via Virtualbox on a Vista machine.</p>
<p>Basically change your network settings from 'NAT' to 'Bridged'.
Seems that the NAT network settings are a little flaky for gem.</p>
<p>Found the answer here:<br>
<a href=
"http://www.ruby-forum.com/topic/204146">http://www.ruby-forum.com/topic/204146</a></p>
<p>Cheers</p>
<p>Evolve2k</p></div>evolve2ktag:help.rubygems.org,2010-01-19:Comment/10752072010-11-17T07:26:39Z2010-11-17T07:26:39ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>Watchers, any more recent experiences with this?</p></div>John Barnettetag:help.rubygems.org,2010-01-19:Comment/10752072011-02-09T11:38:42Z2011-02-09T11:38:43ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>Trying to install rails under UBUNTU</p>
<p>“bundler requires RubyGems version >= 1.3.6″</p>
<p>Package Manager tells me 1.9.1 is installed.</p>
<p>Gem update --system "is disabled on debian"</p>
<p>BUT I AM USING UBUNTU</p>
<p>Wondering what moron designed this and resolving never to hire
anyone who worked on ubunto or ruby or Jruby<br></p></div>ALEX ktag:help.rubygems.org,2010-01-19:Comment/10752072011-02-22T14:00:15Z2011-02-22T14:00:16ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>ALEX, you do realize Ubuntu IS Debian?</p></div>garustag:help.rubygems.org,2010-01-19:Comment/10752072011-05-27T00:27:36Z2011-05-27T00:27:36ZUnable to run "gem update" with RubyGems 1.3.6; "gem update foo" works, however<div><p>This seems like an old, outdated thread. If there's more issues
with this please open a new ticket and we'll try to reproduce
it.</p></div>Nick Quaranto