Rubinius version selection is broken #2847

Closed
BanzaiMan opened this Issue May 11, 2014 · 4 comments

Comments

Projects
None yet
4 participants

See travis-ci/travis-ci#2230 (comment)

Looks like rbx-2.0 and rbx-2.1 do not work, while rbx-2 selects the latest version and rbx-2.1.1 selects the precise one. I doubt Rubinius 2.1.x is maintained any longer.

Contributor

rys commented May 22, 2014

I think this is fixed. Current selector code does this: (left hand side is the user supplied string, right hand side is what the selector will use).

rbx => rbx-2.2.7
rbx-2 => rbx-2.2.7
rbx-2.0 => rbx-2.0.0
rbx-2.1 => rbx-2.1.0
rbx-2.1.1 => rbx-2.1.1
rbx-2.2 => rbx-2.2.7

I believe that's the correct behaviour. Let us know if that's not the case.

rys closed this May 22, 2014

mpapis reopened this May 23, 2014

Owner

mpapis commented May 23, 2014

(it works because the db was updated, we need to make sure it works properly with new binary added to the index and --binary flag)

mpapis added this to the rvm 1.25 milestone May 23, 2014

@mpapis mpapis added a commit that referenced this issue May 23, 2014

@mpapis mpapis remove old rbx/rubinius replacement, make sure __check_latest=0 is ra…
…n before the latest run of __rvm_ruby_string_parse_, update #2847
09501cc
Owner

mpapis commented May 23, 2014

this does it, closing, let me know if you still gt issues

mpapis closed this May 23, 2014

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