From: Andreas Enge <andreas@enge.fr>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Latest news on core-updates
Date: Fri, 21 Apr 2023 10:47:44 +0200 [thread overview]
Message-ID: <ZEJNsOxA/vQao2Lu@jurong> (raw)
In-Reply-To: <861qkd63zx.fsf@gmail.com>
Am Fri, Apr 21, 2023 at 10:20:18AM +0200 schrieb Simon Tournier:
> Since Haskell is also broken on master for i686, I guess the option is
> to apply on some “feature™ branch” after the merge, right?
Yes indeed.
> Therefore, if many things are still missing, I suggest to apply #62967
> [2]. It removes the annoyance you spotted out in #62954 [3]. And as I
> explained in [4], it will be safe because ’valgrind’ appears only in the
> testsuite of ’lz4’ and ’valgrind’ is not even run there.
> Doing so, it will fix failures for powerpc64le and will increase the
> coverage.
CI just disappeared, so I cannot check. If r-minimal builds for powerpc64le
on master, then it is justifiable to fix the regression (leaving open the
possibility of an immediate revert if the patch introduces problems else-
where, which I do not expect). Otherwise I would postpone it until after
the merge.
Andreas
next prev parent reply other threads:[~2023-04-21 8:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57 ` Andreas Enge
2023-04-17 8:06 ` Andreas Enge
2023-04-17 8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17 8:33 ` Andreas Enge
2023-04-17 9:03 ` Andreas Enge
2023-04-17 9:56 ` Andreas Enge
2023-04-17 12:19 ` Simon Tournier
2023-04-17 12:38 ` Andreas Enge
2023-04-17 12:57 ` Simon Tournier
2023-04-17 14:12 ` Lars-Dominik Braun
2023-04-17 17:47 ` Simon Tournier
2023-04-17 18:07 ` Andreas Enge
2023-04-17 19:01 ` Lars-Dominik Braun
2023-04-18 17:16 ` Andreas Enge
2023-04-21 18:29 ` Lars-Dominik Braun
2023-04-17 12:57 ` Andreas Enge
2023-04-17 18:03 ` Maxim Cournoyer
2023-04-17 18:08 ` Andreas Enge
2023-04-18 5:04 ` John Kehayias
2023-04-18 17:38 ` Andreas Enge
2023-04-19 10:48 ` Latest news on core-updates Andreas Enge
2023-04-19 10:58 ` Christopher Baines
2023-04-19 12:41 ` Andreas Enge
2023-04-21 7:58 ` Andreas Enge
2023-04-21 13:01 ` Maxim Cournoyer
2023-04-20 13:56 ` Christopher Baines
2023-04-20 18:09 ` Andreas Enge
2023-04-21 8:20 ` Simon Tournier
2023-04-21 8:47 ` Andreas Enge [this message]
2023-04-21 11:31 ` Simon Tournier
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 17:04 ` reza.housseini
2023-04-23 7:17 ` Andreas Enge
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=ZEJNsOxA/vQao2Lu@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).