ruby pkgs: Source locally installed gems is ignoring because it is missing extensions

[sarcasticadmin]

Description

#400243 was specifically to fix pkgs.lolcat. This seems to effect other packages like against master aacfc64:

• terraspace
• timetrap
• puppet
• licensed

I suspect there are others. I was focusing on anything with a gemset.nix and default ruby.

Warning output from terraspace:

$ nix run github:nixos/nixpkgs/aacfc645dc2aa94f3ad60a3dcd5415024b280374#terraspace -- -h
Source locally installed gems is ignoring #<Bundler::StubSpecification name=rbs version=3.4.0 platform=ruby> bec
ause it is missing extensions
Source locally installed gems is ignoring #<Bundler::StubSpecification name=racc version=1.7.3 platform=ruby> be
cause it is missing extensions
Source locally installed gems is ignoring #<Bundler::StubSpecification name=debug version=1.9.2 platform=ruby> b
ecause it is missing extensions
Usage: terraspace COMMAND [args]

The available commands are listed below.
The primary workflow commands are given first, followed by
less common or more advanced commands.

Main Commands:
...

Moving from ruby (currently 3.3) to ruby_3_4 seems to resolve the warnings without any changes to gems or bundler. See #416427 Ive confirmed this working for terraspace too:

diff --git a/pkgs/by-name/te/terraspace/package.nix b/pkgs/by-name/te/terraspace/package.nix
index b849f4b10665..38f19beab67d 100644
--- a/pkgs/by-name/te/terraspace/package.nix
+++ b/pkgs/by-name/te/terraspace/package.nix
@@ -5,10 +5,11 @@
   bundlerUpdateScript,
   makeWrapper,
   ruby,
+  ruby_3_4,
 }:
 let
   rubyEnv = bundlerEnv {
-    inherit ruby;
+    ruby = ruby_3_4;
     name = "terraspace";
     gemdir = ./.;
   };

Expected behaviour

no warnings for these packages

[ngn999]

kamal, fastlane and cocoapods have the same warnings.

[h0nIg]

as far as i can see, the 25.11. default ruby 3.3.9 is broken at all and incompatible with openssl 3.6: #456753

The 3.4 ruby was bumped recently and therefore maybe solve this particular issue? The 3.3.9 is old and there is 3.3.10 already

[h0nIg]

#456793 should fix this overall

[theCapypara]

I still have this issue on 25.11, would it be worth to backport this to stable?