signal-cli missing dependency: junixsocket

[wamserma]

Describe the bug

signal-cli -u MYNUMBER daemon should start the daemon but states junixsocket is missing.

To Reproduce Steps to reproduce the behavior:

1. register a number with signal-cli, see https://gist.github.com/wamserma/5889730d80de23db680cc56689196acb
2. run `signal-cli -u YOUR_NUMBER daemon'

Expected behavior The daemon starts.

related: https://github.com/NixOS/nixpkgs/issues/82889

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.109, NixOS, 19.09.2260.3b9b10e49be (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.3`
 - channels(root): `"nixos-19.09.2260.3b9b10e49be, unstable-20.09pre215333.42f0be81ae0"`
 - channels(markus): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute: junixsocket signal-cli

[stale[bot]]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.