Skip to content

Build with 9.14#1065

Draft
kushagarr wants to merge 1 commit into
brendanhay:mainfrom
kushagarr:build_with_9.14
Draft

Build with 9.14#1065
kushagarr wants to merge 1 commit into
brendanhay:mainfrom
kushagarr:build_with_9.14

Conversation

@kushagarr

@kushagarr kushagarr commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

This should also close #1035

endgame
endgame reviewed Jun 11, 2026
View reviewed changes

@endgame endgame left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to merge a PR with allow-newers because I want to keep HEAD as close to releasable as possible. Let's wait for the dependent libraries to update first. Do they have PRs yet?

Also, why have we raised the lower bound on crypton?

@kushagarr

kushagarr commented Jun 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Yes, the PRs for those packages are already there. They either need to merge it and make a new release or just make a revision on hackage.
Also if I keep the lower bound for crypton like this >=0.32 && < 0.35 || >=1.1.1 && <1.2 , cabal picks up 0.34 version of crypton and the build fails. Not sure what's the mechanism to make it include the latest one for 9.14.

@endgame

endgame commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

If old crypton does not work with new GHC then there's an upper bound revision that needs to be made. Is there an issue raised against crypton to make the necessary metadata revisions?

Do you have links for the PRs against those dependency packages?

@kushagarr

kushagarr commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

stevenfontanella/microlens#195
stevenfontanella/microlens#194
dmwit/ordered-containers#36

I don't think there is any issue raised against crypton for this for the upper bound revision, but I could be wrong, please check that bit.

@endgame

endgame commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

I need the exact information about the build failure, because cabal repl -b 'crypton == 0.34' worked for me with ghc-9.14.1.

@kushagarr

kushagarr commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author 
root@4014491f106d:/progs/haskell/amazonka/lib/amazonka-core# cabal build amazonka-core
Configuration is affected by cabal.project at '/progs/haskell/amazonka'.
Resolving dependencies...
Build profile: -w ghc-9.14.1 -O1
In order, the following will be built (use -v for more details):
 - amazonka-core-2.0 (lib) (configuration changed)
Configuring library for amazonka-core-2.0...
Preprocessing library for amazonka-core-2.0...
Building library for amazonka-core-2.0...
[ 3 of 31] Compiling Amazonka.Crypto  ( src/Amazonka/Crypto.hs, /progs/haskell/amazonka/dist-newstyle/build/aarch64-linux/ghc-9.14.1/amazonka-core-2.0/build/Amazonka/Crypto.o, /progs/haskell/amazonka/dist-newstyle/build/aarch64-linux/ghc-9.14.1/amazonka-core-2.0/build/Amazonka/Crypto.dyn_o ) [Crypto.MAC.HMAC package changed]
src/Amazonka/Crypto.hs:41:12: error: [GHC-39999]
    • Could not deduce ‘memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
                          a’
        arising from a use of ‘HMAC.hmac’
      from the context: ByteArrayAccess a
        bound by the type signature for:
                   hmacSHA1 :: forall a.
                               ByteArrayAccess a =>
                               Key -> a -> HMAC.HMAC Hash.SHA1
        at src/Amazonka/Crypto.hs:40:1-64
      Possible fix:
        add (memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
               a) to the context of
          the type signature for:
            hmacSHA1 :: forall a.
                        ByteArrayAccess a =>
                        Key -> a -> HMAC.HMAC Hash.SHA1
    • In the expression: HMAC.hmac
      In an equation for ‘hmacSHA1’: hmacSHA1 = HMAC.hmac
   |
41 | hmacSHA1 = HMAC.hmac
   |            ^^^^^^^^^

src/Amazonka/Crypto.hs:44:14: error: [GHC-39999]
    • Could not deduce ‘memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
                          a’
        arising from a use of ‘HMAC.hmac’
      from the context: ByteArrayAccess a
        bound by the type signature for:
                   hmacSHA256 :: forall a.
                                 ByteArrayAccess a =>
                                 Key -> a -> HMAC.HMAC Hash.SHA256
        at src/Amazonka/Crypto.hs:43:1-68
      Possible fix:
        add (memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
               a) to the context of
          the type signature for:
            hmacSHA256 :: forall a.
                          ByteArrayAccess a =>
                          Key -> a -> HMAC.HMAC Hash.SHA256
    • In the expression: HMAC.hmac
      In an equation for ‘hmacSHA256’: hmacSHA256 = HMAC.hmac
   |
44 | hmacSHA256 = HMAC.hmac
   |              ^^^^^^^^^

src/Amazonka/Crypto.hs:47:12: error: [GHC-39999]
    • Could not deduce ‘memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
                          a’
        arising from a use of ‘Hash.hashWith’
      from the context: ByteArrayAccess a
        bound by the type signature for:
                   hashSHA1 :: forall a.
                               ByteArrayAccess a =>
                               a -> Hash.Digest Hash.SHA1
        at src/Amazonka/Crypto.hs:46:1-59
      Possible fix:
        add (memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
               a) to the context of
          the type signature for:
            hashSHA1 :: forall a.
                        ByteArrayAccess a =>
                        a -> Hash.Digest Hash.SHA1
    • In the expression: Hash.hashWith Hash.SHA1
      In an equation for ‘hashSHA1’: hashSHA1 = Hash.hashWith Hash.SHA1
   |
47 | hashSHA1 = Hash.hashWith Hash.SHA1
   |            ^^^^^^^^^^^^^

src/Amazonka/Crypto.hs:50:14: error: [GHC-39999]
    • Could not deduce ‘memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
                          a’
        arising from a use of ‘Hash.hashWith’
      from the context: ByteArrayAccess a
        bound by the type signature for:
                   hashSHA256 :: forall a.
                                 ByteArrayAccess a =>
                                 a -> Hash.Digest Hash.SHA256
        at src/Amazonka/Crypto.hs:49:1-63
      Possible fix:
        add (memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
               a) to the context of
          the type signature for:
            hashSHA256 :: forall a.
                          ByteArrayAccess a =>
                          a -> Hash.Digest Hash.SHA256
    • In the expression: Hash.hashWith Hash.SHA256
      In an equation for ‘hashSHA256’:
          hashSHA256 = Hash.hashWith Hash.SHA256
   |
50 | hashSHA256 = Hash.hashWith Hash.SHA256
   |              ^^^^^^^^^^^^^

src/Amazonka/Crypto.hs:53:11: error: [GHC-39999]
    • Could not deduce ‘memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
                          a’
        arising from a use of ‘Hash.hashWith’
      from the context: ByteArrayAccess a
        bound by the type signature for:
                   hashMD5 :: forall a. ByteArrayAccess a => a -> Hash.Digest Hash.MD5
        at src/Amazonka/Crypto.hs:52:1-57
      Possible fix:
        add (memory-0.18.0:Data.ByteArray.Types.ByteArrayAccess
               a) to the context of
          the type signature for:
            hashMD5 :: forall a. ByteArrayAccess a => a -> Hash.Digest Hash.MD5
    • In the expression: Hash.hashWith Hash.MD5
      In an equation for ‘hashMD5’: hashMD5 = Hash.hashWith Hash.MD5
   |
53 | hashMD5 = Hash.hashWith Hash.MD5
   |           ^^^^^^^^^^^^^

Error: [Cabal-7125]
Failed to build amazonka-core-2.0.

root@4014491f106d:/progs/haskell/amazonka/lib/amazonka-core#

This is the entry in amazonka-core.cabal

, crypton >=0.32 && <0.35 || >=1.1.1 && <1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@endgame endgame endgame left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

containers-0.8 compat

2 participants

@kushagarr @endgame