From: "Michael T. Richter" <ttmrichter@...>
Date: 2008-06-11T15:13:05+09:00
Subject: Re: Gems error concerning yaml

--=-pdrgRMjPwewC6rjdDmXw
Content-Type: multipart/alternative; boundary="=-qw0ONbOuGnLyebeaoiu3"


--=-qw0ONbOuGnLyebeaoiu3
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2008-06-11 at 03:16 +0900, Eric Hodel wrote:

> Since there's no yaml gem, of course RubyGems will "choke" it.
>=20
> Other package managers "choke" on things that don't exist:


The problem is that rubygems' error messages, frankly put, suck bowling
balls through garden hoses.  They're basically the raised exception
without any attempt whatsoever to actually report the conditions that
led to the exception.  (This, to me, defeats the whole point of
exception-handling -- exception raised at the point of detection,
exception rescued at the point of knowing what went wrong, error message
produced that explains situation -- but this is neither here nor there.)

What I'm guessing is this: at some point in the gems update (which
always happens no matter how many times it caches the gem metadata --
read any number of a dozen other threads commenting on this by now) a
YAML file is being processed.  And it's failing for some reason.  And
this failure gets reported in a confusing fashion that makes it look
like the error is caused by a missing YAML component.

--=20
Michael T. Richter <ttmrichter@gmail.com> (GoogleTalk:
ttmrichter@gmail.com)
A well-designed and humane interface does not need to be split into
beginner and expert subsystems. (Jef Raskin)

--=-qw0ONbOuGnLyebeaoiu3
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/3.16.1">
</HEAD>
<BODY>
On Wed, 2008-06-11 at 03:16 +0900, Eric Hodel wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE>
<FONT COLOR=3D"#000000">Since there's no yaml gem, of course RubyGems will =
&quot;choke&quot; it.</FONT>

<FONT COLOR=3D"#000000">Other package managers &quot;choke&quot; on things =
that don't exist:</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
The problem is that rubygems' error messages, frankly put, suck bowling bal=
ls through garden hoses.&nbsp; They're basically the raised exception witho=
ut any attempt whatsoever to actually report the conditions that led to the=
 exception.&nbsp; (This, to me, defeats the whole <B>point</B> of exception=
-handling -- exception raised at the point of detection, exception rescued =
at the point of knowing what went wrong, error message produced that explai=
ns situation -- but this is neither here nor there.)<BR>
<BR>
What I'm guessing is this: at some point in the gems update (which always h=
appens no matter how many times it caches the gem metadata -- read any numb=
er of a dozen other threads commenting on this by now) a YAML file is being=
 processed.&nbsp; And it's failing for some reason.&nbsp; And this failure =
gets reported in a confusing fashion that makes it look like the error is c=
aused by a missing YAML component.<BR>
<BR>
<TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
-- <BR>
<B>Michael T. Richter</B> &lt;<A HREF=3D"mailto:ttmrichter@gmail.com">ttmri=
chter@gmail.com</A>&gt; (<B>GoogleTalk:</B> ttmrichter@gmail.com)<BR>
<I>A well-designed and humane interface does not need to be split into begi=
nner and expert subsystems. (Jef Raskin)</I>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>

--=-qw0ONbOuGnLyebeaoiu3--

--=-pdrgRMjPwewC6rjdDmXw
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)

iD8DBQBIT2zkLqyWkKVQ54QRAjTGAJ9hwbxaeeWVDd4sGHfZ88sCoPnOJQCeLkAM
rJ9hOY8U76U73Zpmr5FSmzI=
=AiYI
-----END PGP SIGNATURE-----

--=-pdrgRMjPwewC6rjdDmXw--