first of all i’m super excited to get my first stake pool up and running however I have run into an issue even before I can get the binaries compiled. On a clean install of 1.14.1 I get ‘Could not resolve dependencies exception’
[root@ip-10-20-1-115 cardano-node]# cabal install cardano-node cardano-cli -- installdir="$HOME/.local/bin"
cabal: Could not resolve dependencies:
[__0] next goal: cardano-crypto-class (user goal)
[__0] rejecting: cardano-crypto-class-2.0.0 (conflict: pkg-config package
libsodium-any, not found in the pkg-config database)
[__0] fail (backjumping, conflict set: cardano-crypto-class)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-crypto-class
Switching back to the 1.13.0 or the 1.13.0-rewards everything works fine - I am missing something here or anyone else faced this issue?
It is considered invalid because the method used by install.md should not depend/use system libsodium, which is IOHK’s lesser of two approaches they recommend in the mentioned guide above.
Frankly both methods and build process is ridiculous! You do not need install GB’s of static binaries to compile something which could be a self contained binary and copied to target hosts / containers.
Can you please explain to me: Which requires a special fork of libsodium with the VRF code to be installed on the system which fork of libsodium should I use?
Do not trust third-party prebuilt binaries. Especially ones who advertise themselves as cardano-builder and behind the scenes are just providing prebuilt binaries.
The same entity was also responsible for raiding funds from faucet unethically before - thus, raising even more questions (in my view).
There will be prebuilt binaries with checksum from IOHK when they’re closer to releases, and there are hydra jobs from CI if you really want them.
The details regarding fork of libsodium are in readme of the repository.
I think your project already includes the libsodium install if I am reading it correctly. I would love to contribute if I can, but I don’t really know enough about Ansible to do so. I just wanted to add the raw steps for other developers who may find this thread. FWIW I’m just doing this install to learn to build with Plutus – I am certain that pool operators will prefer to have automation handling this as you’ve laid out.
a pointless post so moderators can share pointless time lost due to shite engineering decisions and terrible implimentation instructions. might as well be ethereum
