From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 31319@debbugs.gnu.org
Subject: bug#31319: ghc-case-insensitive: Duplicate 'inputs' field.
Date: Thu, 19 Jul 2018 12:02:48 +0200 [thread overview]
Message-ID: <878t67wnjr.fsf@gnu.org> (raw)
In-Reply-To: <871scliy9p.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 02 Jul 2018 15:05:06 +0200")
Ping!
I’d really like to apply the patch you posted in
<https://lists.gnu.org/archive/html/guix-devel/2018-04/msg00201.html>
along with the corresponding package fixes.
I can do that if you want.
Ludo’.
ludo@gnu.org (Ludovic Courtès) skribis:
> Hello Mark,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> It's true that it wouldn't change anything to simply remove those
>> ignored duplicate field initializers. However, I thought it would be
>> better to give people familiar with these packages an opportunity to
>> investigate. Someone may have had a good reason for adding those
>> inputs, even if they are not strictly needed for a successful build.
>>
>> Of course, at some point we should timeout on this. I would advocate
>> commenting out the redundant duplicates instead of simply deleting them,
>> along with a FIXME comment asking someone to investigate. We could also
>> look in the commit history to find out who added those redundant inputs,
>> and ask them directly.
>>
>> If you're impatient to get the duplicate field detection patch committed
>> soon, I could implement these "timeout" measures in the next couple of
>> days.
>
> I think we should go ahead now and mechanically fix packages with
> duplicate fields, and apply the duplicate detection patch.
>
> Would you like to do that?
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2018-07-19 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 17:49 bug#31319: ghc-case-insensitive: Duplicate 'inputs' field Mark H Weaver
2018-05-09 22:34 ` Ludovic Courtès
2018-05-10 17:59 ` Mark H Weaver
2018-05-10 20:30 ` Ludovic Courtès
2018-07-02 13:05 ` Ludovic Courtès
2018-07-19 10:02 ` Ludovic Courtès [this message]
2018-07-20 21:23 ` Mark H Weaver
2019-01-22 22:06 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t67wnjr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31319@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).