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