Hi Marius,

makes sense! So based on what you said, I've been plunging into trying to get 
'next' to run today, and as I (hopefully) make progress, I'll be reporting / 
asking about any problems I encounter. With the caveat that I'm not a ruby guy, 
so some things may be very obvious to everybody other than me...

To get this started: mysql vs mysql2, apparently that got upgraded. But when 
doing a 'bundle install', I'm getting:

*** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (Please 
install the mysql adapter: `gem install activerecord-mysql-adapter` (mysql is 
not part of the bundle. Add it to Gemfile.))

activerecord-mysql-adapter is not listed in the Gemfile. I tried to add 
activerecord-mysql2-adapter to stay with mysql2, but that does not make it 
better. So I added activerecord-mysql-adapter, which then also requires mysql, 
which seems to mean that I have now two versions of the same database driver? 
That does not seem to be right.

Here's the stack trace via Passenger. What might be wrong here?

[ pid=5486 thr=8338960 file=utils.rb:176 time=2013-03-15 20:01:36.930 ]: *** 
Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (Please 
install the mysql adapter: `gem install activerecord-mysql-adapter` (mysql is 
not part of the bundle. Add it to Gemfile.)) (process 5486, thread 
#<Thread:0x00000000fe7c20>):
        from 
/var/lib/gems/1.9.1/gems/bundler-1.3.4/lib/bundler/rubygems_integration.rb:214:in
 `block in replace_gem'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/connection_adapters/mysql_adapter.rb:5:in
 `<top (required)>'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in
 `require'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in
 `block in require'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:236:in
 `load_dependency'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/dependencies.rb:251:in
 `require'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:in
 `resolve_hash_connection'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:41:in
 `resolve_string_connection'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:25:in
 `spec'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/connection_adapters/abstract/connection_specification.rb:130:in
 `establish_connection'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/railtie.rb:82:in
 `block (2 levels) in <class:Railtie>'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/lazy_load_hooks.rb:36:in
 `instance_eval'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/lazy_load_hooks.rb:36:in
 `execute_hook'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/lazy_load_hooks.rb:26:in
 `block in on_load'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/lazy_load_hooks.rb:25:in
 `each'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activesupport-3.2.12/lib/active_support/lazy_load_hooks.rb:25:in
 `on_load'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/activerecord-3.2.12/lib/active_record/railtie.rb:74:in
 `block in <class:Railtie>'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/initializable.rb:30:in
 `instance_exec'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/initializable.rb:30:in
 `run'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/initializable.rb:55:in
 `block in run_initializers'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/initializable.rb:54:in
 `each'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/initializable.rb:54:in
 `run_initializers'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/application.rb:136:in
 `initialize!'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/gems/ruby/1.9.1/gems/railties-3.2.12/lib/rails/railtie/configurable.rb:30:in
 `method_missing'
        from 
/usr/cldstr/cldstr.com/gitorious/ws/mainline/config/environment.rb:5:in `<top 
(required)>'

Thanks,


Johannes.


On Mar 15, 2013, at 7:30, Marius Mårnes Mathiesen <[email protected]> 
wrote:

> [email protected] writes:
>> How stable is V3.0 / next? Any idea when it will be stable enough to run
>> real projects with?
> 
> Johannes,
> It's been a while :-)
> 
> I don't remember if we've communicated this earlier, but we made some
> changes to our original plan. Our original plan was to first launch 3.0,
> basically with no new features but based on Rails 3.x (current), and
> after that launch a new code browser, a feature which required us to
> upgrade our dependencies to Rails 3.
> 
> After quite a lot of struggling to make the new code browser work
> asyncronously within Rails we decided to:
> - make the code browser synchronous (simply too painful to run an async
>  Rack app within Rails)
> - include the new code browser in Gitorious 3
> 
> After all, releasing a new major version practically without any new
> user-facing features doesn't make a lot of sense.
> 
> There are currently a few other tasks blocking :-) item #1 on the list,
> but we hope to get there soon(ish).
> 
> That being said, we've been running the next branch of Gitorious (which
> is what was meant to become 3.0) without any showstoppers on our
> internal server for quite a while, and we promise to help with any
> issues you may find in doing the same. But we'll be saving the 3.0 label
> for the new code browser.
> 
> Cheers,
> - Marius
> 
> -- 
> -- 
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Gitorious" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to