-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
keyfinder has no binaries #18475
Comments
cc @nckx |
(triage) still reproducible? |
I don’t know |
@michalrus can you check? |
Sorry, I meant that I don’t know yet, but it’ll be hard to find some time to check (where did all my time go to ;( ;( ;( ), but I’ll try to soon |
(triage) close? |
Tested on unstable: ping @michalrus |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
Please revisit this. The binary is only thing installed from this package.
|
@lasers Version 2.4 contains exactly zero functional changes compared to 2.2: ibsh/is_KeyFinder@2.2...master |
The KeyFinder derivation should also import That said, KeyFinder is apparently unmaintained upstream, and won't compile against In the above bug report about this, you will see their was a recommendation to switch to Mixxx or keyfinder-cli (both of which are part of nixpkgs). |
|
Right. Thanks for doing that. I would think this could be closed as it sounds like the issue is the original submitter looked for |
Issue description
There’s no KeyFinder executable in path, after installing keyfinder — https://github.com/NixOS/nixpkgs/blob/e9379f7416d04b6b7ff475816b0aa395c1e3f7f9/pkgs/applications/audio/keyfinder/default.nix
Steps to reproduce
Technical details
The text was updated successfully, but these errors were encountered: