From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Update to GHC 9.0.2/Stackage LTS-19.0
Date: Thu, 28 Apr 2022 02:47:16 +0200 [thread overview]
Message-ID: <20220428004716.Gda6bguAQRz-w7y9O5KsZo0IYj2OHiVVwHHAdFEcno8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36292@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
There's a closed pull request on the void-packages repository
Update to GHC 9.0.2/Stackage LTS-19.0
https://github.com/void-linux/void-packages/pull/36292
Description:
And so... the ~~hunt~~ fun begins again!
### Core packages to bump
- [x] ghc
- [ ] ghc-bin
- [x] x86_64-musl [Link](https://download1640.mediafire.com/02oxtdmod6tg/2g0umndrffyechx/ghc-9.0.2-x86_64-void-linux-musl.tar.xz) **Not uploaded yet**
cc. @q66 for the following
- [ ] ppc64le
- [ ] ppc64le-musl
- [x] aarch64 [Link](https://ftrv.se/_/void/ghc-9.0.2/ghc-9.0.2-aarch64-void-linux.tar.xz) **Not uploaded yet**
- [x] aarch64-musl [Link](https://ftrv.se/_/void/ghc-9.0.2/ghc-9.0.2-aarch64-void-linux-musl.tar.xz) **Not uploaded yet**
- [x] cabal-install
- [x] stack
#### Rebuild literally every single haskell package we have and see if anything's broken
Most of these are already done, things should probably go smoothly as 9.0.x does not contain any big breaking changes.
- [x] git-mediate
- [x] kmonad
- [x] cgrep
- [x] debug-me
- [x] hlint
- [x] hoogle
- [x] darcs
- [x] shellcheck
- [x] git-annex
- [x] hledger
- [x] pandoc (contains a fix for `pandoc-crossref` on musl \o/)
- [x] xmobar
- [x] haskell-language-server
### Other things to do
- [x] Either incorporate https://github.com/void-linux/void-packages/pull/36193 into this PR or merge it first and then rebuild GHC for aarch64 and aarch64-musl; cc. @ftrvxmtrx
Closes https://github.com/void-linux/void-packages/pull/36193
[ci skip]
next prev parent reply other threads:[~2022-04-28 0:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 7:20 [PR PATCH] [WIP] " slotThe
2022-03-23 20:31 ` ftrvxmtrx
2022-03-23 20:40 ` ftrvxmtrx
2022-03-24 10:51 ` [PR PATCH] [Updated] " slotThe
2022-03-24 10:51 ` slotThe
2022-03-24 11:34 ` slotThe
2022-03-24 13:37 ` slotThe
2022-03-24 23:05 ` ftrvxmtrx
2022-03-25 12:11 ` [PR PATCH] [Updated] " slotThe
2022-03-25 13:14 ` slotThe
2022-03-25 13:15 ` [PR PATCH] [Updated] " slotThe
2022-03-25 13:44 ` slotThe
2022-03-26 16:43 ` ftrvxmtrx
2022-03-28 16:15 ` ftrvxmtrx
2022-03-30 13:44 ` ftrvxmtrx
2022-03-31 17:15 ` [PR PATCH] [Updated] " slotThe
2022-03-31 17:16 ` slotThe
2022-04-03 11:51 ` ftrvxmtrx
2022-04-23 5:51 ` slotThe
2022-04-23 5:51 ` slotThe
2022-04-28 0:47 ` q66 [this message]
2022-04-28 0:47 ` q66
2022-05-03 10:12 ` Piraty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220428004716.Gda6bguAQRz-w7y9O5KsZo0IYj2OHiVVwHHAdFEcno8@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).