!XrtRvzcHOrHtSKARne:nixos.org

NixOS Audio

134 Members
35 Servers

Load older messages

SenderMessageTime
3 Dec 2023
@fractivore:cyberia.clubsymysIn all seriousness, I'd be willing to help, but just know that it would be my first true packaging project.03:08:13
@gdesforges:matrix.orgGuillaume DesforgesWorry not, the nix community is helpful 09:27:07
@gdesforges:matrix.orgGuillaume Desforges You can ask questions in #dev:nixos.org for instance 09:28:00
@gdesforges:matrix.orgGuillaume DesforgesBut nobody will do the work for you ;)09:28:24
@ThorHop:matrix.orgIdeallyYes changed their display name from hopland (valorent vicky) to hopland (meticulous montesquieu).14:08:35
@sporesirius:matrix.orgSporesirius joined the room.22:31:31
4 Dec 2023
@noiobeforebedtime:winesj.comJack​ joined the room.03:20:13
5 Dec 2023
@federicodschonborn:matrix.orgFederico Damián Schonborn changed their profile picture.00:39:07
@fractivore:cyberia.clubsymysSpotify isn't open source though. Is it really compatible with nix packaging?13:10:13
@Minijackson:matrix.orgMinijacksonthere is quite a number of non open-source software packaged in nixpkgs13:10:56
@Minijackson:matrix.orgMinijacksonif for example spotify is distributed as a flatpak app, there are functions to handle that13:11:24
@fractivore:cyberia.clubsymysWait, also it is open source now13:11:33
@Minijackson:matrix.orgMinijacksonsteam, as another example, constructs a whole "chroot" to make it happy13:11:50
@Minijackson:matrix.orgMinijackson
In reply to @fractivore:cyberia.club
Wait, also it is open source now
even better :D 		13:11:54
@fractivore:cyberia.clubsymysWait, nooo, they just have open sourced components of the platform.13:13:38
@gdesforges:matrix.orgGuillaume Desforges
In reply to @fractivore:cyberia.club
Wait, also it is open source now
Wait wat 		13:26:50
@gdesforges:matrix.orgGuillaume Desforges
In reply to @fractivore:cyberia.club
Wait, nooo, they just have open sourced components of the platform.
You got me there for a second 		13:27:18
@fractivore:cyberia.clubsymysSo spotify is already packaged, but it's the snapcraft version? https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/applications/audio/spotify/linux.nix19:02:23
@fractivore:cyberia.clubsymysI don't really see why we need to repackage it without snapcraft19:02:48
@fractivore:cyberia.clubsymysAlso spotify requires a specific minor version of openssl?? lool that doesn't seem great right?19:04:17
@fractivore:cyberia.clubsymysIt looks like they worked around it by linking the system openssl version to a file named like the one spotify is expecting.19:05:45
@gdesforges:matrix.orgGuillaume Desforges
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.
That's my jam 		19:21:45
@fractivore:cyberia.clubsymysIt's a pretty cool hack yeah.21:40:51
7 Dec 2023
@sporesirius:matrix.orgSporesirius

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.

21:04:34
@sporesirius:matrix.orgSporesirius *

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.

21:04:47
@sporesirius:matrix.orgSporesirius *

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.

21:05:04
@sporesirius:matrix.orgSporesirius *

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.

21:05:38
@lily:lily.flowers@lily:lily.flowers
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

21:09:33
@sporesirius:matrix.orgSporesirius *

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
21:09:38
@sporesirius:matrix.orgSporesirius
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

Yeah, there is a commit. It's a one line fix, I tried that first, but unfortunately that didn't work, so I tried the method describe above. 		21:12:42

Show newer messages

Back to Room ListRoom Version: 9