Source: redmine Version: 3.0~20140825-8~deb8u1 Severity: normal In postinst the Gemfile is created. Creation seems to use /etc/redmine/default/database.yml to find gems to include. In my case that file did not exist because I did not create a default instance, only one with a real name. The resulting Gemfile did not include the 'pg' gem. This caused an error since my instance does use a postgresql database for the backend.
Errors I got: Please configure your config/database.yml first Populating database for redmine instance "hnjs". This may take a while. Please configure your config/database.yml first Please configure your config/database.yml first rake aborted! Gem::LoadError: Specified 'postgresql' for database adapter, but the gem is not loaded. Add `gem 'pg'` to your Gemfile (and ensure its version is at the minimum required by ActiveRecord). Gem::LoadError: pg is not part of the bundle. Add it to Gemfile. Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) Error when running rake db:migrate, check database configuration. The workaround that worked for me: mkdir /etc/redmine/default && cp /etc/redmine/hnjs/database.yml /etc/redmine/default/database.yml dpkg-reconfigure redmine If my interpretation of the problem is correct: is it even possible to have multiple instances use different database backends or will the bundle-stuff only include the gem needed for the backend in the default instance? Cheers henk -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
pgp6ia7ImOQkR.pgp
Description: OpenPGP digital signature
