Project

General

Profile

Actions

Bug #1352

closed

Missing gems in Bundler when using Passenger

Added by Greg Sutcliffe over 12 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Low
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

This refers to the rails3 branch.

It seems Bundler installs the two "git gems" to /var/lib/gems/1.8/bundler/gems. When running "script/rails s", as root, that seems fine, but when it comes to firing up the rails3 branch under Passenger, it fails with something like:

A workaround is to link the bundler gems to the main directory. At the time of writing (since the directories contain git checksums) the following workaround was used:

  1. ln -snf /var/lib/gems/1.8/bundler/gems/has_many_polymorphs-36f15d24ca42 /var/lib/gems/1.8/gems/has_many_polymorphs
  2. ln -snf /var/lib/gems/1.8/bundler/gems/safemode-77d53c3c5271 /var/lib/gems/1.8/gems/safemode

Passenger then started happily. It's only a workaround though - since "script/rails s" works, I suspect there's a pathname or environment issue in Passenger itself.

For reference, this is on Debian Wheezy, Rubgems 1.3.7

Actions #1

Updated by Greg Sutcliffe almost 12 years ago

  • Status changed from New to Assigned
  • Assignee changed from Ohad Levy to Greg Sutcliffe
  • Priority changed from Normal to Low

I'll test this at some point - I don't think it happens any more, but since I mentioned wheezy back then, I should re-test on wheezy.

Actions #2

Updated by Benjamin Papillon almost 11 years ago

  • Status changed from Assigned to Closed

Not relevant anymore

Actions

Also available in: Atom PDF