Forum: Ruby gems 1.3.0 updates itself every time?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
A63764f318f10379c8b51349b757cf4b?d=identicon&s=25 Jay Levitt (Guest)
on 2008-10-21 21:09
(Received via mailing list)
On both my Mac (OS X 10.5.5) and my Linux box (Fedora Core 9), gems 1.2
needed the help of "gem install rubygems-update;update_rubygems" to get
to 1.3.0.  Now, every time I do a "gem update --system", it reinstalls
1.3.0, instead of claiming "Nothing to update".

Is this a known problem with the transition to 1.3?  Obviously, the
solution is "don't do that, Jay"; I just want to make sure it's not a
symptom of a deeper problem on my systems.

Jay Levitt
B09f4659460545e38ece34ddd0d96b46?d=identicon&s=25 Yaser Sulaiman (Guest)
on 2008-10-21 21:40
(Received via mailing list)
The same thing happens with me on my Ubuntu 8.04 installation.

Regards,
Yaser Sulaiman

On Tue, Oct 21, 2008 at 8:18 PM, Jay Levitt
<jay+news@jay.fm<jay%2Bnews@jay.fm>
58479f76374a3ba3c69b9804163f39f4?d=identicon&s=25 Eric Hodel (Guest)
on 2008-10-21 22:18
(Received via mailing list)
On Oct 21, 2008, at 10:18 AM, Jay Levitt wrote:
> On both my Mac (OS X 10.5.5) and my Linux box (Fedora Core 9), gems
> 1.2 needed the help of "gem install rubygems-update;update_rubygems"
> to get to 1.3.0.  Now, every time I do a "gem update --system", it
> reinstalls 1.3.0, instead of claiming "Nothing to update".
>
> Is this a known problem with the transition to 1.3?  Obviously, the
> solution is "don't do that, Jay"; I just want to make sure it's not
> a symptom of a deeper problem on my systems.

There's a bug:

http://rubyforge.org/tracker/index.php?func=detail...

But it's not a high priority.  Other than wasting some time, this
behavior should be harmless.
This topic is locked and can not be replied to.