In reply to @fractivore:cyberia.club
Wait, also it is open source now

In reply to @fractivore:cyberia.club
Wait, also it is open source now

In reply to @fractivore:cyberia.club
Wait, nooo, they just have open sourced components of the platform.

In reply to @fractivore:cyberia.club
It looks like they worked around it by linking the system openssl version to a file named like the one spotify is expecting.

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; [

    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
  ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:

environment.systemPackages = with pkgs; \[
    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
  ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:

environment.systemPackages = with pkgs; \[
    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
 ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:

environment.systemPackages = with pkgs; [
    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
 ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.

In reply to @sporesirius:matrix.org

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; [

    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
  ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.

that is working as intended. if you want applications to use a different alsa-ucm-conf version, you'll have to overlay it or use system.replaceRuntimeDependencies option to graft it

is there a patch available for alsa-ucm-conf? grafting alsa-ucm-conf with a patch to fix the bug might be easier and have less consequences, and you would even be able to PR the patch stuff to nixpkgs and fix it out-of-the-box for everyone

Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:

environment.systemPackages = with pkgs; [
    r2305.alsa-lib
    r2305.alsa-ucm-conf
    r2305.alsa-utils
    
    ...
 ];

Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.
E.g. pipewire is still using alsa-lib 1.2.9:

✦ ❯ nix-store --query --referrers /nix/store/4gassvc0bjajf1kzjrllp599z6acx2zn-alsa-lib-1.2.9 | grep pipewire
/nix/store/ayj04lvgq3b958gickjx69ry4cqj1lki-pipewire-0.3.84

In reply to @lily:lily.flowers

that is working as intended. if you want applications to use a different alsa-ucm-conf version, you'll have to overlay it or use system.replaceRuntimeDependencies option to graft it

is there a patch available for alsa-ucm-conf? grafting alsa-ucm-conf with a patch to fix the bug might be easier and have less consequences, and you would even be able to PR the patch stuff to nixpkgs and fix it out-of-the-box for everyone

In reply to @lily:lily.flowers

that is working as intended. if you want applications to use a different alsa-ucm-conf version, you'll have to overlay it or use system.replaceRuntimeDependencies option to graft it

is there a patch available for alsa-ucm-conf? grafting alsa-ucm-conf with a patch to fix the bug might be easier and have less consequences, and you would even be able to PR the patch stuff to nixpkgs and fix it out-of-the-box for everyone

In reply to @sporesirius:matrix.org
Yeah, there is a commit. It's a one-line fix, I tried that first, but unfortunately it didn't work, so I tried the method described above.

doing a nixos config like the below should patch in the fix and then graft it into your system. it, uh, doesn't work in pure eval (e.g. flakes) so you'll need to add --impure or something if you use flakes (it also needs IFD, but unless you manually disabled that, it should be enabled):

system.replaceRuntimeDependencies = [
  ({
    original = pkgs.alsa-ucm-conf;
    replacement = pkgs.alsa-ucm-conf.overrideAttrs (oldAttrs: {
      patches = (oldAttrs.patches or []) ++ [
        (fetchpatch {
          name = "alsa-ucm-conf-splitpcm-device-argument-fix.patch";
          url = "https://github.com/alsa-project/alsa-ucm-conf/commit/b68aa52acdd2763fedad5eec0f435fbf43e5ccc6.patch";
          hash = "sha256-8WE4+uhi4W7cCSZYmL7uFpcHJ9muX09UkGXyZIpEd9I=";
        })
      ];
    });
  })
];

and you should be able to PR a diff like this to nixpkgs staging branch:

diff --git a/pkgs/by-name/al/alsa-ucm-conf/package.nix b/pkgs/by-name/al/alsa-ucm-conf/package.nix
index b7203a737638..c77b2024dc4e 100644
--- a/pkgs/by-name/al/alsa-ucm-conf/package.nix
+++ b/pkgs/by-name/al/alsa-ucm-conf/package.nix
@@ -1,4 +1,4 @@
-{ lib, stdenv, fetchurl }:
+{ lib, stdenv, fetchurl, fetchpatch }:
 
 stdenv.mkDerivation rec {
   pname = "alsa-ucm-conf";
@@ -9,6 +9,14 @@ stdenv.mkDerivation rec {
     hash = "sha256-nCHj8B/wC6p1jfF+hnzTbiTrtBpr7ElzfpkQXhbyrpc=";
   };
 
+  patches = [
+    (fetchpatch {
+      name = "alsa-ucm-conf-splitpcm-device-argument-fix.patch";
+      url = "https://github.com/alsa-project/alsa-ucm-conf/commit/b68aa52acdd2763fedad5eec0f435fbf43e5ccc6.patch";
+      hash = "sha256-8WE4+uhi4W7cCSZYmL7uFpcHJ9muX09UkGXyZIpEd9I=";
+    })
+  ];
+
   dontBuild = true;
 
   installPhase = ''