Ruby SASS, Unable to Resolve Dependancies

ruby sass, unable to resolve dependancies

Compass 0.12.6 apparently depends on sass ~>3.2.19, which means that the version of sass should be bigger than 3.2 and smaller than 3.3, so basically compass needs sass 3.2.x. You have two options.

1. Also download sass 3.2.19, install both versions of sass, use the latest one yourself and make compass happy.
2. Just install sass 3.2.19 and use that yourself as well, this obviously only works if you don't need any features introduced in sass 3.3.

How to resolve gemfile sass dependency issue

From your comment it seems like your app does not have a Gemfile and therefore bundler cannot solve the dependency betweens different Gems for you. I see two options:

• Install the missing sass Gem manually with gem install sass -v '3.4.6'. If an other versions of the sass Gem is alreday installed, uninstall it first with gem uninstall sass (might break other apps) and than install the needed version: gem install sass -v '3.4.6'. And hope that there are no other Gems missing.

Or:

• Start using Bundler (see: http://bundler.io/gemfile.html). That means: create a Gemfile and add all Gems that your app needs into that file. That might be more work at the beginning, but is IMO the better option if you plan to maintain the app for a longer period of time.

Ruby - Unable to resolve dependencies with actionpack

There are a lot information about dependencies in Gemfile and from Error.

railties (= 5.0.0) was resolved to 5.0.0, which depends on
actionpack (= 5.0.0)

simple_form (~> 3.0.2) was resolved to 3.0.2, which depends on
actionpack (~> 4.0)

~> This limits versions to a subset of the possible versions. Read about it.

So from error you can read, that simple_form depends from actionpack, which can be only from 4.0 to 4.1 version. But railties depends on actionpack at least version 5.0.

To resolve this problem you must update simple_form gem. For example version 3.2.1 has next specification of actionpack:

s.add_dependency('actionpack', '> 4', '< 5.1')

Cannot resolve gem dependencies - doorkeeper, sass-rails - on jruby using Rails 4

I checked applicake/doorkeeper issues on GitHub.
This gem does not support Rails 4 yet, and 0.6.x will not support.

https://github.com/applicake/doorkeeper/pull/200

We won't plan to support versions less than 1.0 for rails 4.

But someone already forked for Rails 4 like this https://github.com/applicake/doorkeeper/pull/213 .

You can use these forks as below.

# Gemfile
gem 'doorkeeper', github: 'kaznum/doorkeeper', branch: 'support_rails4'

Hope to help you.

Upgrading to Rails 5, can't resolve dependencies

The gem web-console is locking your update process, first change it to a more recent version like:

gem 'web-console', '>= 3.3.0'

Then remove Gemfile.lock and run bundle install also always is good to check the version of the other gems and check the official Rails upgrade process documentation in http://guides.rubyonrails.org/upgrading_ruby_on_rails.html

How to resolve You need to have Ruby and Sass installed and in your PATH for this task to work Warning?

Ok I got it. I just had to install Sass using gem install sass and now everything is fine...couldn't be easier.

Missing Dependencies in Compass/SASS

So I resolved the problem. Still unsure as to what it was that changed in my environment that resulted in me needing to deal with this dependency. The solution was not limited to the installation of the wdm gem. The native gem dependency required me to install the Ruby DevKit (http://rubyinstaller.org/downloads).

I am using a Windows 7 OS. Following the instructions located @ https://github.com/oneclick/rubyinstaller/wiki/Development-Kit I

1. unpacked the files to C:\RubyDevKit
2. cmd C:\RubyDevKit
3. ruby dk.rb init >> Initialization Complete!
4. notepad config.yml
5. Added a reference to my primary ruby install ( - C:/Ruby200-x64 )
6. checked that I was all good ( ruby dk.rb review )
7. ruby dk.rb install

After that, I did a couple gem installs and then went straight for
gem install wdm

After that, all my compass watching woes were null and void.

Was it worth it? Dunno...but at least I'm back to where I started.

---

Related Topics