Cannot get upgrade to work

Staking & Delegation Operate a Stake Pool
1

I am currently on 8.1.2 trying to get to 8.7.x and for the life of me I can’t get the installation process to work no matter which set of instructions I use. I’ve gone through them step-by-step five or six times and it always results in the same error:

Error: cabal: Could not resolve dependencies:
[__0] trying: cardano-node-8.7.3 (user goal)
[__1] trying: ouroboros-consensus-0.14.0.0 (dependency of cardano-node)
[__2] trying: cardano-ledger-binary-1.2.1.0 (dependency of
ouroboros-consensus)
[__3] trying: vector-0.13.1.0 (dependency of ouroboros-consensus)
[__4] next goal: cardano-crypto-class (dependency of cardano-node)
[__4] rejecting: cardano-crypto-class-2.1.4.0 (conflict: pkg-config package
libblst-any, not found in the pkg-config database)
[__4] rejecting: cardano-crypto-class-2.1.3.0 (conflict: vector==0.13.1.0,
cardano-crypto-class => vector<0.13)
[__4] skipping: cardano-crypto-class-2.1.2.0, cardano-crypto-class-2.1.1.0,
cardano-crypto-class-2.1.0.2, cardano-crypto-class-2.1.0.1,
cardano-crypto-class-2.1.0.0 (has the same characteristics that caused the
previous version to fail: excludes 'vector' version 0.13.1.0)
[__4] rejecting: cardano-crypto-class-2.0.0.1 (conflict: cardano-ledger-binary
=> cardano-crypto-class>=2.1)
[__4] skipping: cardano-crypto-class-2.0.0.0.1, cardano-crypto-class-2.0.0
(has the same characteristics that caused the previous version to fail:
excluded by constraint '>=2.1' from 'cardano-ledger-binary')
[__4] fail (backjumping, conflict set: cardano-crypto-class,
cardano-ledger-binary, cardano-node, vector)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-crypto-class, cardano-node,
cardano-ledger-binary, vector, ouroboros-consensus
Try running with --minimize-conflict-set to improve the error message.

Anyone have any tips they can provide?

2

Did you already install BLST?

3

Yes, four times now.

4

And cabal update?

5

Yes, I did that as well… Unfortunately I couldn’t get it to work after several hours so I ended up upgrading a different node and just copying the bin folder over.

6

Hi, I’ve had to fight too to build new release on aarch64,
the key for me was to use GHC 9.6.3

Here ‘ghcup tui’ tool screenshot
Schermata del 2024-02-04 09-39-29

1 Like
7

You might find that cardano-node 8.7.2 (and probably 8.7.3) segfaults on aarch64 machines when compiled with ghc 9.6.3. See my previous post about this, which I believe results from a known Haskell bug: Experience with v8.7.2 - #4 by Terminada

8

Since now no problem, no segfault, but unfortunately 9.6.3 it’s the only GHC version I can use to compile it, the others don’t.

I’ve cabal.project.local settings too like:

package cardano-crypto-praos
flags: -external-libsodium-vrf
package trace-dispatcher
ghc-options: -Wwarn
package HsOpenSSL
flags: -homebrew-openssl