I am getting error when i use middleman command - ruby

when I use middleman command, I get errors like below
# middleman
WARN: Unresolved specs during Gem::Specification.reset:
thor (< 2.0, >= 0.15.2)
json (>= 1.7.7, ~> 1.7)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/usr/share/rubygems-integration/1.9.1/gems/bundler-1.3.5/lib/bundler/runtime.rb:33:in `block in setup': You have already activated i18n 0.7.0, but your Gemfile requires i18n 0.6.9. Using bundle exec may solve this. (Gem::LoadError)
from /usr/share/rubygems-integration/1.9.1/gems/bundler-1.3.5/lib/bundler/runtime.rb:19:in `setup'
from /usr/share/rubygems-integration/1.9.1/gems/bundler-1.3.5/lib/bundler.rb:120:in `setup'
from /usr/share/rubygems-integration/1.9.1/gems/bundler-1.3.5/lib/bundler/setup.rb:7:in `<top (required)>'
from /usr/local/lib/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:69:in `require'
from /usr/local/lib/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:69:in `require'
from /var/lib/gems/1.9.1/gems/middleman-core-3.3.10/lib/middleman-core/load_paths.rb:29:in `setup_load_paths'
from /var/lib/gems/1.9.1/gems/middleman-core-3.3.10/bin/middleman:10:in `<top (required)>'
from /usr/local/bin/middleman:23:in `load'
from /usr/local/bin/middleman:23:in `<main>'
I also tried using bundle exec middleman.

Related

uninitialized constant Syck error when running jekyll

Using jekyll, I get the following error when run command bundle exec jekyll serve --watch,
bundler: failed to load command: jekyll (/home/admin/.rbenv/versions/2.3.8/bin/jekyll)
NameError: uninitialized constant Syck
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml/syck_node_monkeypatch.rb:42:in `<top (required)>'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `require'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:200:in `<module:YAML>'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/safe_yaml-0.9.7/lib/safe_yaml.rb:132:in `<top (required)>'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `require'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/jekyll-1.3.0/lib/jekyll.rb:21:in `<top (required)>'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `require'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/jekyll-1.3.0/bin/jekyll:7:in `<top (required)>'
/home/admin/.rbenv/versions/2.3.8/bin/jekyll:22:in `load'
/home/admin/.rbenv/versions/2.3.8/bin/jekyll:22:in `<top (required)>'
/home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/runner.rb:385:in `block in require_program': program version required (Commander::Runner::CommandError)
from /home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/runner.rb:384:in `each'
from /home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/runner.rb:384:in `require_program'
from /home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/runner.rb:52:in `run!'
from /home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/delegates.rb:8:in `run!'
from /home/admin/.rbenv/versions/2.3.8/lib/ruby/gems/2.3.0/gems/commander-4.1.6/lib/commander/import.rb:10:in `block in <top (required)>'
I guess that the few line relating to jekyll-1.3.0 tells us that there is a path problem somewhere.
To update your gems with bundle update
and do a rehash with rbenv rehash
It looks like you're using Jekyll version 1.3.0, which is about 5 years old at this point. Syck was removed from Ruby 2.0.0, so I think you'll need to use a newer version of Jekyll or use the Syck gem to bridge the gap. https://github.com/ruby/syck

Rest-Client will not install for Ruby

I am trying to run a Ruby app with the rest-client gem install. I keep getting the error message:
C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows/root_certs.rb:2:in `require': cannot load such file -- ffi (LoadError)
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows/root_certs.rb:2:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows.rb:7:in `require_relative'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows.rb:7:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient.rb:16:in `require'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient.rb:16:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/rest-client.rb:2:in `require'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/rest-client.rb:2:in `<top (required)>'
from app.rb:6:in `require'
from app.rb:6:in `<main>'
$ ./start ruby
Installing bundle
Starting server
C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows/root_certs.rb:2:in `require': cannot load such file -- ffi (LoadError)
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows/root_certs.rb:2:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows.rb:7:in `require_relative'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient/windows.rb:7:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient.rb:16:in `require'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/restclient.rb:16:in `<top (required)>'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/rest-client.rb:2:in `require'
from C:/RailsInstaller/Ruby2.1.0/lib/ruby/gems/2.1.0/gems/rest-client-1.8.0/lib/rest-client.rb:2:in `<top (required)>'
from app.rb:6:in `require'
from app.rb:6:in `<main>'
However I am sure that the gem is install:
rest-client (2.0.0.rc2, 1.8.0)
rest-open-uri (1.0.0)
rest_client (1.8.3)
Does anyone know possibly what I am doing wrong in the installation process?
The issue was the that FFI was not install and was the reason I was getting error messages. unfortunately using
bundle install
did not install it correct and I had to install the gem manually (which takes much longer than expected to install
gem install ffi

Broken upgrade to susy 2.1.2 cannot load such file -- sass/script/node

I have just updated to susy 2.1.2 from version 1.0.9 so I expected errors.
However, I have no idea what this means.
I do still have both versions installed:
Select gem to uninstall:
1. susy-1.0.9
2. susy-2.1.2
3. All versions
When running my compass:dev I get the following, although the task still finished. How can I remove the erorrs?
Running "compass:dev" (compass) task
C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- sass/script/node (LoadError)
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches/browser_support.rb:1:in `<top (required)>'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:2:in `block in <top (required)>'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `each'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `<top (required)>'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions.rb:9:in `<top (required)>'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:5:in `block in <top (required)>'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `each'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `<top (required)>'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/bin/compass:20:in `block in <top (required)>'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/bin/compass:8:in `fallback_load_path'
from C:/RUBY200/lib/ruby/gems/2.0.0/gems/compass-0.12.2/bin/compass:19:in `<top (required)>'
from C:/Ruby200/bin/compass:23:in `load'
from C:/Ruby200/bin/compass:23:in `<main>'
Running "watch" task
Waiting...
Your Gemfile need only have these:
gem "susy", "~>2.1.0"
gem "sass", "~>3.3.0"
gem "breakpoint", "~>2.4.0"
Bundler will sort out the other dependencies (which are many), as well as updating the gems to the latest versions.
This is the message I got when trying to update Susy with bundler.
susy (~> 2.1.2) ruby depends on
sass (~> 3.3.0) ruby
compass (~> 0.12.6) ruby depends on
sass (3.2.19)
This means you will need at least Sass 3.3.0. The latest alpha pre release of Compass will work with this and you can install it with the following command:
gem install compass --pre
Alternatively if you are using a Gemfile you could install it like this:
gem "compass", "~> 1.0.0.alpha.19"

Padrino error launching sample_blog

I run into this error when I try to launch 'padrino sample_blog'. I installed updated versions of 'multi_json' and 'atomic' gems but I can't launch the blog and have no idea how to solve it, any help?
:sample_blog user$ padrino start
WARN: Unresolved specs during Gem::Specification.reset:
multi_json (~> 1.3)
atomic (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/padrino-core-0.9.21/lib/padrino-core/cli/base.rb:1:in `require': cannot load such file -- thor (LoadError)
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/padrino-core-0.9.21/lib/padrino-core/cli/base.rb:1:in `<top (required)>'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/padrino-core-0.9.21/bin/padrino:7:in `require'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/padrino-core-0.9.21/bin/padrino:7:in `<top (required)>'
from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/padrino:23:in `load'
from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/padrino:23:in `<main>'
from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_noexec_wrapper:14:in `eval'
from /usr/local/rvm/gems/ruby-1.9.3-p392/bin/ruby_noexec_wrapper:14:in `<main>'
Try this and see if it helps:
gem cleanup atomic multi_json

Padrino with RVM gemsets: uninitialized constant ActiveSupport::Deprecation

I'm getting an error trying to run an app, not even trying to do anything sophisticated either, just get the basic thing running... Just wondering if anyone can give me any pointers as to how to debug it. I suspect it might be to do with RVM gemsets, but I'm not sure...
Here's the error message I'm receiving:
NameError: uninitialized constant ActiveSupport::Deprecation
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/rake-0.9.2.2/lib/rake/ext/module.rb:36:in `const_missing'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/activesupport-3.2.1/lib/active_support/core_ext/module/deprecation.rb:7:in `deprecate'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/activesupport-3.2.1/lib/active_support/core_ext/module/synchronization.rb:44:in `<class:Module>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/activesupport-3.2.1/lib/active_support/core_ext/module/synchronization.rb:6:in `<top (required)>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/activesupport-3.2.1/lib/active_support/core_ext/module.rb:8:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/activesupport-3.2.1/lib/active_support/core_ext/module.rb:8:in `<top (required)>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-core-0.9.21/lib/padrino-core/support_lite.rb:13:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-core-0.9.21/lib/padrino-core/support_lite.rb:13:in `<top (required)>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-core-0.9.21/lib/padrino-core.rb:2:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-core-0.9.21/lib/padrino-core.rb:2:in `<top (required)>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-0.9.21/lib/padrino.rb:2:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#marathon_site/gems/padrino-0.9.21/lib/padrino.rb:2:in `<top (required)>'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:68:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:68:in `block (2 levels) in require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:66:in `each'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:66:in `block in require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:55:in `each'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:55:in `require'
~/Developer/.rvm/gems/ruby-1.9.3-p0#global/gems/bundler-1.1.rc.7/lib/bundler.rb:118:in `require'
~/Documents/Projects/MarathonSite/config/boot.rb:8:in `<top (required)>'
I have activesupport 3.2.1 listed in the gemset with my project, so I'm not entirely sure why it's complaining. Any pointers as to what's going on would be appreciated, so I can debug this kind of thing in the future.
Seems a gem clashing.
Update padrino to latest version 0.10.5 (or 0.10.6.c)
gem install padrino --pre
Try using a stable version of bundler
gem uninstall bundler -a; gem install bundler
Edit gemfile of your project and point to padrino 0.10.5 or 0.10.6.c

Resources