unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates?
Date: Tue, 16 Mar 2021 20:25:50 +0100	[thread overview]
Message-ID: <CAJ3okZ0-jkq9DAC6=At+Eky4_KZ6bOA6YUBuigpJaoLyP8UC7g@mail.gmail.com> (raw)
In-Reply-To: <YFEEg1JkPT48BK0n@jasmine.lan>

Hi,

On Tue, 16 Mar 2021 at 20:18, Leo Famulari <leo@famulari.name> wrote:
> On Tue, Mar 16, 2021 at 07:19:53PM +0100, zimoun wrote:
> > I guess that it will not build for i686.  Does it?
>
> I don't know. Either we will find out when building on CI, or people can
> test it manually now.

Please try out the patch from:

<https://lists.gnu.org/archive/html/guix-devel/2021-03/msg00295.html>

and if it works for you, please apply it.

> We might consider building the wip-next-release earlier than you had
> suggested. There is a large number of major updates on the branch, so it
> will unfortunately be more like core-updates than I had planned for.

Let's do that. :-)

> If that's not acceptable, we can narrow the scope of the existing
> grafts, by cherry-picking bug fix patches rather than updating the
> entire package.

You are right, it could be nice to have ASAP an idea about what is
acceptable and then how to narrow.


Cheers,
simon


  reply	other threads:[~2021-03-16 19:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  5:09 GNU Guix (pull?) on i686 broke after zstd grafting Léo Le Bouter
2021-03-06  5:30 ` Léo Le Bouter
2021-03-10 10:37 ` Ludovic Courtès
2021-03-10 10:43   ` Léo Le Bouter
2021-03-11  2:11   ` Léo Le Bouter
2021-03-11  9:37     ` zimoun
2021-03-11  9:40       ` Léo Le Bouter
2021-03-11  9:58         ` zimoun
2021-03-11 10:05           ` Léo Le Bouter
2021-03-16 16:34 ` Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates? zimoun
2021-03-16 17:06   ` Léo Le Bouter
2021-03-16 17:48     ` Leo Famulari
2021-03-16 18:03       ` Léo Le Bouter
2021-03-16 17:59     ` zimoun
2021-03-16 17:55   ` Leo Famulari
2021-03-16 18:08     ` Léo Le Bouter
2021-03-16 18:46       ` zimoun
2021-03-16 18:50         ` Léo Le Bouter
2021-03-16 19:04           ` zimoun
2021-03-16 18:19     ` zimoun
2021-03-16 18:26       ` Léo Le Bouter
2021-03-16 19:18       ` Leo Famulari
2021-03-16 19:25         ` zimoun [this message]
2021-03-16 19:29           ` Leo Famulari
2021-03-16 21:46             ` Security-czar needed? WAS: " Bengt Richter
2021-03-16 22:03               ` Leo Famulari
2021-03-17  6:24               ` Léo Le Bouter
2021-03-17 14:00                 ` zimoun
2021-03-16 21:47             ` Maxime Devos
2021-03-16 20:53     ` Tobias Geerinckx-Rice
2021-03-16 21:18       ` Vincent Legoll
2021-03-16 21:56         ` Leo Famulari
2021-03-17  6:40       ` Léo Le Bouter
2021-03-30  0:35   ` Léo Le Bouter

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='CAJ3okZ0-jkq9DAC6=At+Eky4_KZ6bOA6YUBuigpJaoLyP8UC7g@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).