# Cannot Freeze Gems **URL:** \ **Category:** Rails\ **Created:** [December 9, 2007, 8:36pm UTC](https://www.ruby-forum.com/t/cannot-freeze-gems/122579 "2007-12-09T20:36:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Mukund](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e8c25b/32.png) [@Mukund](https://www.ruby-forum.com/u/Mukund)\ **Post date:** [December 9, 2007, 8:36pm UTC](https://www.ruby-forum.com/t/cannot-freeze-gems/122579/1 "2007-12-09T20:36:19Z")
I am facing the following issue since Rails 2 was released. I need to freeze 1.2.6 and I can’t. The error messages are below. For the record, the rails application works fine via Mongrel. I just can’t freeze the gems. These are on Fedora 7. $ rake rails:freeze:gems VERSION=1.2.6 --trace (in /work/aptana/workspace/avls) \*\* Invoke rails:freeze:gems (first\_time) \*\* Execute rails:freeze:gems Freezing to the gems for Rails 1.2.6 rake aborted! uninitialized constant Gem::GemRunner /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:2028:in `const_missing' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake:26 /usr/lib64/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake: 25:in`each’ /usr/lib64/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake:25 /usr/lib/ruby/1.8/fileutils.rb:121:in `chdir' /usr/lib/ruby/1.8/fileutils.rb:121:in`chdir’ /usr/lib64/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake:24 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`execute’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`execute’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in`synchronize’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in`top\_level’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in`top\_level’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in`top\_level’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in`standard\_exception\_handling’ /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7 /usr/bin/rake:16:in`load’ /usr/bin/rake:16 * * * moreover, I get the following odd errors. they were fine before # gem --version 0.9.5 # gem install rails --version=1.2.6 Successfully installed rails-1.2.6 1 gem installed # rails --version /usr/lib/ruby/site\_ruby/1.8/rubygems.rb:377:in `report_activate_error': Could not find RubyGem activeresource (= 2.0.1) (Gem::LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:309:in`activate’ from /usr/lib/ruby/site\_ruby/1.8/rubygems.rb:335:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:334:in`each’ from /usr/lib/ruby/site\_ruby/1.8/rubygems.rb:334:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:76:in`active\_gem\_with\_options’ from /usr/lib/ruby/site\_ruby/1.8/rubygems.rb:50:in `gem’ from /usr/bin/rails:18 ---
**Author:** ![Mukund](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e8c25b/32.png) [@Mukund](https://www.ruby-forum.com/u/Mukund)\ **Post date:** [December 9, 2007, 8:41pm UTC](https://www.ruby-forum.com/t/cannot-freeze-gems/122579/2 "2007-12-09T20:41:35Z")
This is a known issue and it is fixed in Rails edge (change set 8336). Regards, Nicolai ---
**Author:** ![Mukund](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/e8c25b/32.png) [@Mukund](https://www.ruby-forum.com/u/Mukund)\ **Post date:** [December 10, 2007, 7:45am UTC](https://www.ruby-forum.com/t/cannot-freeze-gems/122579/3 "2007-12-10T07:45:34Z")
Thanks Nicolai. Can we expect a Rails 1.2.6.x or 1.2.7 that addresses this problem by the end of December? I assume when you say edge, it is for the 2.0.x code base. Regards, Mukund