stevenhaddox / rvm_fw

RVM::FW - Exposing hidden Rubies for firewalled RVMs
http://rvm-fw.herokuapp.com
MIT License
31 stars 9 forks source link

rubygems version list depends on github.com #14

Closed mindscratch closed 11 years ago

mindscratch commented 11 years ago

the scripts/rubygems has two functions that dependon github.com, in particular rubygems_version_list: https://github.com/wayneeseguin/rvm/blob/master/scripts/rubygems#L80

when installing ruby-1.9.3-pXYZ I get an error because it can't get the checksum for "rubygems-.tgz", notice the rubygems version is missing.

Not sure how to "fix" this since it's a core rvm script, might have to package a "fixed" version of rvm that wouldn't depend on github.com or other external services.

stevenhaddox commented 11 years ago

For now we should probably revert back to the most recent version of RVM that works without this dependency... We need to ping Wayne Seguin and whomever the current RVM maintainers via the RVM google group about a way to make a config to override the GitHub dependency so we can provide that number manually...

stevenhaddox commented 11 years ago

As an update, I've submitted this issue of having hard-coded URLs to RVM's Google group (https://groups.google.com/forum/?fromgroups#!forum/rubyversionmanager). Once the topic is approved we should be able to monitor their response there.

mindscratch commented 11 years ago

already got a response, says to look here: https://rvm.io/rvm/offline/

I'll check it out this week (hopefully).

mpapis commented 11 years ago

@stevenhaddox - the issues should be submitted to the rvm issue tracker, the google group is for more common discussions

mpapis commented 11 years ago

additionally to the offline docs have a look on binary rubies - run __list_remote_all_for - that's a list of binary rubies that can be installed with rvm mount, for more details read rvm help mount

stevenhaddox commented 11 years ago

@mpapis thanks. The issue here was actually that we just aren't specifying the latest version of RubyGems in the db file properly. The default of "latest-1.8" is probably (haven't verified) querying out to the web to get that version number. Simply changing that to "1.8.25" avoids this issue entirely.

I've modified the source code to manually control the version number since we want that for this kind of deployment anyway.

mpapis commented 11 years ago

on rvm get head you can now say:

rvm install 2.0.0 --rubygems 2.0.1