essentialkaos/rbinstall

Utility for installing prebuilt Ruby versions to RBEnv

rbinstall's Issues

Unable to install jRuby 1.6.* due to invalid gem option

Bug report

System info:

• Version used (rbinstall --version): 0.18.0
• OS (e.g. from /etc/*-release): CentOS 6.9, CentOS 7.4.1708
• Kernel (uname -a): Linux 0b4015909cd2 4.9.87-linuxkit-aufs (official Docker image for CentOS 6 and CentOS 7: centos:6 and centos:7)
• Install tools: yum/dnf

Steps to reproduce:

Install jRuby 1.6.3 via rbinstall utility.

Expected behavior:

jRuby is successfully installed.

Actual behavior:

jRuby installation is failing.

Additional info:

List of affected versions:

• jruby-1.6.3
• jruby-1.6.4
• jruby-1.6.5.1
• jruby-1.6.6
• jruby-1.6.7
• jruby-1.6.8

Here is the content of /tmp/rbinstall-fail.log logging file:

ERROR:  While executing gem ... (OptionParser::InvalidOption)
    invalid option: --no-document

Uninstallation Ruby from the system

Feature Request

I suppose that would be great to be able to uninstall Ruby from the system. It might help if you need to remove installed Ruby by mistake. Also it a great chance to integrate RBInstall with SCM systems (such as Ansible, SaltStack etc.) which are already uses similar interfaces (like present or absent states in Ansible) for other package managers.

Unable to install Ruby 1.9.2-p* due to OpenSSL error

Bug report

System info:

• Version used (rbinstall --version): 0.18.0
• OS (e.g. from /etc/*-release): CentOS 6.9, CentOS 7.4.1708
• Kernel (uname -a): Linux f950a7f5e375 4.9.87-linuxkit-aufs (see official CentOS 7 Docker image with the name centos:6 or centos:7)
• Install tools: yum/dnf

Steps to reproduce:

Install Ruby 1.9.2-p330 via rbinstall utility.

Expected behavior:

Ruby 1.9.2-p330 is successfully installed.

Actual behavior:

Ruby installation is failing.

List of affected versions:

• 1.9.2-p180 (+railsexpress)
• 1.9.2-p290 (+railsexpress)
• 1.9.2-p318 (+railsexpress)
• 1.9.2-p320 (+railsexpress)

Additional info:

Here is the following content from /tmp/rbinstall-fail.log logging file:

ERROR:  While executing gem ... (OpenSSL::SSL::SSLError)
SSL_read:: shutdown while in init

Add an option to disable the progress indicator

It is necessary to be able to disable the indicator to avoid getting very long logs with every sprite of the indicator showing on a separate line.

Unable to install Ruby 1.9.3

Bug report

System info:

• Version used (rbinstall --version): 0.17.0
• OS (e.g. from /etc/*-release): CentOS Linux release 7.4.1708 (Core)
• Kernel (uname -a): Linux b7c93bac75ef 4.9.49-moby #1 SMP Wed Sep 27 23:17:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce:

Run the following command to install Ruby 1.9.3-p551:

rbinstall -R 1.9.3-p551

Expected behavior:

Ruby, RubyGems and Bundler are installed without any errors.

Actual behavior:

✔ Checking sha1 checksum (< 1 second)
✔ Unpacking 7z archive (2 seconds)
✔ Checking binary (< 1 second)
✖ Updating RubyGems to 2.6.14 (< 1 second)
Can't update rubygems. Update command output saved as /tmp/rbinstall-fail.log
✖ Installing bundler (< 1 second)

Can't install gem bundler. Gem command output saved as /tmp/rbinstall-fail.log.

Additional info:

$ cat /tmp/rbinstall-fail.log
ERROR:  While executing gem ... (OptionParser::InvalidOption)
    invalid option: --no-document

Support versioning for gems

Feature Request

Proposal:

Add versioning support for gems:install in configuration file.

Current behavior:

rbinstall installs the latest available version from RubyGems.

Desired behavior:

rbinstall installs specified version from gems:install with widely-known RubyGem's versions specifiers.

Use case:

rbinstall installs gem bundler by default as it specified in configuration file. On January, 3rd Bundler development team released 2.0.0 version (and 2.0.1 one day after) which has a list of breaking changes.

In particular, bundler 2.x is unable to install gems if Gemfile.lock contains version lower than 2.x., and vice-versa. It means that any application which relies on Bundler 1.x. will be broken after (re-)installation Ruby via rbinstall after January, 3.

Maybe we should install two versions of bundler with fixed versions of 1.x and 2.x. and let Bundler choose which version it should use during on dependencies installation.