Freezing Rails 1.2.6 & rubygems 0.95 Problems

Freezing to 1.2.6 appears to be broken right now for two reasons. My
environment is using rails 1.2.6 and rubygems 0.9.5 Attempting to
freeze to 1.2.6 with this will result in this output & error:

% rake rails:freeze:edge TAG=rel_1-2-6

** Invoke rails:freeze:edge (first_time)
** Execute rails:freeze:edge
A vendor/rails/railties

. . .

A vendor/rails/activesupport/MIT-LICENSE
A vendor/rails/activesupport/README
Exported revision 8214.
svn: URL ‘http://dev.rubyonrails.org/svn/rails/tags/rel_1-2-6/
activeresource’ doesn’t exist

To fix this, you need to edit the …/PATH_TO_RAILS/lib/tasks/
framework.rake file and remove activeresource from the for loop here:

  for framework in %w(railties actionpack activerecord

actionmailer activesupport activeresource)

=============================================

The next problem I had appears to be a result of another bug in the
1.2.6 version of framework.rake. Here I attempt to do the freeze and
it fails:

(ghtrp03) ~/suites/staging/cm % rake rails:freeze:gems --trace
/usr/local/lib/ruby/site_ruby/1.8
/usr/local/lib/ruby/site_ruby/1.8/i386-freebsd7
/usr/local/lib/ruby/site_ruby
/usr/local/lib/ruby/1.8
/usr/local/lib/ruby/1.8/i386-freebsd7
.
(in /usr/home/dmack/suites/staging/cm)
** 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/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:2028:in
const_missing' /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake: 26 /usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake: 25:ineach’
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake:
25
/usr/local/lib/ruby/1.8/fileutils.rb:121:in chdir' /usr/local/lib/ruby/1.8/fileutils.rb:121:inchdir’
/usr/local/lib/ruby/gems/1.8/gems/rails-1.2.6/lib/tasks/framework.rake:
24
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:inexecute’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:inexecute’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in
invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:insynchronize’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in
invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:intop_level’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in
each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:intop_level’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in
standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:intop_level’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:instandard_exception_handling’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7 /usr/local/bin/rake:20:inload’
/usr/local/bin/rake:20

Fixing this was mentioned in another thread on this list. Just add
the line:

  require 'rubygems/gem_runner'

below the line:

  require 'rubygems'

in framework.rake.

After doing that, all is well:

(ghtrp03) ~/suites/staging/cm % rm -rf vendor/rails
(ghtrp03) ~/suites/staging/cm % rake rails:freeze:gems --trace
/usr/local/lib/ruby/site_ruby/1.8
/usr/local/lib/ruby/site_ruby/1.8/i386-freebsd7
/usr/local/lib/ruby/site_ruby
/usr/local/lib/ruby/1.8
/usr/local/lib/ruby/1.8/i386-freebsd7
.
(in /usr/home/dmack/suites/staging/cm)
Freezing to the gems for Rails 1.2.6
Unpacked gem: ‘activesupport-1.4.4’
Unpacked gem: ‘activerecord-1.15.6’
Unpacked gem: ‘actionpack-1.13.6’
Unpacked gem: ‘actionmailer-1.3.6’
Unpacked gem: ‘actionwebservice-1.2.6’
Unpacked gem: ‘rails-1.2.6’

Does this stuff get tested before release? At least add it to the
release notes.

Dan

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs