Hi you all! I’ve got Mongrel saying this when I use the localization
simplified plug-in: any idea?
** Loading any Rails specific GemPlugins
Exiting
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:92:in
load_specification': /Users/stratboy/Documents/05_SAMPLES/RAILS/newser/vendor/plugins/l10n-simplified-0.8/lib/localization_simplified.rb:13:ingsub!’: can’t convert nil into String (TypeError)
from
/Users/stratboy/Documents/05_SAMPLES/RAILS/newser/vendor/plugins/l10n-simplified-0.8/lib/localization_simplified.rb:13:in
localize_strftime' from /Users/stratboy/Documents/05_SAMPLES/RAILS/newser/vendor/plugins/l10n-simplified-0.8/lib/localization_simplified.rb:191:instrftime’
from
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:13:in
today' from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:314:indate=’
from
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:416:in
send' from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:416:ininitialize’
from
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:412:in
each' from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/specification.rb:412:ininitialize’
… 31 levels…
from
/opt/local/lib/ruby/gems/1.8/gems/rails-1.2.4/lib/commands/server.rb:39
from
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in
gem_original_require' from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:inrequire’
from script/server:3
What version of Rubygems do you have?
Evan
Hi! I don’t how to find it. I can say that I’m running rails 1.2.4 on
ruby 1.8.6 (2007-03-13 patchlevel 0)
Evan W. wrote:
What version of Rubygems do you have?
Evan
Can you try it with the Rubygems beta? Run:
$ gem update --system --source http://segment7.net/
I could’t reproduce your issue using the beta so perhaps it was a gem
problem that is already fixed.
Evan
Yes I can try, but excuse me, I’m not an expert, so I’m quite afraid of
running that command: can that update run my mac or rails installation
into some kind of trouble if something goes wrong? By the way, I’ve used
macports to install ruby and rails.
Evan W. wrote:
Can you try it with the Rubygems beta? Run:
$ gem update --system --source http://segment7.net/
I could’t reproduce your issue using the beta so perhaps it was a gem
problem that is already fixed.
Evan
It worked before, than suddenly stopped… 
Evan W. wrote:
I haven’t had any trouble with 0.9.5.6, but it’s a valid concern.
What version of Mongrel are you using? Did the plugin work before, and
now is broken, or did it never work?
Evan
Did it stop after you upgraded Mongrel? Or did you not upgrade.
I haven’t had any trouble with 0.9.5.6, but it’s a valid concern.
What version of Mongrel are you using? Did the plugin work before, and
now is broken, or did it never work?
Evan
p.s.
I did not upgraded mongrel. At least I don’t think so.
I’m sorry I was upgrading the gems while you’re writing. I’ve just
upgraded rails to 1.2.5 too. Now, if I run rails -v, I’ve got this error
/opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:367:in
report_activate_error': RubyGem version error: activesupport(1.4.1 not = 1.4.4) (Gem::LoadError) from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:299:inactivate’
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:325:in
activate' from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:324:ineach’
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:324:in
activate' from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:76:inactive_gem_with_options’
from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:50:in `gem’
from /opt/local/bin/rails:18
Evan W. wrote:
Did it stop after you upgraded Mongrel? Or did you not upgrade.
On 10/27/07, Luca R. [email protected] wrote:
I’m sorry I was upgrading the gems while you’re writing. I’ve just
upgraded rails to 1.2.5 too. Now, if I run rails -v, I’ve got this error
/opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:367:in
`report_activate_error’: RubyGem version error: activesupport(1.4.1 not
= 1.4.4) (Gem::LoadError)
That seems to be a issue with the versions of activesupport and rails
installed.
could you list the gems you have?
gem list rails
gem list activesupport
gem deps rails -v ‘1.2.5’
The last command should list you what gems of activesupport,
actionpack and activerecord is using, but I guess all is related to
that.
Also, did you updated the config/environment.rb to match the new
installed gems prior doing the rake rails:update in your
application?
(That is documented in the Ruby on Rails weblog about the upgrade
procedure.
–
Luis L.
Multimedia systems
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
Maybe I’ve updated to 1.2.4 the wrong way too…
gem list rails
rails (1.2.5, 1.2.4, 1.2.3, 1.2.2)
gem list activesupport
activesupport (1.4.3, 1.4.2, 1.4.1)
gem deps rails -v ‘1.2.5’
ERROR: While executing gem … (RuntimeError)
Unknown command deps
Also, did you updated the config/environment.rb to match the new
installed gems prior doing the rake rails:update in your
application?
Well, no…
I updated rail via “sudo gem update rails -y” and did nothing else.
I’ve just read the weblog, but since I’ve not used gem install rails,
what should I do now?
Best way to proceed is to uninstall all gem versions of Rails,
ActiveSupport, ActionPack, ActiveRecord, ActionMailer, and
ActionWebService from your system, and then run ‘gem install rails’
again. This makes sure that the only available versions of Rails are
the latest ones, and avoids activation conflicts.
Evan
Theoretically you should be able to keep multiple versions at a time,
but it doesn’t really work so well for Rails in practice because its
dependency tree is deep.
Many people export the repository release tags into /vendor/rails
instead of using the gems. This guarantees that each app uses only its
individual version of Rails.
Evan
Ok thank you. I’ll try and let you know. Really thank you for your
support!
Luca
Evan W. wrote:
Theoretically you should be able to keep multiple versions at a time,
but it doesn’t really work so well for Rails in practice because its
dependency tree is deep.
Many people export the repository release tags into /vendor/rails
instead of using the gems. This guarantees that each app uses only its
individual version of Rails.
Evan
Done. Now all is running perfect. THANK YOU ALL, VERY MUCH!!! :):)
Evan W. wrote:
Theoretically you should be able to keep multiple versions at a time,
but it doesn’t really work so well for Rails in practice because its
dependency tree is deep.
Many people export the repository release tags into /vendor/rails
instead of using the gems. This guarantees that each app uses only its
individual version of Rails.
Evan
Time#today was removed from RubyGems, so the suggestion on this blog
post might fix your problem:
http://blog.segment7.net/articles/2007/10/08/time-today-going-away