Control: forcemerge -1 767548 Hello,
On Wed, Nov 26, 2014 at 04:57:39PM +1100, Dmitry Smirnov wrote: > Package: redmine > Version: 3.0~20140825-1 > Severity: normal > > (Re-)installing Redmine in "Jessie" produced the following error: > > ~~~~ > Setting up redmine (3.0~20140825-1) ... > dbconfig-common: writing config to > /etc/dbconfig-common/redmine/instances/default.conf > > Creating config file /etc/redmine/default/database.yml.new with new version > dbconfig-common: flushing administrative password > Populating database for redmine instance "default". > This may take a while. > Could not find sprockets-2.12.1 in any of the sources > Run `bundle install` to install missing gems. > 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 > Errors were encountered while processing: > redmine > ~~~~ > > I don't quite understand where this problem is coming from. > I experienced it on the instance of Redmine which was once upgraded > from the earlier version. I could not reproduce this issue with new > instance of Redmine... The problem is that at the first install, the Gemfile.lock gets the versions of packages that were installed then, and will forever expect those exact versions (which is obviously broken). A workaround is to symlink Gemfile.lock to /dev/null: ln -sfT /dev/null /usr/share/redmine/Gemfile.lock This change (having Gemfile.lock as a symlink to /dev/null) has been committed to git and will upload as soon as I manage to include fixes for other important bugs. -- Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
