Bundler could not find compatible versions for gem "i18n": - ruby-on-rails-4

im a noob. i need help.
im trying to install Redmine CRM plugin however im getting an error when i run this:
bundle install --without development test
it says:
Bundler could not find compatible versions for gem "i18n":
In Gemfile:
rails (= 4.2.0) ruby depends on
railties (= 4.2.0) ruby depends on
activesupport (= 4.2.0) ruby depends on
i18n (~> 0.7) ruby
money (~> 5.1.0) ruby depends on
i18n (~> 0.6.0) ruby

Redmine CRM plugin has to be upgraded to newer versions of redmine in parallel. I recommend to upgrade redmine first (with an empty plugins directory) and then add the redminecrm plugins and upgrade them too.
Redmine CRM Plugin 4.0.3 is compatible with Redmine 2.6-3.1
Older versions of the Redmine CRM Plugin installed on Redmine 3.1 result in the error you posted.

In your Gemfile, manually specify I18n gem like
gem 'I18n', '~0.6.0'

Related

Upgrade redmine from 1.0.1 to 3.1.1

I want to upgrade from 1.0.1 to 3.1.1
what are the steps? and what is prerequists to install 3.1.1?
what is ruby version and gem is compatible with 3.1.1 ?
thnx in advanced
Redmine 3 runs Rails 4 so it's prerequisites apply. You should at least run Ruby 2.0.
Redmine itself is easily upgraded,
everything else depends on which plugins you are running if any, and if these are still maintained and available in a version compatible with Redmine 3.1.

Activeadmin bundle error

I am having this error when trying to bundle install. From what I understand it says activeadmin gem depends on metasearch 0.9.2 and metasearch gem depends on activerecord 3.1.0 but rails 4.1.0 depends on activercod 4.1.0. so what is my course of action for this?
Bundler could not find compatible versions for gem "activerecord":
In Gemfile:
activeadmin (>= 0) ruby depends on
meta_search (>= 0.9.2) ruby depends on
activerecord (~> 3.0.0.rc2) ruby
rails (= 4.1.0) ruby depends on
activerecord (4.1.0)
We're currently working on 1.0.0, which as far as dependencies, moves
us from meta_search to Ransack and adds Rails 4 support. You can get
Rails 4 and 4.1 support by tracking master:
gem 'activeadmin', github: 'activeadmin'
https://github.com/activeadmin/activeadmin

Bundler could not find compatible versions for jquery-ui-rails

I've created a new gemset, then, when I try to bundle install, I get this error:
Bundler could not find compatible versions for gem "jquery-ui-rails":
In Gemfile:
activeadmin (>= 0) ruby depends on
jquery-ui-rails (~> 5.0) ruby
alchemy_cms (~> 3.0.0.rc5) ruby depends on
jquery-ui-rails (4.1.1)
Although, I've apt-get update, any help?
remove the version constrain from alchemy_cms in Gemfile and run:
bundle update

Why is uglifier gem in default Rails Gemfile still of version 1.3.0?

When creating a new Rails 4 app the default Gemfile has this in the gem list:
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
This despite that the last official version of uglifier being 2.4.0
Am I missing something here or why the discrepancy in versions?
The bundler version specifier '>= 1.3.0' means at least version 1.3.0 should be accepted. In other words, using the current version 2.4.0 is just fine.
In fact, that's the installed version you're going to have when starting a new application from scratch. Just check your Gemfile.lock file for the actual installed versions of gems in your bundle. You'll probably find something like this:
uglifier (2.4.0)
execjs (>= 0.3.0)
json (>= 1.8.0)
Which means you have uglifier 2.4.0.
More info: http://guides.rubygems.org/patterns/#pessimistic_version_constraint

Rails4 new application creation - Bundler expecting version MySQL2 3.1.3?

I'm starting to experiment with Rails 4 for work where we are using the MySQL2 3.1.0 gem on the server.
Locally with Ruby 2.0, I installed the MySQL2 3.1.0 Gem and everything was fine there (matching the gem version on the work server basically just to match the production server environment).
When I created a new Application (ruby new r4_test -d mysql) I ran into a problem though. Bundler crashed during the new application creation process complaining about missing MySQL2 3.1.3 files. It looks like 3.1.3 (released 3 months ago if I'm looking right) is the highest version number of the MySQL2 Gem. I'm confused about this because the only version of MySQL2 installed in the Ruby folder is version 3.1.0. Why did Bundler ignore the installed gem and expect a higher version that wasn't installed locally? I skipped Rails3 so I'm new to Bundler. It doesn't seem like it should expect a version that's not local though. Sometimes there are bugs or other issues where you need to stay on an older version of a gem for awhile too. ?
Thanks!
If you don't already have a Gemfile.lock in your project directory, Bundler tries to install the most recent version available that meets the version criteria in Gemfile. So, for a new Rails project, it will try to install the latest dependencies of the default generated Gemfile. It doesn't actually look at your installed gems at all unless you already have a Gemfile.lock.
You can use the --skip-bundle (or -B) if you don't want Rails to run bundle install when creating a new project. That gives you a chance to customize the Gemfile first. You can add in a version constraint if you want to be sure it will use the version you already have installed.