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

rubygems version with jruby does not obey 'no_proxy' ENV #934

Closed
mkristian opened this issue Aug 1, 2013 · 5 comments
Closed

rubygems version with jruby does not obey 'no_proxy' ENV #934

mkristian opened this issue Aug 1, 2013 · 5 comments
Milestone

Comments

@mkristian
Copy link
Member

@mkristian mkristian commented Aug 1, 2013

since I am routing ALL my traffic through TOR nowadays I got some problems with using bundler or 'gem' as they do NOT obey the 'no_proxy' settings and then runs into a flaw of my TOR setup. with MRI works and a look into the code reveals that they fixed that problem with rubygems already. I guess the jruby rubygems needs an update.

@BanzaiMan
Copy link
Member

@BanzaiMan BanzaiMan commented Aug 4, 2013

What's the RubyGems versions on MRI and JRuby? IIRC, you can update RubyGems now independent of JRuby:

jruby -S gem update --system
@mkristian
Copy link
Member Author

@mkristian mkristian commented Sep 3, 2013

great that branch works for me and my proxy settings :)

@BanzaiMan
Copy link
Member

@BanzaiMan BanzaiMan commented Sep 3, 2013

Merged and pushed. c4a1b9a

@BanzaiMan BanzaiMan closed this Sep 3, 2013
@headius
Copy link
Member

@headius headius commented Sep 3, 2013

FWIW, I'd like to go to RG 2.1 for 1.7.5 assuming it is released in the next day or so. It supports default gems better than 2.0, which we'd like to ship in 1.7.5 (json, etc).

Thanks for updating RG to 2.0.7, @BanzaiMan :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants