Rails 2.0.2: Some new defaults and a few fixes

rubyonrails-talk
1

Now that we have the big Rails 2.0 release out the door, it's a lot easier to push out smaller updates more frequently. So that's what we're going to do. Rails 2.0.2 contains a bunch of smaller fixes to various bugs, no show-stopping action, just further polish. But it also contains a few new defaults:

2

DHH wrote:

Now that we have the big Rails 2.0 release out the door, it's a lot easier to push out smaller updates more frequently. So that's what we're going to do. Rails 2.0.2 contains a bunch of smaller fixes to various bugs, no show-stopping action, just further polish. But it also contains a few new defaults:

Ruby on Rails — Rails 2.0.2: Some new defaults and a few fixes >

Am I the only getting

ERROR: While executing gem ... (OpenURI::HTTPError)   404 Not Found

  when trying to update to this latest Rails?

3

Am I the only getting

ERROR: While executing gem ... (OpenURI::HTTPError)         404 Not Found

  when trying to update to this latest Rails?

Hello Andy,

I can confirm it:

~ $ sudo gem update -y [sudo] password for armin: Updating installed gems... Attempting remote update of actionmailer Select which gem to install for your platform (i486-linux) 1. activesupport 2.0.2 () 2. Skip this gem 3. Cancel installation

1

ERROR: While executing gem ... (OpenURI::HTTPError)     404 Not Found ~ $

I have also no idea what is meant by the 1st platform. I mean the empty brackets.

Armin

4

Armin Joellenbeck wrote:

5

I had the same problem, here is the solution: http://bparanj.blogspot.com/2007/12/upgrading-to-rails-202.html

6

Unfortunately, your article seems to have disappeared...

7

The most important thing to do is "gem update --system". Then "gem update rails" worked for me.

///ark

8

Sorry guys Maredit messes up my post sometimes. Here is the working link: http://bparanj.blogspot.com/2007/12/upgrading-to-rails-202.html

9

Be very when doing a "gem update --system" if you installed with MacPorts. I'm not sure why but this completely hosed my rubygems and I wound up going back to ruby source and installing a fresh version of Ruby, rubygems, and all the gems. It was quicker than figuring out what was wrong (and what the heck else did I have to do with my time, right?).

If you do decide to "gem update --system", and you installed with MacPorts, at least take a snapshot of /opt/local/lib/ruby (or wherever you had port install your Ruby) so you can rollback if something gets toasted. Note that Eric Hodel said (on ruby-talk) "if you didn't build it, don't update it." Caveat updater.