From: "Michael T. Richter" Date: 2008-06-01T22:53:59+09:00 Subject: Re: Gems not working --=-ZJdul+9yZVtm3/IbDXST Content-Type: multipart/alternative; boundary="=-qxQgwPlq6rBiiwRw/fbg" --=-qxQgwPlq6rBiiwRw/fbg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-06-01 at 09:20 +0900, Tom Copeland wrote: > On Fri, 2008-05-30 at 03:55 +0900, Jim Hoskins wrote: > > I am currently not able to install any gems. I was using Gem 1.1.1 but > > kept receiving the following errors: > >=20 > > ERROR: While executing gem ... (Gem::RemoteSourceException) > > Error fetching remote gem cache: Errno::EPIPE: Broken pipe reading > > http://gems.rubyonrails.org/yaml >=20 > Hm, that "yaml" file is 20 MB now... is your client timing out, or maybe > refusing to fetch that much data? The gem servers at rubyforge and whoever hosts for ruby on rails seem to be badly overloaded. I get these broken pipe errors all the time to the point that I wrap all uses of gem in "unless" blocks in bash to make sure things actually go through. What would help is if the --no-update-sources flag actually did something. Half the time the point of failure lies in updating the local source cache from the remote site, but whether or not I specify --no-update-sources the source cache is downloaded at tremendous expense. Sometimes it's downloaded multiple times in a single invocation (if I install a lot of gems at the command line at once). --=20 Michael T. Richter (GoogleTalk: ttmrichter@gmail.com) It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it. (Steve McConnell) --=-qxQgwPlq6rBiiwRw/fbg Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Sun, 2008-06-01 at 09:20 +0900, Tom Copeland wrote:
On Fri, 2008-05-30 at 03:55 +0900, Jim Hoskins wrot=
e:
> I am currently not able to install any gems. I=
 was using Gem 1.1.1 but
> kept receiving the following errors:
> 
> ERROR:  While executing gem ... (Gem::RemoteSo=
urceException)
>     Error fetching remote gem cache: Errno::EP=
IPE: Broken pipe reading
> h=
ttp://gems.rubyonrails.org/yaml

Hm, that "yaml" file is 20 MB now... is y=
our client timing out, or maybe
refusing to fetch that much data?

The gem servers at rubyforge and whoever hosts for ruby on rails seem to be= badly overloaded.  I get these broken pipe errors all the time to the= point that I wrap all uses of gem in "unless" blocks in bash to = make sure things actually go through.

What would help is if the --no-update-sources flag actually did something.&= nbsp; Half the time the point of failure lies in updating the local source = cache from the remote site, but whether or not I specify --no-update-source= s the source cache is downloaded at tremendous expense.  Sometimes it'= s downloaded multiple times in a single invocation (if I install a lot of g= ems at the command line at once).

--
Michael T. Richter <ttmri= chter@gmail.com> (GoogleTalk: ttmrichter@gmail.com)
It's OK to figure out murder mysteries, but you shouldn't need to figure= out code. You should be able to read it. (Steve McConnell)
--=-qxQgwPlq6rBiiwRw/fbg-- --=-ZJdul+9yZVtm3/IbDXST Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIQqntLqyWkKVQ54QRArShAJsFWeomIu/ZoF5jHp0e1sQj1GSv3wCeJtoI Rsa3+dpOHEqBCOksjWH2P5Q= =y0BU -----END PGP SIGNATURE----- --=-ZJdul+9yZVtm3/IbDXST--