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

hyperdex: could not exec replicant #17995

Closed
tari opened this issue Aug 25, 2016 · 2 comments
Closed

hyperdex: could not exec replicant #17995

tari opened this issue Aug 25, 2016 · 2 comments

Comments

@tari
Copy link
Contributor

tari commented Aug 25, 2016

Issue description

Starting the HyperDex coordinator by running hyperdex coordinator does most of its work by re-executing replicant, which must be on PATH. This does not work with the current derivation.

This could be fixed either by ensuring replicant is added to PATH (would making it a propagated build input be sufficient?) or patching hyperdex to exec replicant by its store path.

Steps to reproduce

Install hyperdex, run hyperdex coordinator. It fails.

Technical details

  • System: 16.03.1242.c5cbda2 (Emu)
  • Nix version: nix-env (Nix) 1.11.2
  • Nixpkgs version: 16.03.1242.c5cbda2
@teh
Copy link
Contributor

teh commented Sep 2, 2016

Thanks! Upstream hyperdex is not super maintained and in my experience not stable enough to be used in production. I vote for removing it from nixos. @tari are you relying in hyperdex in nixos or is are you just testing?

[1]
https://github.com/rescrv/HyperDex/commits/master

@tari
Copy link
Contributor Author

tari commented Sep 2, 2016

I was just testing, not relying on it. Removal sounds okay to me.

Alternately, I tested and adding replicant to propagatedUserEnvPkgs (in addition to buildInputs) fixes the problem.

joachifm added a commit that referenced this issue Sep 6, 2016
Remove broken hyperdex package and dependencies. Closes #17995.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants