ruby-activerecord-3.2 depends on wrong version of ruby-arel and ruby-tzinfo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rails (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
ruby-activerecord-3.2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
How to reproduce : install clean Trusty LTS,
then install ruby-rack1.4 to avoid conflicts with ruby-rack (see bug lp:1319367),
then install rails (2:3.2.13+1, component versions 3.2.16-1).
Then run 'rails new something' to create a new Rails project.
Then install : ruby-jquery-rails , ruby-coffee-rails , ruby-sqlite3 , ruby-sass-rails , ruby-uglifier so that 'rails new' can continue.
Then remove directory 'something' and run 'rails new something' again
On the step 'run bundle install --local' , get a message :
Resolving dependencies...
Could not find gem 'arel (~> 3.0.2) ruby', which is required by gem 'rails (= 3.2.16) ruby', in any of the sources.
Check ruby-arel version and find that it is 4.0.0-2. Go to http://
Repeat: remove directory 'something' , run 'rails new something'. Get a message :
Could not find gem 'tzinfo (~> 0.3.29) ruby', which is required by gem 'rails (= 3.2.16) ruby', in any of the sources.
See that its version is 1.1.0-1 in Trusty. Go to http://
Repeat: 'rm -r something ; rails new something'. Now it finally completes normally. Just remember that you can't run 'safe-upgrade' on your system because new Trusty .debs will break gem dependencies again.
I would appreciate more care about having working Rails in Ubuntu 14.04. It's an LTS release after all.
I will repeat the same test case under Debian Wheezy and Debian Sid to give you a sample for comparison.
Probably some Debian Sid fixes should be integrated into Ubuntu LTS.
Status changed to 'Confirmed' because the bug affects multiple users.