search

tacho / oauth-signet

Automatically exported from code.google.com/p/oauth-signet
Apache License 2.0
0 stars 0 forks source link

issue with jwt 1.0 which just got released #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. require signet in your project
2. wait for jwt 1.0 release (it happened)
3. bundle update

so bundle update will update jwt to 1.0 now signet crashes requiring the old 
version although the newest one is allowed by the gemspec

What version of the product are you using? On what operating system?
0.4.x but 0.5.0 has same issue. so as master branch
OSX + Linux

Please provide any additional information below.

error output

....bundler-1.6.1/lib/bundler/rubygems_integration.rb:258:in `block in 
replace_gem': can't activate jwt (~> 0.1.4), already activated jwt-1.0.0. Make 
sure all dependencies are added to Gemfile. (Gem::LoadError)
    from ..../gems/signet-0.4.5/lib/signet/oauth_2/client.rb:25:in `<top (required)>'

I dont know which solution you prefer... 
either you locked down the gemspec (patch attached)
or open up that restriction on lib/signet/oauth_2/client.rb line 25

Original issue reported on code.google.com by somek...@gmail.com on 7 May 2014 at 5:49

Attachments:

GoogleCodeExporter commented 9 years ago 
workaround is to lockdown jwt in your gemfile

Original comment by somek...@gmail.com on 7 May 2014 at 5:53

GoogleCodeExporter commented 9 years ago 
Hey can you go into detail as to how you lockedown jwt in your gemfile? I'm 
kind of new to ruby/rails. Thanks.

Original comment by mohammad...@gmail.com on 11 Aug 2014 at 6:31

GoogleCodeExporter commented 9 years ago 
can you please explain how to apply the patch?

Original comment by vmidevt...@gmail.com on 14 Oct 2014 at 8:44

GoogleCodeExporter commented 9 years ago 
Same problem here. It strikes me as ill-advised to be specifying gems outside 
of the gemspec, but perhaps there are historical reasons for doing this that I 
am not aware of.

Original comment by lukeasro...@gmail.com on 23 Oct 2014 at 8:58

GoogleCodeExporter commented 9 years ago 
For others, if you want to address by locking down jwt in your gemfile, as 
mentioned, just specify the most recent version before 1.0.0:

gem 'jwt', '~> 0.1.13'


then you may need to `gem update jwt`, or at least `bundle install`.

Original comment by lukeasro...@gmail.com on 23 Oct 2014 at 9:12