On Jan 3, 2011, at 10:50, Len Lawrence wrote:
> On Sun, 02 Jan 2011 15:38:39 -0500, Jakub Groncki wrote:
>> I know that it sounds a bit lamely, but try to uninstall the gem and
>> then install it again.
>>=20
>> Happy New Year ;)
>=20
> Aye, I did that and sure enough the script works again.  The gem now=20=

> installs into the lib64 path so I suppose anything else I use will =
have=20
> to be reinstalled.  It must be a feature of the latest rubygem-update =
to=20
> go with the system architecture. =20

It's a feature of your ruby.  RubyGems installs in the directories that =
match your ruby install.=