Leftover gems after upgrading to Rails 2.1

Also, I checked the gems folder C:\ruby\lib\ruby\gems\1.8\gems and it
shows the previous gems along with the new gems for Rails, e.g., it has
actionpack-1.13.1 and actionpack-2.1.0, activerecord-1.15.1 and
activerecord-2.1.0, and so on, you get the idea.

So my question is that normal? Should the old gems still be there? If
not, how do I remove them? Thanks in advance for your help.

$ gem help cleanup
Usage: gem cleanup [GEMNAME ...] [options]

   Options:
     -d, --dryrun

   Common Options:
     -h, --help Get help on this command
     -V, --[no-]verbose Set the verbose level of output
     -q, --quiet Silence commands
         --config-file FILE Use this config file instead of default
         --backtrace Show stack backtrace on errors
         --debug Turn on Ruby debugging

   Arguments:
     GEMNAME name of gem to cleanup

   Summary:
     Clean up old versions of installed gems in the local repository

   Defaults:
     --no-dryrun

In short, it's normal for multiple versions of the gems to be there.

Also, there's no reason not to upgrade to Ruby 1.8.6 as long as you
avoid the latest patch that's causing all the trouble. The One-Click
Installer here [ http://rubyforge.org/frs/?group_id=167 ] should be
fine, as it's based on patch level 111 of the main Ruby 1.8.6
distribution.

Regards,
Craig

Philip Hallstrom wrote:

$ gem help cleanup

Philip, thanks for the info, here's the output

Craig Demyanovich wrote:

In short, it's normal for multiple versions of the gems to be there.

Also, there's no reason not to upgrade to Ruby 1.8.6 as long as you
avoid the latest patch that's causing all the trouble. The One-Click
Installer here [ http://rubyforge.org/frs/?group_id=167 ] should be
fine, as it's based on patch level 111 of the main Ruby 1.8.6
distribution.

Regards,
Craig

Craig, actually there are a few good reasons for me not to upgrade to
1.8.6, see my post on the issues I encountered here
http://rubyonrailswin.wordpress.com/2008/06/23/upgrading-ruby/

I am not familiar with the latest patch problem with one click install,
what is it?

Philip Hallstrom wrote:

$ gem help cleanup

Philip, thanks for the info, here's the output
-----------------------------------------------------
C:\Documents and Settings\Bob>gem cleanup
Cleaning up installed gems...
Attempting to uninstall rails-1.2.1
Successfully uninstalled rails-1.2.1
Attempting to uninstall actionmailer-1.3.1
Successfully uninstalled actionmailer-1.3.1
Attempting to uninstall activerecord-1.15.1

You have requested to uninstall the gem:
       activerecord-1.15.1
actionwebservice-1.2.1 depends on [activerecord (= 1.15.1)]
rails-1.2.1 depends on [activerecord (= 1.15.1)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] n
Unable to uninstall activerecord-1.15.1:
       Gem::DependencyRemovalException: Uninstallation aborted due to
dependent
gem(s)
Attempting to uninstall rake-0.7.1
ERROR: Interrupted
Terminate batch job (Y/N)? y
-----------------------------------------------------
I terminated the cleanup because my current app is frozen to rails
1.2.1, so it shouldn't be a problem for me to uninstall
activerecord-1.15.1, right? I intend to start a new app with Rails 2.1
and keep my current app at 1.2.1, just making sure I am not going to
screw anything with the cleanup. Thanks again for your help.

If you've frozen rails into vendor you don't need any of the gems installed.

Philip Hallstrom wrote:

Attempting to uninstall actionmailer-1.3.1
       Gem::DependencyRemovalException: Uninstallation aborted due to
screw anything with the cleanup. Thanks again for your help.

If you've frozen rails into vendor you don't need any of the gems
installed.

Thanks that's what I thought. Also, I found out that Rails 2.x does not
include actionwebservice gem by default now (it does in 1.x), quoting
from article
http://weblog.rubyonrails.org/2007/9/30/rails-2-0-0-preview-release

Craig, actually there are a few good reasons for me not to upgrade to
1.8.6, see my post on the issues I encountered here
http://rubyonrailswin.wordpress.com/2008/06/23/upgrading-ruby/

Ah, I know your pain when wanting to upgrade Ruby on Windows. In the
past for me, the pain hasn't been so great that I decided not to
upgrade, though. I just made a note of what I wanted to keep,
uninstalled old Ruby, installed new Ruby, installed gem versions that
I wanted to keep and installed new gems.

I am not familiar with the latest patch problem with one click install,
what is it?

There's no problem with the One-Click Installer itself of which I'm
aware. I was noting that, since it is based on Ruby 1.8.6 p111, it
should be fine. A new patch level of Ruby 1.8.6, p230, was announced
recently, but it has caused problems for many people. There are
several mailing list discussions (on ruby-talk) and blog posts about
it if you care to search.

Craig

Craig Demyanovich wrote:

Is upgrading Ruby a non-issue for Linux? I am on FC6. Well if it was
just limited to gems, I would have taken the plunge but for me, I used
htree which wasn't packaged as a gem, plus I remembered having to do
something funky to get MySQL and Mongrel gems working, so it wasn't a
straight gem upgrade deal for me.

I meant to say I am on FC6 for my production machine, I am using Windows
XP for my development machine.

I've only worked a little on Linux. There, package managers can make
upgrading easy, or those in the know just rebuild Ruby from source.
I'm sure that there is a thing or two not to do no matter which of
those two approaches one uses.

I spend almost all of my time working on Mac OS X 10.5, which includes
Ruby. Since I've been using the stock Ruby distribution, I get
upgrades when Apple releases them. Another approach on OS X is to use
a package manager like Fink [ http://www.finkproject.org/ ] or
MacPorts [ http://www.macports.org/ ] to install and maintain Ruby.
Both make upgrading Ruby pretty painless, and they track Ruby releases
a little more closely than Apple does.

On OS X, at least, I've never had to reinstall gems or reconfigure my
Ruby environment in any way when upgrading. I expect that the same is
true on Linux, but I don't know for sure.

While I wouldn't say that upgrading Ruby on Linux or OS X is a
non-issue, it has been, in my experience, vastly easier than on
Windows.

That said, I suppose you could run Ruby under cygwin [
http://www.cygwin.com/ ] on Windows if it would suit your needs. You'd
be working in a Unix/Linux-like environment, and you'd have package
management at your disposal for upgrades.

Craig

Craig Demyanovich wrote:

I've only worked a little on Linux. There, package managers can make
upgrading easy, or those in the know just rebuild Ruby from source.
I'm sure that there is a thing or two not to do no matter which of
those two approaches one uses.

I spend almost all of my time working on Mac OS X 10.5, which includes
Ruby. Since I've been using the stock Ruby distribution, I get
upgrades when Apple releases them. Another approach on OS X is to use
a package manager like Fink [ http://www.finkproject.org/ ] or
MacPorts [ http://www.macports.org/ ] to install and maintain Ruby.
Both make upgrading Ruby pretty painless, and they track Ruby releases
a little more closely than Apple does.

On OS X, at least, I've never had to reinstall gems or reconfigure my
Ruby environment in any way when upgrading. I expect that the same is
true on Linux, but I don't know for sure.

While I wouldn't say that upgrading Ruby on Linux or OS X is a
non-issue, it has been, in my experience, vastly easier than on
Windows.

That said, I suppose you could run Ruby under cygwin [
http://www.cygwin.com/ ] on Windows if it would suit your needs. You'd
be working in a Unix/Linux-like environment, and you'd have package
management at your disposal for upgrades.

Craig

Ah, RoR gets all the love on Mac, textmate and all *sigh*, Windows XP is
seriously a redheaded stepchild LOL. I am guessing Linux upgrade should
be relatively painless (hopefully) but I won't be upgrading it until a
later point in time when I take the plunge first for Windows to keep the
2 environments as similar as possible. Good suggestion about cygwin, I
do have it on my system but for now will keep the current Windows setup
with Ruby 1.8.5 and I got Rails 2.1 working. Per your suggestions
searching for 1.8.6 issues, seems like it can give me some additional
grief, so I am sticking with 1.8.5 :slight_smile:

Thanks for all your help.

Cali,
It's nice to hear someone rationally explain using RonR on a Windows
XP machine. It seems there are evangelical emotions for those who do
not.
Do you think there should be a RonR forum for people who develop on
Windows machines? I've got an RonR Linux installation running next to
me but seem to get more work done on my Windows XP using NetBeans 6.1.
Kathleen

KathysKode@gmail.com wrote:

Cali,
It's nice to hear someone rationally explain using RonR on a Windows
XP machine. It seems there are evangelical emotions for those who do
not.
Do you think there should be a RonR forum for people who develop on
Windows machines? I've got an RonR Linux installation running next to
me but seem to get more work done on my Windows XP using NetBeans 6.1.
Kathleen

On Jun 28, 2:33�pm, Cali Wildman <rails-mailing-l...@andreas-s.net>

Great idea Kathy, I like it so much that I went ahead and created a
Google group
http://groups.google.com/group/ruby-on-rails-windows

I sent you an email to join, any other RoR Windows developer, please
join us. I will send an email to ruby-forum admin to see if I can get it
added to here.