Skip to content
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

[WIP] spotifyd: init at 0.2.2 #47172



Copy link

Motivation for this change

Spotifyd is a daemon for Spotify. It is especially useful for headless servers that need to be able to play songs from Spotify.

This PR includes a basic implementation for a spotifyd module.

This PR is WIP because the package was not able to build. This problem is related to #30742.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Fits

Copy link

Any progress on this? On the unstable channel, I was able to successfully build. But on execution it aborts as soon as I try to connect over Spotify Connect—illegal hardware instruction.

Copy link
Member Author

I still cannot get this to build. What have you done specifically to get the binaries?

Copy link

I checked out the nixos-unstable branch (at commit bc41317e24317b0f506287f2d5bab00140b9b50e). I then manually copied your spotifyd package (714034d), manually commenting out the cargoBuildFlags line. Then nix-env -iA nixpkgs.spotifyd worked.

@jmgrosen jmgrosen mentioned this pull request Feb 17, 2019
10 tasks
Copy link

flokli commented Feb 17, 2019

closing in favor of #55923.

@flokli flokli closed this Feb 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging this pull request may close these issues.

None yet

5 participants