| 19 May 2023 |
 raitobezarius | by adopting a openssl gem ≥ 3 | 22:38:51 |
| raitobezarius | i don't understand why ruby 3_1 openssl gem is affected | 22:39:06 |
| raitobezarius | or 3_2… | 22:39:10 |
| raitobezarius | anyway ruby openssl gem seems to be manageable by maintainers (?) | 22:39:22 |
| raitobezarius | I'm much more worried about nodejs 16, did we try to bump everything violently? | 22:39:45 |
 hexa | these 3 paths will be fetched (9.46 MiB download, 38.99 MiB unpacked):
/nix/store/5ky83lr7b07p8iv4lxs8gr5wj4x77qa6-openssl-1.1.1t
/nix/store/a0l81j1mp4sh6f7x20mnk6flqcpjy8vr-ruby3.2.2-openssl-3.1.0
/nix/store/hni2h87m1ziyma3cak2fk6wfm5rpnr18-ruby-3.2.2
copying path '/nix/store/5ky83lr7b07p8iv4lxs8gr5wj4x77qa6-openssl-1.1.1t' from 'https://cache.nixos.org'
copying path '/nix/store/hni2h87m1ziyma3cak2fk6wfm5rpnr18-ruby-3.2.2' from 'https://cache.nixos.org'
copying path '/nix/store/a0l81j1mp4sh6f7x20mnk6flqcpjy8vr-ruby3.2.2-openssl-3.1.0' from 'https://cache.nixos.org'
| 22:40:04 |
| raitobezarius | this makes no sense to me | 22:40:22 |
| raitobezarius | this seems a bad packaging issue | 22:40:34 |
| raitobezarius | I mean, I have done the patch for Ruby 3.0, I am certain that OpenSSL 3.1.0 gem supports OpenSSL 3.x | 22:40:52 |
| raitobezarius | I'm checking now | 22:41:45 |
| raitobezarius | pkgs/development/ruby-modules/gem-config/default.nix
23:, cmake, libssh2, openssl, openssl_1_1, libmysqlclient, git, perl, pcre, pcre2, gecode_3, curl
519: buildInputs = [ openssl_1_1 ];
| 22:41:51 |
| raitobezarius | of course :) | 22:41:52 |
| hexa | has an issue attached | 22:41:58 |
| hexa | use -B1 | 22:41:59 |
| raitobezarius | this issue is not relevant | 22:42:17 |
| hexa | building it with openssl 3 currently | 22:42:28 |
| raitobezarius | it makes sense only for Ruby 3.0 which didn't had support for it | 22:42:42 |
| raitobezarius | This is not true anymore since our patch | 22:42:45 |
| raitobezarius | I'm building a Discourse with Node.js 18 to test it throughly | 22:42:56 |
| hexa | yeah, builds | 22:43:13 |
| hexa | PR incoming | 22:43:15 |
| raitobezarius | should I let you drive them? | 22:43:33 |
| raitobezarius | should I do Node.js shit? | 22:43:39 |
| hexa | comitting ruby rn | 22:43:48 |
| hexa | feel free to look at node | 22:43:52 |
| raitobezarius | Testing Node.js then | 22:43:53 |
| raitobezarius | mini_racer native gem node (embedding a V8 engine) is not compatible with any V8 engine (i.e. Node.js 18) | 22:44:34 |
| raitobezarius | thinking about a strategy | 22:44:40 |
| raitobezarius | oh lord: https://github.com/rubyjs/mini_racer/pull/261 | 22:45:19 |
| raitobezarius |
I wish I could put a money bounty on this... to be honest. CDCK would pay 10k dolllars to get us on latest libv8 node at this point in time...
| 22:45:46 |
