On 2016-06-28 16:40:09 [-0300], Antonio Terceiro wrote: > upstream already has support for OpenSSL 1.1.0 in trunk for Ruby 2.4; > see upstream bug linked above. given the current state of afairs, we > will need to either backport that for Ruby 2.3 ourselves, or disable the > openssl extension bundled with the interpreter and use a standalone > ruby-openssl package.
2.4 is scheduled for 2016-12-25 so it is unlikely to be part of the next Debian release, right? Is the backport huge (in terms of conflicts of the original patch) or is it simpler to go for the ruby-openssl package? Sebastian
