From: Lars-Dominik Braun <lars@6xq.net>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: john.kehayias@protonmail.com, rekado@elephly.net,
philip@munksgaard.me, 50843@debbugs.gnu.org
Subject: [bug#50843] [PATCHES] Stackage update to 18.10.
Date: Sat, 2 Oct 2021 11:45:11 +0200 [thread overview]
Message-ID: <YVgqJ27OsHjc4gdK@noor.fritz.box> (raw)
In-Reply-To: <877dewlktp.fsf@yoctocell.xyz>
Hi,
> * What exacty does the TODO comment for ‘ghc-hsyaml’ mean? The
> ‘native-inputs’ comment should also be removed if tests aren’t
> enabled. This applies to ‘ghc-stmonadtrans’ as well
it means enabling tests/native-inputs creates a package dependency loop
somewhere in the graph. I’d keep the commented out native-inputs
though. Otherwise whoever wants to fix this has to add them again from
scratch. Unless there are other reasons to remove them?
> * The ‘inputs’ comments for ‘ghc-silently’ should probably be removed.
You’re right, fixed.
> I noticed that a lot of new packages have been auto-generated and added
> as-is, without checking licenses and fixing descriptions. I have
> attached a patch that fixes these (I hope I didn’t miss any packages).
Sorry, I ran out of time at the end and couldn’t fix them. I fixed
some brackets and pushed it, thank you for doing this tedious work.
Cheers,
Lars
next prev parent reply other threads:[~2021-10-02 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 11:14 [bug#50843] [PATCHES] Stackage update to 18.10 Lars-Dominik Braun
2021-09-27 18:31 ` John Kehayias via Guix-patches via
2021-09-29 12:02 ` Lars-Dominik Braun
2021-10-01 17:24 ` Xinglu Chen
2021-10-02 9:45 ` Lars-Dominik Braun [this message]
2021-10-03 11:35 ` Xinglu Chen
2021-10-04 7:27 ` zimoun
2021-10-08 7:28 ` bug#50843: " Lars-Dominik Braun
2021-10-08 13:53 ` [bug#50843] " Xinglu Chen
2021-10-08 14:23 ` John Kehayias via Guix-patches via
[not found] ` <handler.50843.D50843.163367810626298.notifdone@debbugs.gnu.org>
2021-10-08 22:47 ` Ludovic Courtès
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=YVgqJ27OsHjc4gdK@noor.fritz.box \
--to=lars@6xq.net \
--cc=50843@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=philip@munksgaard.me \
--cc=public@yoctocell.xyz \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.