Paul Codding's Weblog

Upgrading a large RoR Project from 1.2.6 to 2.0.2

Posted January 21st, 2008 by Paul Codding

This evening while upgrading a large Ruby on Rails application that I’ve been working on for the past year and a half, I ran into some issues upgrading to 2.0.2.  As you may know actionwebservice has been ousted from rails in favor of REST.  For those of us that depend on using SOAP for interoperability with other applications, we need it to work.  After spending a great deal of time googling to remove the following error:

`report_activate_error':
RubyGem version error: actionpack(2.0.2 not = 1.13.6) (Gem::LoadError)

I found this very helpful article about getting actionwebservices to run under Rails 2.0.2. I’ve yet to see the issues that some other users have seen when using actionwebservices with Rails 2.0.2, but we shall see in the coming days of using it. One thing I had to do that I didn’t really like was to freeze the rails gems into the project. I would rather not have them in my subversion repository.Another issue encountered was with installing gems that needed compilation on my OS X Leopard machine.  Luckily I found a great article detailing the use of the ARCHFLAGS environmental variable. So to install my postgres gem all I had to do was this:

$ sudo -s# export ARCHFLAGS="-arch i386"# gem install postgres

After that, the gem was installed and I no longer received any compile time errors. This stems from the universal binary support mechanism in OS X.