Btw, ruby-activesupport-3.2 should be made dependent on ruby-test-unit
Without that package installed, 'rails console' in a newly-created Rails project gives :
/usr/lib/ruby/vendor_ruby/active_support/test_case.rb:12:in `<module:ActiveSupport>': uninitialized constant Test (NameError)
After its installation, the message changes into :
/usr/lib/ruby/vendor_ruby/active_support/test_case.rb:12:in `<module:ActiveSupport>': uninitialized constant Test::Unit::TestCase (NameError)
And as described in Debian bug 738747, adding a line : require 'test/unit' in the beginning of the file /usr/lib/ruby/vendor_ruby/active_support/test_case.rb eliminates the exception and fixes startup of 'rails console'
So, please, I hope you know what to do.
Btw, ruby-activesupp ort-3.2 should be made dependent on ruby-test-unit
Without that package installed, 'rails console' in a newly-created Rails project gives :
/usr/lib/ ruby/vendor_ ruby/active_ support/ test_case. rb:12:in `<module: ActiveSupport> ': uninitialized constant Test (NameError)
After its installation, the message changes into :
/usr/lib/ ruby/vendor_ ruby/active_ support/ test_case. rb:12:in `<module: ActiveSupport> ': uninitialized constant Test::Unit: :TestCase (NameError)
And as described in Debian bug 738747, adding a line : ruby/vendor_ ruby/active_ support/ test_case. rb
require 'test/unit'
in the beginning of the file
/usr/lib/
eliminates the exception and fixes startup of 'rails console'
So, please, I hope you know what to do.