2014-09-03 55 views
0

我安裝了用於維護客戶端舊版代碼的Rails 2.3.8。問題是,我不能運行捆綁安裝,因爲它產生了以下錯誤失敗後:Ruby on Rails - Bundler無法找到適用於gem「activerecord」的兼容版本

Bundler could not find compatible versions for gem "activerecord": 
    In Gemfile: 
    rails (= 2.3.8) ruby depends on 
     activerecord (= 2.3.8) ruby 

    activerecord (2.3.11) 

我Gmefile是

source :gemcutter 

# == Application Gems 
gem "rails", "2.3.8" 
gem "activesupport" 
gem "mysql", "2.8.1" 
gem "devise", "1.0.8" 
gem "inherited_resources", "1.0.6" 
gem "will_paginate", "2.3.14" 
gem "canable", "0.1.1", :require => 'canable' 
gem "aasm", "2.1.5", :require => "aasm" 
gem "fastercsv", "1.5.3", :require => 'fastercsv' 
gem "jnunemaker-validatable", :require => 'validatable' 
gem "thinking-sphinx", "1.3.18" 
gem "delayed_job", "2.1.0.pre" 
gem "ts-delayed-delta", "1.1.0", :require => "thinking_sphinx/deltas/delayed_delta" 
gem "erubis" 
gem "cloudfiles" 
gem 'hoptoad_notifier' 
gem 'aws-s3' 
gem 'json' 
gem 'cocaine' 
gem 'fog', '~> 0.9.0' 

# requires exiftool (command line utility) to be installed! 
# http://www.sno.phy.queensu.ca/~phil/exiftool/install.html 
gem "mini_exiftool", "2.4.2" 
gem "rack-killswitch" 
gem "carmen" 
gem "rest-client" 

# == Deployment Gems 
gem "capistrano" 
gem "capistrano-ext" 

# Visual email testing in the browser 
gem "mail_view", :group => :development 

# == Test Gems 
group :test do 
    gem "shoulda", "2.11.1" 
    gem "machinist", "1.0.3" 
    gem "faker", "0.3.1" 
    gem "mocha", "0.9.8" 
    gem "timecop", "0.3.4" 
    gem "cucumber", "0.8.5" 
    gem "cucumber-rails", "0.3.2" 
    gem "webrat" # needed for cucumber 
    gem "database_cleaner", "0.5.0" # needed for cucumber 
    gem "sinatra", "1.0" 
    gem "rack-contrib" 
    gem "artifice" 
end 

我已經加入gem "activerecord", "2.3.8"沒有成功,因爲它接着說,捆綁已被鎖定到2.3.11。

是否有人能夠勝任。

+0

這是一個全新的Gemfile嗎?還是你修改它,以便它以前有'gem「rails」,「2.3.11」',現在它有'2.3.8'? – 2014-09-03 14:06:06

回答

0

嘗試

bundle update activerecord

應該處理的活動記錄的特定版本

賠率是其他寶石之一鎖定你到Rails 2.3.11(ActiveRecord的2.3.11)。你可以看到什麼取決於Gemfile.lock中的內容。

另一個選項是刪除Gemfile.lock並再次運行包。

+0

你可能也應該改變你的來源到rubygems! – 2014-09-03 14:05:20

相關問題