From: Rob Sanheim <rsanheim@...>
Date: 2009-09-24T12:08:31+09:00
Subject: Re: Ruby 1.9, Rubygems, and .gemspec warnings

--000e0cd292585d590104744a25c5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 23, 2009 at 10:18 PM, Andreas Haller <andreashaller@gmail.com>w=
rote:

> Don French wrote:
> > On Sep 10, 8:06=EF=BF=BDpm, Ryan Davis <ryand-r...@zenspider.com> wrote=
:
> >> Well, I recommend you don't do that.
> >> where you install your own rubygems update. So, for now, don't do that=
.
> > Am I missing something? how do you update rubygems with 1.9? Is there
> > a new process?
> > Thanks
>
> Don, i think you just don't. Rubygems now is part of/comes bunded with
> Ruby 1.9.
>
> However, i was having the same issue runnig on ruby 1.9.2dev (2009-09-15
> trunk 24928) [-darwin9.8.0], but only with a library/gem using Jeweler.
>
> Removing Jeweler solved the problem.
>

Rubygems comes bundled with Ruby 1.9, but IIRC its version 1.3.1 - or at
least it reports itself as such.  So once you run gem update --system, the
bug appears, at least until you remove that gem update.

- Rob

--000e0cd292585d590104744a25c5--