From: zimoun <zimon.toutoune@gmail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 62861@debbugs.gnu.org
Subject: [bug#62861] [PATCH v1] gnu: ghc-basement: fix build for i686
Date: Tue, 16 May 2023 16:13:02 +0200 [thread overview]
Message-ID: <86r0rg5pqp.fsf@gmail.com> (raw)
In-Reply-To: <20230415135921.1266-1-GNUtoo@cyberdimension.org> (Denis Carikli's message of "Sat, 15 Apr 2023 15:59:21 +0200")
Hi Denis,
This submission #62861 [1] contains two patches. Are they part of the
same series?
1: http://issues.guix.gnu.org/issue/62861
On Sat, 15 Apr 2023 at 15:59, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> * gnu/packages/haskell-xyz.scm (ghc-basement):
> [source]: Add patch.
> * gnu/packages/patches/ghc-basement-0.0.15-i686-fix.patch: New file.
> * gnu/local.mk (dist_patch_DATA):
> ---
> gnu/local.mk | 1 +
> gnu/packages/haskell-xyz.scm | 3 +-
> .../ghc-basement-0.0.15-i686-fix.patch | 113 ++++++++++++++++++
> 3 files changed, 116 insertions(+), 1 deletion(-)
> create mode 100644 gnu/packages/patches/ghc-basement-0.0.15-i686-fix.patch
Well, is this already part of some Haskell updates?
On Wed, 10 May 2023 at 19:34, Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> * gnu/packages/linux.scm (fakeroot): Update to 1.31.
> ---
> gnu/packages/linux.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I have not tried it yet but LGTM at first.
Cheers,
simon
next prev parent reply other threads:[~2023-05-16 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 13:59 [bug#62861] [PATCH v1] gnu: ghc-basement: fix build for i686 Denis 'GNUtoo' Carikli
2023-05-10 17:34 ` [bug#62861] [PATCH v1] gnu: fakeroot: Update to 1.31 Denis 'GNUtoo' Carikli
2023-05-16 14:13 ` zimoun [this message]
2023-05-17 23:14 ` [bug#62861] [PATCH v1] gnu: ghc-basement: fix build for i686 Denis 'GNUtoo' Carikli
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=86r0rg5pqp.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=62861@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.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).