-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix and extend installing binaries for Rubinius #2373
Comments
👍 What about the case of |
It should match the highest available rubinius-2.x.y, unless there is a specific rubinius-2.tar.bz2. |
👍 |
I am happy to update the Ruby VMs once these changes are ready :) |
@joshk ❤️ |
@joshk any chance you could test |
The output on the builds for the travis-canary project seem different, so in case this change to RVM was deployed, there are more bugs: https://travis-ci.org/rubinius/travis-canary/builds/14337331
|
the error from 3. is from old version - so the new code was not deployed yet |
Ah the difference with |
I can try updating rvm in a debug vm and test out these combos if you like? On 22 November 2013 at 12:24:45 am, Michal Papis (notifications@github.com) wrote: the error from 3. is from old version - so the new code was not deployed yet — |
@joshk please try updating to |
Seems to work a charm, can we get this into 1.24.x? |
working on extra fix for detecting more short versions, will push stable in hour or two |
awesome, I will build a new image tomorrow and update production :) |
Ahhh, found a bug...
The last |
it's not a bug, it is recorded version of rubinius in rvm - it is 2.2.0, you need to use fuzzy to find latest version of the installed rubies: rvm use rbx --install --binary --fuzzy |
But I did a |
You have to admit that
is a little odd |
yep I did not update the recorded version for rubinius yet, the new fuzzy will check the available binaries for you always so it will work just fine |
Ok, great, let me know when I should run the tests once more :) |
…pdate rubinius to 2.2.1, update #2373
released |
1. Fix installing binaries
RVM presently appears to match a Travis specification like
rvm: rbx-2.2
to the highest matching available binary (eg rubinius-2.2.1.tar.bz2) as seen here: https://travis-ci.org/rubinius/travis-canary/jobs/14282001However, the install failed with some issue about a gemset.
2. Extend installing binaries
The binary matching logic should first match a specific available binary. In the case above, a binary exists for rubinius-2.2.tar.bz2 and that is listed in the index.txt file. RVM should prefer that to the match that it performed. If the binary had not existed, it should have matched the highest available.
If a specific special case is needed,
rvm: rbx
should match rubinius.tar.bz2. In other words, the most specific match should accept no version numbers at all.The text was updated successfully, but these errors were encountered: