Even simple application (using Passenger, I hope it’s Rails’ and not Passenger’s fault) can’t be launched without it dying to error: Could not find gem 'sqlite3-ruby (>= 0, runtime)' in any of the gem sources listed in your Gemfile. (Bundler::GemNotFound) Reproducible: Always Steps to Reproduce: 1. Install rails 3.0.3 2. Do new app (rails new foo) 3. Try to launch it Actual Results: Error str specified above Expected Results: It should work
Do you have sqlite3-ruby installed? Does it help to install it manually?
Yup, fixed by installing it manually. Sorry, forgot to mention it.
It looks like sqlite3 is provided in the default config/database.yml, but this obviously won't work if you don't have the sqlite3 USE flag set when emerging activerecord. I'm not sure we should fix this, since folks who don't want sqlite3 on their system should just select a different database with 'rails new -d <database>'. I'm closing this as WONTFIX, please feel free if you have a different viewpoint or if I missed something.
Hmm, maybe there should be an useflag that would just pull the dependency?
That USE flag is already defined for activerecord, so if you have sqlite3 set and emerge all of rails then things should work as expected even with the example database.yml.
Okay, this is getting even more strange... Should I just open new bug? This time, sqlite3-ruby inside the tree didn’t help, because its name is ”sqlite3-ruby”. Instead installing ”sqlite3” using rubygems installed correctly named sqlite3 plugin to get Rails running.
I'm not sure if this is the same problem you had initially, but I have seen this as well. It's due to a discrepancy between the name of the sqlite gem and our ruby-sqlite package. The solution is to rename the package for Gentoo, which is on my todo list.
(In reply to comment #7) > I'm not sure if this is the same problem you had initially, but I have seen > this as well. It's due to a discrepancy between the name of the sqlite gem and > our ruby-sqlite package. The solution is to rename the package for Gentoo, > which is on my todo list. Actually it turns out that this is already fixed with dev-ruby/sqlite3-ruby-1.3.3. I've now made activerecord 3.0.7 depend on that version.