Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gem "hashie" issue #35

Closed
kushbhandari opened this issue May 16, 2014 · 7 comments
Closed

gem "hashie" issue #35

kushbhandari opened this issue May 16, 2014 · 7 comments

Comments

@kushbhandari
Copy link

After adding "desk" gem to my Gemfile and runnin bundle install I get into below errors:

Bundler could not find compatible versions for gem "hashie":

In Gemfile:

desk (>= 0) ruby depends on
  hashie (~> 1.2.0) ruby

grape (>= 0) ruby depends on
  hashie (2.0.3)

Can "hashie" be upgraded to >= 2.0.3 ?

@chriswarren
Copy link
Owner

Can you upgrade hashie in a branch, make sure tests run, and then make a
pull request for it?

Thanks!

On Fri, May 16, 2014 at 12:06 PM, kushbhandari notifications@github.comwrote:

After adding "desk" gem to my Gemfile and runnin bundle install I get into
below errors:

Bundler could not find compatible versions for gem "hashie":
In Gemfile:
desk (>= 0) ruby depends on
hashie (~> 1.2.0) ruby

grape (>= 0) ruby depends on
hashie (2.0.3)

Can "hashie" be upgraded to >= 2.0.3 ?


Reply to this email directly or view it on GitHubhttps://github.com//issues/35
.

@kushbhandari
Copy link
Author

I tried running tests but ran into few errors like below:

/desk/spec/helper.rb:12:in `require': cannot load such file -- ruby-debug (LoadError)

Then I installed ruby-debug19 for this and updated Gemfile too. But still getting few more errors:

`require': dlopen(path/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle, 9): Symbol not found: _ruby_current_thread (LoadError)
Referenced from: /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle
Expected in: flat namespace
in/.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle - /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle

I think I will keep on getting these errors to use this so I will stop here and ask if this is expected for Ruby version on my system.
My Ruby Version: ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-darwin13.0.1]

I am running tests by running:

rspec spec/desk_spec.rb

I am doing this before even upgrading hashie gem version. Please let me know if this is expected or I am into completely different direction.

Thanks,
Kush

@kushbhandari
Copy link
Author

@chriswarren Another update:
I did below also:

bundle exec rake spec

And got almost similar errors:

/.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby-debug-base.rb:1:in require': dlopen(/.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle, 9): Symbol not found: _ruby_current_thread (LoadError) Referenced from: /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle Expected in: flat namespace in /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle - /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby_debug.bundle from /.rvm/gems/ruby-1.9.3-p448/gems/ruby-debug-base19-0.11.25/lib/ruby-debug-base.rb:1:in<top (required)>'

@chriswarren
Copy link
Owner

@kushbhandari Have you had any luck with this?

@kushbhandari
Copy link
Author

Sorry for late reply, no I haven't tried enough after that. Will let you know if I am able to resolve this sometime later. I will close this issue for now and come back to open if need more information. Thanks.

@wkoffel
Copy link
Contributor

wkoffel commented Jul 23, 2014

I'm running into this same issue. Did anyone find a work-around? My conflict is with elasticsearch-model gem which requires hashie > 2.1.1. The requirement for 1.x within desk is going to continue to bite more places.

@wkoffel
Copy link
Contributor

wkoffel commented Jul 23, 2014

So I updated the gemspec on a branch, and didn't have any issues with the tests. Maybe there was something else going on with kushbhandari's setup. I created a pull request if you want to give it a go, Chris.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants