jose-jwt doctests failing due to "Ambiguous interface"

[DanBurton]

Even though I added the non-cryptonite packages to the hide section of build-constraints.yaml, these errors still occurred.

> /tmp/stackage-build12/jose-jwt-0.7.4$ dist/build/doctests/doctests

Jose/Internal/Base64.hs:8:1: warning: [-Wdeprecations]
    Module ‘Control.Monad.Error’ is deprecated:
      Use Control.Monad.Except instead

Jose/Jwk.hs:23:1: error:
    Ambiguous interface for ‘Crypto.Random’:
      it was found in multiple packages:
      crypto-random-0.0.9 cryptonite-0.21 crypto-api-0.13.2

Jose/Jwk.hs:24:1: error:
    Ambiguous interface for ‘Crypto.PubKey.RSA’:
      it was found in multiple packages:
      crypto-pubkey-0.2.8 cryptonite-0.21

Jose/Jwk.hs:25:1: error:
    Ambiguous interface for ‘Crypto.PubKey.ECC.ECDSA’:
      it was found in multiple packages:
      crypto-pubkey-0.2.8 cryptonite-0.21

Jose/Jwk.hs:27:1: error:
    Ambiguous interface for ‘Crypto.Number.Serialize’:
      it was found in multiple packages:
      crypto-numbers-0.2.7 cryptonite-0.21

[bergmark]

@DanBurton are you sure the hidden packages were rebuilt?

[DanBurton]

@bergmark I thought the build script might take care of it. Apparently not? Do we have a "best practice" for forcing a select few packages to rebuild?

[bergmark]

Maybe @snoyberg knows a good way to do it? I hackety hacked it last time by adding an upper bound to force a rebuild, and then lifting it again.

[juhp]

Might be better now after #2181?