-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module pipewireLowLatency causes build failure #161
Comments
The directory should be generated if not available, as per how |
I haven't tried it on my actual machine yet but I get the same error in the CI pipeline that updates my flake.lock - https://github.com/e-nikolov/nix-config/actions/runs/8061032114/job/22018053387?pr=421
The only relevant change seems to be the update to nixpkgs. So probably the latest batch of commits to nixpkgs-unstable broke this. |
Could you see if pointing your input at #162 resolves the issue? |
I get another error now - https://github.com/e-nikolov/nix-config/actions/runs/8063764183/job/22026253959?pr=421
|
In case it's useful, I think these are the recent commits to nixpkgs that contain pipewire related changes: Coming from those PRs: |
do you override nix-gaming's instance of nixpkgs? |
Yes, I do |
NixOS/nixpkgs@8ba76f8 added extraConfig, not sure why it wouldn't be available. I'll take another look |
oversight on my behalf, try now please |
Now I get
|
I'd really like to know why your |
This is going to be a weird question, but do you have wireplumber enabled? |
I don't have anything about wireplumber in my nix-configs. I also haven't seen it mentioned in the docs for nix-gaming. Do I have to enable it? Things seemed to work fine until today. |
should be enabled by defaulting according to the option docs |
environment.etc.wireplumber.source = "${configs}/share/wireplumber"; I think one of the recent changes in nixpkgs-unstable creates the "/etc/wireplumber" directory and it somehow prevents the
Do you by any chance have something like this in your flake: inputs.nix-gaming.follows = "nixpkgs";
inputs.nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable"; I think commit that causes the issue is only on nixpkgs-unstable and not on nixos-unstable yet. |
They also have: pathsToLink = [ "/share/wireplumber" ]; and a new configPackages option. Perhaps the correct way to add the low latency config is via a package that outputs to |
I am currently using Progress tracker for the PRs: |
I follow nixpkgs-small for my nix-gaming input. Might be why I did not came across that warning. |
No, we should not need to ship a package to be able to provide rules. |
Looks like these changes have landed in |
Updated nixpkgs @ #162. Should be good for a merge, but testing would be appreciated. |
Just tried it and I still have the build failure. |
Are you overriding your nixpkgs input locally? |
Okay what the hell, they are forcing us to provide configs as a package. |
As per NixOS/nixpkgs#291946, we are no longer able to write to I've found that using writeTextDir is able to conform to the new format, and hopefully fixed it until another maintainer high on shroom decides they don't like how things, yknow, work. Once again, testing is appreciated. |
It looks like your PR fixes it now, at least on my machine @NotAShelf |
Same here |
Sorry for causing this breakage! By no means did I intend to make wireplumber harder to configure and an From what I can tell an Note: I added that assertion to at least get users with this breakage a slightly better error message. I maybe should have added a note on an |
From what I understand, WirePlumber itself has gotten a breaking change and is moving the config files to
That is correct. |
NixOS/nixpkgs#292115 will add |
Attempting to build on nixos-unstable with the
services.pipewire.lowLatency.enable = true
causes the build to failed due to the usage ofenvironment.etc."pipewire/pipewire-pulse.d"
Error message:
mkdir: cannot create directory '/nix/store/mhzd8fy047lqcp72lmakmi7rlaap31zf-etc/etc/pipewire/pipewire-pulse.d': Permission denied
The text was updated successfully, but these errors were encountered: