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

Looking for maintainer of Rubinius support #739

Closed
pitr-ch opened this issue Jul 7, 2018 · 2 comments
Closed

Looking for maintainer of Rubinius support #739

pitr-ch opened this issue Jul 7, 2018 · 2 comments
Labels
enhancement Adding features, adding tests, improving documentation. looking-for-contributor We are looking for a contributor to help with this issue.

Comments

@pitr-ch
Copy link
Member

pitr-ch commented Jul 7, 2018

We currently do not have capacity to maintain Rubinius support. If anybody is interested please respond.

@pitr-ch pitr-ch added enhancement Adding features, adding tests, improving documentation. looking-for-contributor We are looking for a contributor to help with this issue. labels Jul 7, 2018
@pitr-ch pitr-ch changed the title Maintain Rubinius support Looking for maintainer of Rubinius support Jul 7, 2018
@olleolleolle
Copy link
Contributor

olleolleolle commented Jun 17, 2021

The Rubinius matrix element in Travis CI is not even installing.

Perhaps that should be let go?

Example: https://travis-ci.com/github/ruby-concurrency/concurrent-ruby/jobs/515376058

16.07s$ rvm use rbx-3.107 --install --binary --fuzzy
curl: (22) The requested URL returned error: 404 Not Found
Required rbx-3.107 is not installed - installing.
curl: (22) The requested URL returned error: 404 Not Found
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm rbx-3.107 do rvm gemset create ' first, or append '--create'.
The command "rvm use rbx-3.107 --install --binary --fuzzy" failed and exited with 2 during .

@chrisseaton
Copy link
Member

The Rubinius repository and discussion rooms have been dead for a year now. Might be time to remove support. I think GitLab are maintaining an internal copy is the only thing? But we can't test against that, and we can't test against that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding features, adding tests, improving documentation. looking-for-contributor We are looking for a contributor to help with this issue.
Projects
None yet
Development

No branches or pull requests

3 participants