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.

Sign up for GitHub

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

Jump to bottom

JRuby 1.7.4 Regression, Failing to find installed gems from bin commands #782

Closed
zdennis opened this issue Jun 1, 2013 · 7 comments
Closed

JRuby 1.7.4 Regression, Failing to find installed gems from bin commands #782

zdennis opened this issue Jun 1, 2013 · 7 comments
Labels
application
Milestone
Invalid or Duplicate

Comments

@zdennis
Copy link

zdennis commented Jun 1, 2013

The following works with JRuby 1.7.3 but fails with JRuby 1.7.4:

  • create a Gemfile with "warbler" in it
  • execute: bundle install --path vendor
  • execute: vendor/jruby/1.9/bin/warble

Expected output (with JRuby 1.7.3):

warble aborted!
No executable script found

Actual output (with JRuby 1.7.4):

Gem::LoadError: Could not find warbler (>= 0) amongst [bouncy-castle-java-1.5.0147, 
bundler-1.3.5, jruby-launcher-1.0.16-java, jruby-openssl-0.8.8, rake-10.0.4, rake-10.0.3, 
rubygems-bundler-1.1.1, rvm-1.11.3.8]
to_specs at /Users/zdennis/.rvm/rubies/jruby-1.7.4/lib/ruby/shared/rubygems/dependency.rb:247
to_spec at /Users/zdennis/.rvm/rubies/jruby-1.7.4/lib/ruby/shared/rubygems/dependency.rb:256
   gem at /Users/zdennis/.rvm/rubies/jruby-1.7.4/lib/ruby/shared/rubygems.rb:1231
(root) at vendor/jruby/1.9/bin/warble:22
@headius
Copy link
Member

headius commented Jun 2, 2013

@zdennis Hmmm, I'm not sure what would cause that. Works ok installed in normal gem home?

@BanzaiMan
Copy link
Member

Not sure what's going on yet, but bundle exec doesn't suffer from this problem.

@headius
Copy link
Member

headius commented Jun 10, 2013

I could not reproduce this on JRuby master (I get the same result as JRuby 1.7.3):

ext-jruby-local ~/projects/jruby/tmp2 $ bundle install --path vendor
The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
Fetching gem metadata from http://rubygems.org/..
Installing rake (10.0.4) 
Installing jruby-jars (1.7.4) 
Installing jruby-rack (1.1.13.2) 
Installing rubyzip (0.9.9) 
Installing warbler (1.3.8) 
Using bundler (1.3.0) 
Your bundle is complete! It was installed into ./vendor

ext-jruby-local ~/projects/jruby/tmp2 $ vendor/jruby/1.9/bin/warble 
WARN: Unresolved specs during Gem::Specification.reset:
      jruby-rack (>= 1.0.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
warble aborted!
No executable script found
/Users/headius/.rvm/gems/ext-jruby-local/gems/warbler-1.3.8/lib/warbler/traits/nogemspec.rb:43:in `default_executable'
/Users/headius/.rvm/gems/ext-jruby-local/gems/warbler-1.3.8/lib/warbler/traits/nogemspec.rb:32:in `update_archive'
/Users/headius/.rvm/gems/ext-jruby-local/gems/warbler-1.3.8/lib/warbler/traits.rb:40:in `update_archive'
...

Can you provide an example repository that exhibits the problem with JRuby master? Also, a listing of your installed gems and environment when it fails would help diagnose further.

@phil88530
Copy link

I am getting the same error when cap deploy with passenger, but not if you webrick it locally

@headius
Copy link
Member

headius commented Sep 12, 2013

I noticed that RG 2.1 does not appear to be canonicalizing the binstub
shebang lines, but I'm not sure if that has anything to do with this:

system ~/projects/jruby $ head -5 bin/rspec
#!/Users/headius/projects/jruby/test/../bin/jruby
#
# This file was generated by RubyGems.
#
# The application 'rspec-core' is installed as part of a gem, and

On Wed, Sep 11, 2013 at 5:59 PM, YuFei Zhu notifications@github.com wrote:

I am getting the same error when cap deploy with passenger

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/782#issuecomment-24252564
.

@aplatypus
Copy link

I keep seeing this message on JRuby 9.0 ...

 WARN: Unresolved specs during Gem::Specification.reset

These GEM-s are already installed, the whole is very confusing.

  WARN: Unresolved specs during Gem::Specification.reset:
       json (>= 1.7.7, ~> 1.7)
       minitest (~> 5.1)
 WARN: Clearing out unresolved specs.
 Please report a bug if this causes problems.
               run  bundle update from "."
 Fetching gem metadata from http://rubygems.org/........
 Fetching version metadata from http://rubygems.org/...
 Fetching dependency metadata from http://rubygems.org/..
 Resolving dependencies...
 Using i18n 0.7.0
  . . .

@kares
Copy link
Member

kares commented Jan 20, 2017

this is issue should no longer be relevant -> if so please confirm it still mis-behaving using latest JRuby 1.7

@kares kares closed this as completed Jan 20, 2017
@kares kares added this to the Invalid or Duplicate milestone Jan 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
application
Projects
None yet
Milestone
Invalid or Duplicate
Development

No branches or pull requests
6 participants
@zdennis @headius @BanzaiMan @kares @aplatypus @phil88530