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

Rack version mismatch #1066

Closed
balasankarc opened this issue Jul 13, 2015 · 6 comments
Closed

Rack version mismatch #1066

balasankarc opened this issue Jul 13, 2015 · 6 comments

Comments

@balasankarc
Copy link

Hi,
The gemspec file (of version 0.12.0) specifies that the rack version requirement is ">=1.3.0". However, spec/grape/integration/rack_spec.rb checks whether the Rack version is 1.5.3 or 1.6.1. This induces ambiguity. Please fix it.

I am packaging grape for Debian (as part of GitLab packaging. Grape is a member of the dependency chain), where the rack version is still 1.5.2. But all the tests (other than the one mentioned above) seems to run perfectly with Rack v1.5.2. So, is it necessary for grape to require the above mentioned exact rack versions? If not, can you remove that spec I mentioned above?

Thanks.

@dblock
Copy link
Member

dblock commented Jul 13, 2015

I think we should make it >= 1.5.2 in gemspec. Would appreciate a PR.

@balasankarc
Copy link
Author

I'll send a PR ASAP.

BTW, Rack 1.5.2 sets it's release as "1.5", not "1.5.2" ( as seen here ). So, the split on period to Rack.release will assign nil to the variable 'release' which will cause the mentioned test to fail.

If Rack versions >= 1.5.2 work succesfully, can we disable the mentioned test? All the tests run fine with 1.5.2 (and 1.6.4 - I checked). So, is that test really needed?

@dblock
Copy link
Member

dblock commented Jul 13, 2015

I am fine with anything that makes the test match what's in Gemspec or removes any unnecessary tests. Make a call.

@dm1try
Copy link
Member

dm1try commented Aug 14, 2015

I think we should make it >= 1.5.2

rails 3 locked on rack ~> 1.4.5, do you wanna drop support of rails 3?)

@dblock
Copy link
Member

dblock commented Aug 14, 2015

I would be open to dropping support for Rails 3 en general, but only if there's a good reason.

@dm1try
Copy link
Member

dm1try commented Aug 20, 2015

The mentioned test is fixed in #1104.

but only if there's a good reason.

The reason above(updating old dependencies) is not good one?) Anyway it's another issue and can be fixed later, I agree.

@dm1try dm1try closed this as completed Aug 20, 2015
dm1try added a commit that referenced this issue Nov 4, 2018
This reverts commit 022a642.

rm useless appraisal

ref #1813, #1066
basjanssen pushed a commit to basjanssen/grape that referenced this issue Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants