Rails: The Revenge!
Posted (December 17th, 2007 at 4:02 pm PST) by TerriJust when I thought it was safe to upgrade, another version appears!
I’m going to start upgrading our servers to Rails 2.0.2. This involves packaging, testing, and then slowly rolling it out. The jump is to a 2.x version from 1.2.6, so I’m going to take my time with this one to make sure nothing goes horribly wrong, so it might be right after the new year when it’s all done, just to be safe.
For your new year’s resolution, you will freeze your rails! Login via shell, and in your rails directory, run “rake freeze_gems” - that should do the trick!
Please contact support if you have any questions or concerns.
15 Responses to “Rails: The Revenge!”
I can’t seem to freeze either (on reeses):
Freezing to the gems for Rails 1.2.6
rm -rf vendor/rails
mkdir -p vendor/rails
cd vendor/rails
rake aborted!
uninitialized constant Gem::GemRunner
Any ideas?
Same “uninitialized constant Gem::GemRunner” freeze error for me on Pierce. Here are a couple links that talk about it but it seems the fix needs to be done to the gem, which I don’t think we have access to:
http://bpdp.wordpress.com/2007/11/28/rubygems-095-and-rails-126-uninitialized-constant-gemgemrunner/
http://groups.google.com/group/rubyonrails-core/browse_thread/thread/d3e96496eca8735c
as a word of advice from a developer who keeps seeing his old sites error offline because of a deleted gem. i’d hold off on deleting old 1.x rails gems from the servers even if you do install the 2.0.x versions. it’s a very incompatible upgrade and there’s no harm in have a little extra code on each server satisfy those of us who aren’t keen on freezing. different rails versions can live in harmony together. very few developers are jumping on the 2.0 bandwagon.
I have already a 2.0 app running on DH because I froze it. I dunno if it was the right thing to do, but everything works. Now back to rails site to see what 2.0.2 is about 
Same GemRunner error here on pacman.
Also getting the Gem::GemRunner error on crenshaw & virgil
Could you hold off on the upgrade until we can freeze to 1.2.6?
As a workaround to the freeze_gems problem. Try
rake rails:freeze:edge TAG=rel_1-2-6
Seems to work OK for me.
For anyone who ran “rake freeze_gems” and got the gemrunner error, for Steven’s fix to work, you first need to “rm -rf vendor” to undo the failed first attempt at freezing gems.
Alex P, if you rm -rf vendor you remove also plugins and other stuff you could have there other than the gems. Better backup vendor somewhere before attempting the upgrade and then restore it if something goes wrong.
Rails 1.2.6 has a bug, DH has patched this on all of the servers. If you still get the error when freezing rails then this means you probably have a failed freeze in your vendor directory. Remove the vendor/rails directory and try the freeze again… Remember, if all else fails, tell support.
Any word on when we can expect the 2.x upgrade to be rolled out?
I just checked in and noticed this post says “Resolved: Yes” now. I logged into pierce and there is indeed a 2.0.2 gem. Guess I should see if mine will run on 2.0.2. 
When I try the rake command under windows xp, it errors because svn isn’t on the machine and isn;t mentioned in PATH.
Can anyone point me to a “dummies” guide to setting up svn?
Does the version of svn matter?
And what would I add to PATH?
Many thanks,
Les
I heard a rumor that there is a way to force an older version of Rails in my environment.rb
I don’t know how to do that, though. Any tips?
Doesn’t freeze on Godiva:
no such file to load — /home/.godiva/MYUSER/MYAPP/config/../vendor/rails/railties/lib/initializer