From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-security@gnu.org,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
Andreas Enge <andreas@enge.fr>,
70581@debbugs.gnu.org, McSinyx <cnx@loang.net>,
Janneke Nieuwenhuizen <janneke@gnu.org>
Subject: bug#70581: PHP, glibc, and CVE-2024-2961
Date: Thu, 19 Dec 2024 11:25:53 +0900 [thread overview]
Message-ID: <87r064mmry.fsf@gmail.com> (raw)
In-Reply-To: <87bjx9nw23.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Wed, 18 Dec 2024 11:07:48 +0100")
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> + (patches (map search-patch
>> + (fold (cut delete <...>)
>> + %glibc-patches
>> + '("glibc-2.39-git-updates.patch"))))))))
>
> Or: (delete "glibc-2.39-git-updates.patch" (search-patches %glibc-patches)).
It doesn't seem to work the way you'd intuitively expect, because
search-patches is syntax, and %glibc-patches is a list. So you at least
need the map and search-patch procedure:
--8<---------------cut here---------------start------------->8---
(delete "glibc-2.39-git-updates.patch" (map search-patch %glibc-patches)).
--8<---------------cut here---------------end--------------->8---
And then the delete has no effect because 'search-path' returns absolute
paths, so the patch to delete is now something like
'/home/maxim/src/guix/gnu/packages/patches/glibc-2.39-git-updates.patch',
for example.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-12-19 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 6:44 bug#70581: PHP, glibc, and CVE-2024-2961 McSinyx via Bug reports for GNU Guix
2024-04-26 7:20 ` Liliana Marie Prikler
2024-12-14 14:20 ` bug#70581: [PATCH] gnu: glibc: Graft with fix for CVE-2024-2961 Maxim Cournoyer
2024-12-18 7:31 ` bug#70581: PHP, glibc, and CVE-2024-2961 Maxim Cournoyer
2024-12-18 10:07 ` Ludovic Courtès
2024-12-19 2:25 ` Maxim Cournoyer [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
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=87r064mmry.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=70581@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=cnx@loang.net \
--cc=guix-security@gnu.org \
--cc=janneke@gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=ludo@gnu.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).