Invalid Gemspec generated with Zentest 4.9.0 #38

Closed
vishnun opened this Issue Mar 6, 2013 · 4 comments

Comments

Projects
None yet
4 participants
@vishnun

vishnun commented Mar 6, 2013

Invalid gemspec in [../.rvm/gems/ruby-1.9.3-p194/specifications/ZenTest-4.9.0.gemspec]: Illformed requirement ["< 2.1, >= 1.8"]

The correct requirement seems to be ["< 2.1", ">= 1.8"]

The double quotes are missing.

I am using Ruby-1.9.3 just incase you need to know that.

@zenspider

This comment has been minimized.

Show comment
Hide comment
@zenspider

zenspider Mar 6, 2013

Member

The bug is in rubygems. Please update and reinstall zentest.

Member

zenspider commented Mar 6, 2013

The bug is in rubygems. Please update and reinstall zentest.

@zenspider zenspider closed this Mar 6, 2013

@Hakben

This comment has been minimized.

Show comment
Hide comment
@Hakben

Hakben Mar 16, 2013

I launch the command "gem install ZenTest" again just now from my Terminal. I still have this error message: Invalid gemspec in [../.rvm/gems/ruby-1.9.3-p194/specifications/ZenTest-4.9.0.gemspec]: Illformed requirement ["< 2.1, >= 1.8"]
Am i suppose to do something else?

Hakben commented Mar 16, 2013

I launch the command "gem install ZenTest" again just now from my Terminal. I still have this error message: Invalid gemspec in [../.rvm/gems/ruby-1.9.3-p194/specifications/ZenTest-4.9.0.gemspec]: Illformed requirement ["< 2.1, >= 1.8"]
Am i suppose to do something else?

@vishnun

This comment has been minimized.

Show comment
Hide comment
@vishnun

vishnun Mar 16, 2013

Well the bug closed still exists...Its not exactly fixed as such...
In the meanwhile..Delete that file manually and then install a previous
version..
or every time you face this problem, modify the part ["< 2.1, >= 1.8"] *in
that file by *["< 2.1", ">= 1.8"]

Note the quotes missing before you update it. That fixes the problem.

Regards,
Vishnu Narang.
(ThoughtWorks Inc.)

On Sat, Mar 16, 2013 at 5:05 PM, Hakben notifications@github.com wrote:

I launch the command "gem install ZenTest" again just now from my
Terminal. I still have this error message: Invalid gemspec in
[../.rvm/gems/ruby-1.9.3-p194/specifications/ZenTest-4.9.0.gemspec]:
Illformed requirement ["< 2.1, >= 1.8"]


Reply to this email directly or view it on GitHubhttps://github.com/seattlerb/zentest/issues/38#issuecomment-15003353
.

vishnun commented Mar 16, 2013

Well the bug closed still exists...Its not exactly fixed as such...
In the meanwhile..Delete that file manually and then install a previous
version..
or every time you face this problem, modify the part ["< 2.1, >= 1.8"] *in
that file by *["< 2.1", ">= 1.8"]

Note the quotes missing before you update it. That fixes the problem.

Regards,
Vishnu Narang.
(ThoughtWorks Inc.)

On Sat, Mar 16, 2013 at 5:05 PM, Hakben notifications@github.com wrote:

I launch the command "gem install ZenTest" again just now from my
Terminal. I still have this error message: Invalid gemspec in
[../.rvm/gems/ruby-1.9.3-p194/specifications/ZenTest-4.9.0.gemspec]:
Illformed requirement ["< 2.1, >= 1.8"]


Reply to this email directly or view it on GitHubhttps://github.com/seattlerb/zentest/issues/38#issuecomment-15003353
.

@alexkwolfe alexkwolfe referenced this issue in seattlerb/rubyinline Mar 21, 2013

Closed

ZenTest #33

@alexkwolfe

This comment has been minimized.

Show comment
Hide comment
@alexkwolfe

alexkwolfe Jun 13, 2013

For those that are still dealing with this problem, you can lock ZenTest at version 4.3 to avoid it:

gem 'ZenTest', '= 4.3', require: false

Skipping require: false will load the full ZenTest gem which will set $TESTING = true. This causes problems in other libraries that switch on this global variable.

I ran into this exact problem with Resque.

For those that are still dealing with this problem, you can lock ZenTest at version 4.3 to avoid it:

gem 'ZenTest', '= 4.3', require: false

Skipping require: false will load the full ZenTest gem which will set $TESTING = true. This causes problems in other libraries that switch on this global variable.

I ran into this exact problem with Resque.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment