-
Notifications
You must be signed in to change notification settings - Fork 38
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
Request for Debian bullseye/stable-based images #73
Comments
It seems cabal-install and ghc provide Debian 10 binaries but not yet 11. |
Yep, my understanding is it will come 'soon' based on the work around https://gitlab.haskell.org/ghc/ghc/-/issues/21002 . Not sure about the cabal side of things, but presumably if GHC is providing it cabal will also follow suit. |
9.4.1 support amd64 deb11, however aarch64 support is not yet included. The images need to support both processor architectures, so we will need to wait. deb11 aarch64 support is scheduled for 9.4.3. |
cabal 3.8 does not support deb11 unfortunately. If someone is motivated they could raise the issue with the cabal folk. |
I created haskell/cabal#8376 |
EOL of Buster is approaching, so this should probably be prioritized. Any more blockers? |
No longer a maintainer, but I think GHC is still not providing deb11 for aarch64 https://downloads.haskell.org/~ghc/9.8.1/ . Perhaps it will come with 9.10.1 https://gitlab.haskell.org/ghc/ghc/-/issues/22005 |
Pleased to see deb11 builds have appeared at https://downloads.haskell.org/~ghc/9.10.1-alpha1/ |
I know, right? Is there anything we could do @jmtd? Say, move to deb12 and use deb11 bindists? |
Upstream tracking issue: https://gitlab.haskell.org/ghc/ghc/-/issues/25077 |
https://gitlab.haskell.org/ghc/ghc/-/issues/25077 seems to have been resolved. |
Debian 11 "bullseye" came out in August 2021, and at that point stable came to mean Bullseye, and oldstable to mean Buster.
hub.docker.com/_/haskell says
This is currently not correct. Please consider providing bullseye-based images. Thanks!
The text was updated successfully, but these errors were encountered: