From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] GHC 8.10.7
Date: Fri, 11 Mar 2022 14:43:19 +0100 [thread overview]
Message-ID: <20220311134319.q6DQkOWLkkcxriAzCKOe5JG5ALuJ3ZZB6CzOhXRykBc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33850@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
There's a closed pull request on the void-packages repository
[WIP] GHC 8.10.7
https://github.com/void-linux/void-packages/pull/33850
Description:
The 8.10.x release flood seems to have stopped; time for the fun part to begin!
- [x] ghc
- [ ] ghc-bin
- [x] x86_64-musl (**Not uploaded to alpha.de yet** [Link](https://www.mediafire.com/file/i2385lbvjbmzx3l/ghc-8.10.7-x86_64-void-linux-musl.tar.xz/file))
cc @q66 for the following
- [ ] ppc64le
- [ ] ppc64le-musl
- [x] cabal-install
- [x] stack
Rebuild literally every single haskell package we have and see if anything's broken:
- [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
- [x] xmobar
- [x] haskell-language-server
Other things to do:
- [x] Merge https://github.com/void-linux/void-packages/pull/33749
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
[ci skip]
prev parent reply other threads:[~2022-03-11 13:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 16:44 [PR PATCH] " slotThe
2021-11-02 7:56 ` [PR PATCH] [Updated] " slotThe
2021-11-03 18:18 ` slotThe
2021-11-04 12:15 ` xaltsc
2021-11-05 6:23 ` [PR PATCH] [Updated] " slotThe
2021-11-05 6:26 ` slotThe
2021-11-08 19:11 ` Chocimier
2021-11-10 11:05 ` [PR PATCH] [Updated] " slotThe
2021-11-10 11:06 ` slotThe
2021-11-15 10:54 ` slotThe
2022-01-26 10:13 ` [PR PATCH] [Updated] " slotThe
2022-01-26 10:15 ` slotThe
2022-01-26 15:42 ` q66
2022-01-26 16:05 ` slotThe
2022-02-22 19:22 ` [PR PATCH] [Updated] " slotThe
2022-02-22 20:14 ` slotThe
2022-02-28 21:50 ` q66
2022-03-05 6:51 ` [PR PATCH] [Updated] " slotThe
2022-03-05 6:52 ` slotThe
2022-03-11 13:43 ` q66 [this message]
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=20220311134319.q6DQkOWLkkcxriAzCKOe5JG5ALuJ3ZZB6CzOhXRykBc@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).