-
Notifications
You must be signed in to change notification settings - Fork 68
install error: tins requires Ruby version >= 2.0 #94
Comments
Ruby >= 2.0 required, it's just that. |
....but OverSip installs ruby 1.9.1 forced, not me... |
Sorry, my fault. I don't understand, oversip just requires Ruby >= 1.9.2. It seems that such a $ gem list | grep ansicolor |
OverSIP 2.0.4 released. Please check it and let me know. |
I have the same problem, just tried out 2.0.4 - didnt work.
It seems I can not just set Neither 1.9 nor 2.0 version has |
Yes, error remains: installing 'oversip' Ruby Gem version 2.0.4... $ gem list | grep ansicolor (after error) -> empty ...# gem list |
Hmm, forcing |
Honestly no idea. You may try to create a Ruby file with this content: # Ruby external gems.
require "syslog"
# Load EventMachine-LE here to avoid som EM based gem in server.rb to be loaded first
# (and load eventmachine instead of eventmachine-le).
gem "eventmachine-le", "= 1.1.7"
require "eventmachine-le"
gem "iobuffer", "= 1.1.2"
require "iobuffer"
gem "em-udns", "= 0.3.6"
require "em-udns"
gem "escape_utils", "= 1.0.1"
require "escape_utils"
gem "term-ansicolor", "= 1.3.0"
require "term/ansicolor"
gem "posix-spawn", "= 0.3.9"
require "posix-spawn"
gem "em-synchrony", "= 1.0.3"
require "em-synchrony" Run it and let's see what happens. You may also try by loading such a |
I had to set up all the gems it required; the file runs without errors. |
Okay, I figured it out. |
Ok. So, is there anything the OverSIP deb package can do to avoid this problem? |
I believe this is debian/ubuntu 14.04 issue and it will not be fixed in any way (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737782).
|
I managed to install oversip 2.0.4 on Ubuntu 14.04 after:
|
install failed. |
Ubuntu 14.04 amd64, no ruby preinstalled or installed ruby 2.3.1 (in both situations)
Can't install oversip:
...# apt-get install oversip
...
installing 'oversip' Ruby Gem version 2.0.3...
ERROR: Error installing oversip:
tins requires Ruby version >= 2.0.
(got ruby 1.9.1 installed after that)
Is RVM workaround the only way?
Similar closed dependency issue:
#54
The text was updated successfully, but these errors were encountered: