Package: redmine
Version: 3.0~20140825-8~deb8u2
Severity: serious
Quack,
Migration fails with:
===================================================================
Setting up redmine (3.0~20140825-8~deb8u2) ...
Please configure your config/database.yml first
Populating database for redmine instance "dc".
This may take a while.
Please configure your config/database.yml first
Please configure your config/database.yml first
rake aborted!
Gem::LoadError: Specified 'mysql2' for database adapter, but the gem is
not loaded. Add `gem 'mysql2'` to your Gemfile (and ensure its version
is at the minimum required by ActiveRecord).
Gem::LoadError: mysql2 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.
dpkg: error processing package redmine (--configure):
subprocess installed post-installation script returned error exit
status 1
===================================================================
After investigation, the postinst properly loops on my
redmine/current-instances, so this is well, but unfortunately the new
magical Gemfile is not passed the instance name, thus using "default" as
default instance name.
In my case I don't have a "default" instance (which is permitted via
debconf), but anyway each instance could have a different adapter so
this will fail in some non-exotic configurations. So it seems a
different Gemfile.lock should probably be generated for each instance,
with the X_DEBIAN_SITEID set by the postinst. Or maybe if there is no
possible conflict have the Gemfile loop on all database config files and
load all necessary adapters.
Regards.
--
Marc Dequènes
