rake aborted! no such file to load -- merb-core/dispatch/session

[cparratto]

I have been unable to get rubytime up and running. I'm sure I am going something wrong. I get the following:

sudo bundle exec rake db:automigrate --trace
(in /opt/bitnami/projects/rubytimenotstable)
Merb root at: /opt/bitnami/projects/rubytimenotstable
Loading init file from ./config/init.rb
Loading ./config/environments/development.rb
DataMapper::Resource.append_inclusions is deprecated, use DataMapper::Model.append_inclusions instead (/opt/bitnami/ruby/lib/ruby/gems/1.8/bundler/gems/merb_dm_xss_terminate-5ee5f92/lib/merb_dm_xss_terminate.rb:7)
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rcov_stats-2.0.1/lib/rcov_stats.rb:6: warning: already initialized constant TYPES
** Invoke db:automigrate (first_time)
** Invoke merb_env (first_time)
** Execute merb_env
Merb root at: /opt/bitnami/projects/rubytimenotstable
Loading ./config/environments/rake.rb
~ Loaded RAKE Environment...
rake aborted!
no such file to load -- merb-core/dispatch/session
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core/bootloader.rb:582:in require' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core/bootloader.rb:582:inrun'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core/bootloader.rb:97:in run' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core/server.rb:172:inbootup'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core/server.rb:42:in start' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core.rb:165:instart'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/merb-core-1.1.0.pre/lib/merb-core.rb:178:in start_environment' /opt/bitnami/projects/rubytimenotstable/Rakefile:24 /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:incall'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in execute' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:ineach'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in execute' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:ininvoke_with_call_chain'
/opt/bitnami/ruby/lib/ruby/1.8/monitor.rb:242:in synchronize' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:ininvoke_with_call_chain'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in invoke_prerequisites' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:ineach'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in invoke_prerequisites' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:ininvoke_with_call_chain'
/opt/bitnami/ruby/lib/ruby/1.8/monitor.rb:242:in synchronize' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:ininvoke_with_call_chain'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in invoke' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:ininvoke_task'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in top_level' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:ineach'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in top_level' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:instandard_exception_handling'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in top_level' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:inrun'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in standard_exception_handling' /opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:inrun'
/opt/bitnami/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/opt/bitnami/ruby/bin/rake:19:in `load'
/opt/bitnami/ruby/bin/rake:19

Any ideas on how to address this?

[mackuba]

This looks very strange, that file (merb-core/dispatch/session) seems to be in merb-core gem, so it should have found it if it found other files from that gem...

Why are you running the command with sudo? Maybe it will work if you call it as a standard user?

Or maybe for some reason the gem wasn't installed properly? In this case, it should help if you uninstall it and reinstall again...