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

Faraday dependency causing issues #31

Closed
jtippett opened this issue Jan 20, 2014 · 14 comments
Closed

Faraday dependency causing issues #31

jtippett opened this issue Jan 20, 2014 · 14 comments

Comments

@jtippett
Copy link

Hi,

the dependency on Faraday is declared in such a way that it is causing problems:

spec.add_dependency 'faraday', ['>= 0.8', '< 0.10']

Faraday is now on 0.9 but users of analytics-ruby cannot update as it conflicts with this requirement. IMO unless there is a specific known incompatibility with 0.10 (impossible, since it is not released yet), it's inappropriate to exclude it in this way. '>= 0.8' should be sufficient.

@calvinfo
Copy link
Contributor

huh, yeah, we can certainly relax it!

@mikeatlas
Copy link

+1

@mikeatlas
Copy link

Any update on this? I can't update my bundle right now in a straightforward manner without this breaking dependency issue.

calvinfo added a commit that referenced this issue Feb 20, 2014
* adding .group(), .page(), and .screen() calls
* relaxing faraday dependency, fixes #31
@calvinfo
Copy link
Contributor

Yep, just relaxed from the latest version!

@mikeatlas
Copy link

Bundler could not find compatible versions for gem "faraday":
In Gemfile:
analytics-ruby (= 0.6.0) ruby depends on
faraday (< 0.9, >= 0.7.4) ruby

analytics-ruby (= 0.6.0) ruby depends on
  faraday (0.9.0)

@seanmcoleman
Copy link

Also having the same problem as @mikeatlas

@mikeatlas
Copy link

Might need to open a new ticket...

On Feb 28, 2014, at 12:51 AM, Sean Coleman notifications@github.com wrote:

Also having the same problem as @mikeatlas


Reply to this email directly or view it on GitHub.

@calvinfo
Copy link
Contributor

calvinfo commented Mar 4, 2014

hey guys, yeah the problem seems to be that faraday_middleware actually requires < 0.9 which is where the conflict is coming from. there's some progress on it: lostisland/faraday_middleware#74

it's probably worth dropping all of these deps and just going with core libraries, since we're not doing anything fancy. making json requests shouldn't be too difficult

@pickerflicker
Copy link

The current gemspec won't work in bundler for this reason:

Bundler could not find compatible versions for gem "faraday":
In Gemfile:
analytics-ruby (~> 0.6.0) ruby depends on
faraday (< 0.9, >= 0.7.4) ruby

analytics-ruby (~> 0.6.0) ruby depends on
  faraday (0.9.0)

@calvinfo
Copy link
Contributor

calvinfo commented Mar 7, 2014

yeah, that's thanks to faraday_middleware I believe. planning on taking a look at this tonight and switching to the core libs

@jemgold
Copy link

jemgold commented Mar 12, 2014

:( did you get a chance to take a look at this? Somehow our production app has dropped back to analytics-ruby 0.0.1 and I can't get any recent version running because lots of other gems now depend on faraday 0.9

¯_(ツ)_/¯

@calvinfo
Copy link
Contributor

@jongd yep, just removed faraday with 1.0.0. if you give it a spin, please let me know if you run into any problems!

@jemgold
Copy link

jemgold commented Mar 13, 2014

Hero, thanks so much.

@mikeatlas
Copy link

working for me now. thanks

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

6 participants