unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Leo Famulari <leo@famulari.name>,
	Leo Prikler <leo.prikler@student.tugraz.at>
Cc: Maxime Devos <maximedevos@telenet.be>, 48304@debbugs.gnu.org
Subject: [bug#48304] [PATCH] gnu: expat: Update via graft.
Date: Sun, 23 May 2021 17:33:05 +0200	[thread overview]
Message-ID: <871r9xqxce.fsf@gnu.org> (raw)
In-Reply-To: <YJf+TnQ+DenU++Mx@jasmine.lan>

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

merge 48304 48612
thanks

Leo Famulari <leo@famulari.name> skriver:

> On Sun, May 09, 2021 at 04:37:39PM +0200, Leo Prikler wrote:
>> Indeed, the mail they dropped over at guix-devel made it seem as though
>> not being on 2.3.0 was a security risk already.  The ChangeLog does
>> mention some items worth fuzzing over.
>
> In general, all updates are security updates. But we shouldn't / can't
> update all core packages with grafts just because. Grafting is a kludge
> that doesn't always work as expected (and the problems are hidden), and
> it has a high I/O performance cost.
>
> So, let's wait for a security advisory.

I opened a similar discussion about the security fix in Expat 2.4.0
recently and am merging with this issue (which I had not seen):

  https://issues.guix.gnu.org/48612

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-05-23 15:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 23:27 [bug#48304] [PATCH] gnu: expat: Update via graft Leo Prikler
2021-05-09 14:05 ` Leo Famulari
2021-05-09 14:27   ` Maxime Devos
2021-05-09 14:32     ` Leo Famulari
2021-05-09 14:37     ` Leo Prikler
2021-05-09 15:22       ` Leo Famulari
2021-05-23 15:33         ` Marius Bakke [this message]
2021-06-03  3:17           ` bug#48304: " Leo Famulari

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=871r9xqxce.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=48304@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=leo@famulari.name \
    --cc=maximedevos@telenet.be \
    /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).