-
-
Notifications
You must be signed in to change notification settings - Fork 14k
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
tuxedo-keyboard: 3.2.14 -> 4.6.2 #337287
tuxedo-keyboard: 3.2.14 -> 4.6.2 #337287
Conversation
@blanky0230 may you have a look. Would be really nice this fix could be merged. |
I've just been trying to use this update but I get a |
how exactly do you try it out? My nixos knowledge is still q bit limited |
I downloaded the raw
which mimics |
Mhh ok I can't build due to a conflict :-(
|
Does this conflict with #336633? |
Not sure, I added this
Which then fails with
It takes the wrong driver version (3.2.14), so I guess I am doing something wrong anything |
If you've got 'hardware.tuxedo-keyboard.enable = true;' or you are using `hardware.tuxedo-rs.enable = true;' or anything then it'll be pulling in the original 'tuxedo-keyboard' derivation. You'll need to add 'hardware.tuxedo-keyboard.enable = lib.mkForce false;' to prevent this original (3.2.14) derivation from being used. For what its worth I think that #336633 does fix this problem - but it will need 'tuxedo-rs' to implement using 'tuxedo-drivers' rather than 'tuxedo-keyboard' if that's what you are using. |
Ahh I see, that makes sense - I slowly getting the grasp of it.... |
Description of changes
Fixes #337072
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.