all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Aaron Covrig via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 74199@debbugs.gnu.org
Subject: [bug#74199] [PATCH] gnu: zlib: Update to version 1.3.1
Date: Mon, 4 Nov 2024 08:00:23 -0500	[thread overview]
Message-ID: <CAK7qAcSKfY+3E1BJWRVoGuWudCcFDy8i0Lhb49Auk0buvp_O7A@mail.gmail.com> (raw)
In-Reply-To: <87cyjbwmp2.fsf@ngraves.fr>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Hello Nicolas,

Ok, should I resubmit against ‘core-updates’ or is this automatically done
via the marking for more info?

v/r,

Aaron Covrig

On Mon, Nov 4, 2024 at 01:13 Nicolas Graves <ngraves@ngraves.fr> wrote:

> On 2024-11-03 21:48, Aaron Covrig via Guix-patches via wrote:
>
> > * gnu/packages/compression.scm (zlib): Update to version 1.3.1
> > ---
> >
> > The zlib version 1.3.1 update addresses CVE-2023-45853,
> > see issue: https://github.com/madler/zlib/issues/868
>
> Hi Aaron,
>
> This is true, but rebuilding zlib will rebuild more than 30000 packages.
> You can see that with  guix refresh -l zlib | cut -d : -f 1
> That's why we can't simply merge a patch like that.  There are two
> solutions in this case, to my knowledge:
> - use a graft (see the manual, or packages with a "replacement" field)
> - wait for core-updates to pick up this commit
>
> In the meantime, marking this commit as moreinfo, we don't want to
> compute the revision for this.
>
> --
> Best regards,
> Nicolas Graves
>

[-- Attachment #2: Type: text/html, Size: 1688 bytes --]

      reply	other threads:[~2024-11-04 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  2:48 [bug#74199] [PATCH] gnu: zlib: Update to version 1.3.1 Aaron Covrig via Guix-patches via
2024-11-04  6:13 ` Nicolas Graves via Guix-patches via
2024-11-04 13:00   ` Aaron Covrig via Guix-patches via [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK7qAcSKfY+3E1BJWRVoGuWudCcFDy8i0Lhb49Auk0buvp_O7A@mail.gmail.com \
    --to=guix-patches@gnu.org \
    --cc=74199@debbugs.gnu.org \
    --cc=aaron.covrig.us@ieee.org \
    --cc=ngraves@ngraves.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.