GNU bug report logs - #36126
[PATCH] Add ghc-validation.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36126 in the body.
You can then email your comments to 36126 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: guix-patches <at> gnu.org
Subject: [PATCH] Add ghc-validation.
Date: Fri, 7 Jun 2019 06:51:52 -0500

[Message part 1 (text/plain, inline)]

Hello all,

The version bump pushes guix refresh over the 300-package line. Given
that and the fact that there are dependencies on older versions in the
tree, would it be better to give the newer version a special name
instead, or did I make the correct choice here?

Guix packages are a new foray for me, so I imagine something will be
wrong. Did my best to split into proper dependency order though, and
ready to touch up.

Cheers,

Jacob.

[0004-gnu-ghc-ansi-terminal-Update-to-0.9.1.patch (text/x-patch, attachment)]

[0003-gnu-ghc-ansi-wl-pprint-Use-ghc-ansi-terminal-0.8.patch (text/x-patch, attachment)]

[0002-gnu-Add-ghc-ansi-terminal-0.8.patch (text/x-patch, attachment)]

[0005-gnu-Add-ghc-concurrent-output.patch (text/x-patch, attachment)]

[0001-gnu-Add-ghc-wl-pprint-annotated.patch (text/x-patch, attachment)]

[0006-gnu-Add-ghc-hedgehog.patch (text/x-patch, attachment)]

[0007-gnu-Add-ghc-validation.patch (text/x-patch, attachment)]

Message #8 received at 36126 <at> debbugs.gnu.org (full text, mbox):

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: 36126 <at> debbugs.gnu.org
Subject: Followup.
Date: Sat, 22 Jun 2019 04:18:57 -0500

Got no response for this, and as I haven't contributed before I'm not
sure how to proceed outside of bumping the bug after a couple weeks.

Should I fix something about the patch, close this ticket and reopen a
new one, sit and wait, or something I have not considered?

Thanks,

Jacob.

Message #11 received at 36126 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: 36126 <at> debbugs.gnu.org
Subject: Re: [bug#36126] Followup.
Date: Sat, 22 Jun 2019 20:20:15 +0200

[Message part 1 (text/plain, inline)]

Jacob!

Jacob MacDonald wrote:
> Got no response for this, and as I haven't contributed before 
> I'm not
> sure how to proceed outside of bumping the bug after a couple 
> weeks.

This is absolutely fine!  Sorry about that.  We have too few 
active reviewers (I plead guilty here, too) and those who grok 
Haskell are even rarer (not me, not really…).

Sending a friendly ping after a fortnight or so certainly isn't 
frowned upon.

> Should I fix something about the patch, close this ticket and 
> reopen a
> new one, sit and wait, or something I have not considered?
          ^^^^^^^^^^^^

Let's hope your new message attracts a curious Haskeller.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #16 received at 36126-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: 36126-done <at> debbugs.gnu.org
Subject: Re: [bug#36126] [PATCH] Add ghc-validation.
Date: Tue, 02 Jul 2019 17:57:05 +0200

Hello Jacob,

Jacob MacDonald <jaccarmac <at> gmail.com> skribis:

> The version bump pushes guix refresh over the 300-package line. Given
> that and the fact that there are dependencies on older versions in the
> tree, would it be better to give the newer version a special name
> instead, or did I make the correct choice here?

I think you did it right.  :-)

> Guix packages are a new foray for me, so I imagine something will be
> wrong. Did my best to split into proper dependency order though, and
> ready to touch up.

I applied all 7 patches to ‘master’ (I added a copyright line for you).
It’s above the 300-package line as you write, but these packages build
fairly quickly, so I think it’s OK.

Thanks for the patch set, and apologies for the delay!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.