Control: severity -1 wishlist Control: tag -1 + wontfix On Thu, Feb 16, 2017 at 01:10:18PM +0000, Daniel Pocock wrote: > Package: redmine > Version: 3.3.1-2 > Severity: important > > > I upgraded a system from jessie to stretch > > The upgrade of the redmine package fails with the error below > > The system has ruby-json 2.0.1+dfsg-3 > > > Setting up redmine (3.3.1-2) ... > dbconfig-common: writing config to > /etc/dbconfig-common/redmine/instances/default.conf > dbconfig-common: flushing administrative password > Your bundle is locked to json (2.0.3), but that version could not be > found in any of the sources listed in your Gemfile. If you haven't > changed sources, that means the author of json (2.0.3) has removed it. > You'll need to update your bundle to a different version of json (2.0.3) > that hasn't been removed in order to install. > Run `bundle install` to install missing gems. > dpkg: error processing package redmine (--configure): > subprocess installed post-installation script returned error exit status 7 > Errors were encountered while processing: > redmine > E: Sub-process /usr/bin/dpkg returned an error code (1)
Your system has ruby-json 2.0.1 but the error message says "Your bundle is locked to json (2.0.3)". This happens when you have plugins installed and you pulled their arbitrary dependencies on top of the debian packages, so you end up with an unsupportable configuration. To fix your system, you can try: - removing /var/lib/redmine/Gemfile.lock and trying the upgrade again or - removing the plugins you have installed, doing the upgrage, them reinstalling them
signature.asc
Description: PGP signature
