rake freeze error

I tried to freeze an app only to have it blow up in my face. This one is completely beyond me. My hard drive crashed on me recently, and this is a brand new rails 1.2.1/gem 0.9.1 installation. Worked fine before on 1.1.6/0.9.0, but now, this:

republic:~/work/rakehatesme ron$ rake rails:freeze:gems --trace (in /Users/ron/work/rakehatesme) ** Invoke rails:freeze:gems (first_time) ** Execute rails:freeze:gems Freezing to the gems for Rails 1.2.1 rm -rf vendor/rails mkdir -p vendor/rails cd vendor/rails ERROR: While executing gem ... (ArgumentError)     install directory "activesupport-1.4.0" not absolute rake aborted! exit /usr/local/lib/ruby/site_ruby/1.8/rubygems/user_interaction.rb:171:in `exit' /usr/local/lib/ruby/site_ruby/1.8/rubygems/user_interaction.rb:171:in `terminate_interaction' (eval):3:in `terminate_interaction' /usr/local/lib/ruby/site_ruby/1.8/rubygems/cmd_manager.rb:95:in `run' /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:30:in `run' /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/tasks/framework.rake:26 /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/tasks/framework.rake:25:in `each' /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/tasks/framework.rake:25 /usr/local/lib/ruby/1.8/fileutils.rb:121:in `chdir' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:812:in `chdir' /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/tasks/framework.rake:24 /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in `invoke' /usr/local/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7 /usr/local/bin/rake:16:in `load' /usr/local/bin/rake:16

-Ron

I (and many others) have experienced this issue. It seems to be related to the new rubygems rather than rails, or the interaction between the two.

upgrading to the latest gem seems to fix the problem.

gem update --system