I am looking for clarification on the install process, specifically on Centos. Following the guide @ https://drupal.org/node/2052955 without any variation from the guidance (or any errors/unexpected results) up untill bundle install.
So, on a fresh drupal install, drush installed, fresh omega 4 theme, fresh drush wizard subtheme i get: 

[root@vm subtheme]# bundle install
Resolving dependencies...
Could not find gem 'sass (>= 0) ruby' in the gems available on this machine.

Here are some more cmds which show the states, maybe there is an obvious error/misconfiguration there:

[root@vm subtheme]# rvm gemset list

gemsets for ruby-1.9.3-p448 (found in /usr/local/rvm/gems/ruby-1.9.3-p448)
   (default)
   global
=> omega.subtheme
[root@vm subtheme]# rvm requirements
Checking requirements for centos.
Requirements installation successful.
[root@vm subtheme]# gem list

*** LOCAL GEMS ***

bundler (1.3.5)
bundler-unload (1.0.1)
executable-hooks (1.2.0)
rake (10.1.0)
rubygems-bundler (1.3.0)
rvm (1.11.3.8)
[root@vm subtheme]# gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.8.25
  - RUBY VERSION: 1.9.3 (2013-06-27 patchlevel 448) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/local/rvm/gems/ruby-1.9.3-p448@omega.subtheme
  - RUBY EXECUTABLE: /usr/local/rvm/rubies/ruby-1.9.3-p448/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/rvm/gems/ruby-1.9.3-p448@omega.subtheme/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /usr/local/rvm/gems/ruby-1.9.3-p448@omega.subtheme
     - /usr/local/rvm/gems/ruby-1.9.3-p448@global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org/"]
  - REMOTE SOURCES:
     - http://rubygems.org/

Any suggestions on how to get past this?

Comments

c13l0’s picture

c13l0 commented

I have a different flavor of linux, so not sure if this will work for CentOS. In the terminal go to preferences>profiles>command then check-mark "Run command as login shell". I was then able to bundle install and bundle exec guard.

serg2’s picture

serg2 commented
Status: Active » Closed (works as designed)

thanks for the thought C13L0.
No matter what I did I could not get this to work. Everything indicated the setup was right until running [root@vm subtheme]# bundle install

I cleaned everything out of the server using 

rvm list  #what ruby version is in use?
rvm gemset list #what gemset is in use?
rvm use gemset omega.mysubtheme #use this gemset; do it before rvm requirements and bundle install
rvm gemset empty gemsetname #great if you've accidentally bundle installed into the wrong gemset
rvm gemset delete gemsetname #great for wiping out any gemsets eg. leftovers from a deleted subtheme
gem list #what gems are in this gemset?

and tried again (quite a few times!) and then finally gave up and deleted the server.

This morn with fresh eyes I tried again and... it is working as designed so I can only put the error down to my incompetence :s
Closing the issue

c13l0’s picture

c13l0 commented

Glad you got it working!