Phusion Passenger Throwing Error After Upgrading Gems

Question

I am currently running Redmine, and while updating the gems, Phusion Passenger is throwing errors that it is unable to locate the required libraries. It seems that it keeps looking for the older gems, and not the newer ones.

After updating the gems, I run the command:

gem cleanup

to remove all older gems that should not be needed anymore.

Unfortunately, despite the fact that newer gems are installed, Phusion Passenger is throwing the following error:

Could not find activesupport-3.2.11 in any of the sources (Bundler::GemNotFound)

activesupport-3.2.12 has been installed, however.

To temporarily resolve the issue, I needed to install the older version back. Unfortunately, I needed to install all of the older versions of the dependencies... Is there a way to get Phusion Passenger to see the newer versions of the required gems? I don't really know much about Ruby, Rails, or gems, so I appreciate any assistance I get on this issue.

Thank You

EDIT: Per request, here is the output for gem dependency activesupport -reverse-dependencies:

Gem activesupport-3.2.12
  i18n (~> 0.6)
  multi_json (~> 1.0)
  Used by
    actionpack-3.2.12 (activesupport (= 3.2.12))
    activemodel-3.2.12 (activesupport (= 3.2.12))
    activerecord-3.2.12 (activesupport (= 3.2.12))
    activeresource-3.2.12 (activesupport (= 3.2.12))
    rails-3.2.12 (activesupport (= 3.2.12))
    railties-3.2.12 (activesupport (= 3.2.12))
    treetop-1.4.12 (activesupport (>= 0, development))

EDIT: I think I found the source of my problems: The Gemfile and the Gemfile.lock that is in the Redmine directory. In the Gemfile.lock file, it lists the following:

specs:
    actionmailer (3.2.11)
    actionpack (= 3.2.11)
    mail (~> 2.4.4)
    actionpack (3.2.11)
    activemodel (= 3.2.11)
    activesupport (= 3.2.11)
    builder (~> 3.0.0)
    erubis (~> 2.7.0)
    journey (~> 1.0.4)
    rack (~> 1.4.0)
    rack-cache (~> 1.2)
    rack-test (~> 0.6.1
    ...

So, this is likely the file that is causing all the issues... Now, how to fix this?

Answer 1

You'll have to do the following:

Open the Redmine Gemfile (should be located at root of the redmine project). In that file, you'll update the desire gems. In the terminal, go to the root of the Redmine project (same level where the Gemfile is located) and there do a bundle install. That will update your gems and Replace your Gemfile.lock with a new one listing the new gems.