!aGqRytqbCECitOFhbt:nixos.org

Release Management

342 Members
Release schedule: https://github.com/NixOS/nixpkgs/issues/193585 | Feature Freeze: https://github.com/NixOS/nixpkgs/issues/194208 | Blockers: https://github.com/orgs/NixOS/projects/1391 Servers

Load older messages


SenderMessageTime
19 May 2023
@raitobezarius:matrix.orgraitobezariusi don't understand why ruby 3_1 openssl gem is affected22:39:06
@raitobezarius:matrix.orgraitobezariusor 3_2…22:39:10
@raitobezarius:matrix.orgraitobezariusanyway ruby openssl gem seems to be manageable by maintainers (?)22:39:22
@raitobezarius:matrix.orgraitobezariusI'm much more worried about nodejs 16, did we try to bump everything violently?22:39:45
@hexa:lossy.networkhexa
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:matrix.orgraitobezariusthis makes no sense to me22:40:22
@raitobezarius:matrix.orgraitobezariusthis seems a bad packaging issue22:40:34
@raitobezarius:matrix.orgraitobezarius 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:matrix.orgraitobezariusI'm checking now22:41:45
@raitobezarius:matrix.orgraitobezarius
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:matrix.orgraitobezariusof course :)22:41:52
@hexa:lossy.networkhexahas an issue attached22:41:58
@hexa:lossy.networkhexause -B122:41:59
@raitobezarius:matrix.orgraitobezariusthis issue is not relevant22:42:17
@hexa:lossy.networkhexabuilding it with openssl 3 currently22:42:28
@raitobezarius:matrix.orgraitobezarius it makes sense only for Ruby 3.0 which didn't had support for it 22:42:42
@raitobezarius:matrix.orgraitobezariusThis is not true anymore since our patch22:42:45
@raitobezarius:matrix.orgraitobezariusI'm building a Discourse with Node.js 18 to test it throughly22:42:56
@hexa:lossy.networkhexayeah, builds22:43:13
@hexa:lossy.networkhexaPR incoming22:43:15
@raitobezarius:matrix.orgraitobezariusshould I let you drive them?22:43:33
@raitobezarius:matrix.orgraitobezariusshould I do Node.js shit?22:43:39
@hexa:lossy.networkhexacomitting ruby rn22:43:48
@hexa:lossy.networkhexafeel free to look at node22:43:52
@raitobezarius:matrix.orgraitobezariusTesting Node.js then22:43:53
@raitobezarius:matrix.orgraitobezariusmini_racer native gem node (embedding a V8 engine) is not compatible with any V8 engine (i.e. Node.js 18)22:44:34
@raitobezarius:matrix.orgraitobezariusthinking about a strategy22:44:40
@raitobezarius:matrix.orgraitobezariusoh lord: https://github.com/rubyjs/mini_racer/pull/26122:45:19
@raitobezarius:matrix.orgraitobezarius

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
@raitobezarius:matrix.orgraitobezarius *

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:49

Show newer messages


Back to Room ListRoom Version: 6