Tom Copeland
6/2/2008 1:31:00 AM
On Mon, 2008-06-02 at 08:58 +0900, Michael T. Richter wrote:
> On Mon, 2008-06-02 at 04:07 +0900, Tom Copeland wrote:
> > > $ for a in actionmailer RedCloth rspec rubygems-update rails fxruby
> > > bindata actionpack gem_plugin rush ruby-debug-ide activeresource
> > > opod ; do echo $a ; until gem install $a ; do echo Retrying $a... ;
> > > done ; done
>
> > I think an easier way to do this might be:
> >
> > sudo gem install actionmailer RedCloth [... etc ...]
>
> The problem with this is that if -- scratch that, when -- it fails, I
> either have to go into the backscroll and figure out which pieces
> installed and which didn't, or I wrap that all up in an until and if
> (when) any single gem fails, the whole thing gets restarted.
Ah right, because the gem client is timing out, gotcha.
> My way, while less efficient overall, at least doesn't reinstall gems
> a dozen times over because the next-to-last one failed to install.
> Were the gems servers actually reliable, I wouldn't have to do even
> the until wrap, not to mention the grotesquely inefficient
> one-at-a-time approach I took above.
What surprises me is seeing the gem client fetch the uncompressed index
(that is, the yaml file) rather than fetching the compressed index. The
compressed version is only 1MB, and seems like that would be much less
likely to time out. It might be worth posting to the
rubygems-developers list and seeing if they could help you hunt down
this problem.
Yours,
Tom