From: Liliana Prikler via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Andreas Enge <andreas@enge.fr>,
Janneke Nieuwenhuizen <janneke@gnu.org>,
70581@debbugs.gnu.org, McSinyx <cnx@loang.net>,
guix-security@gnu.org
Subject: bug#70581: PHP, glibc, and CVE-2024-2961
Date: Fri, 20 Dec 2024 08:00:13 +0100 [thread overview]
Message-ID: <41e8919d208dfdfc0a50b456286c0de2d0b1ad20.camel@tugraz.at> (raw)
In-Reply-To: <87r064mmry.fsf@gmail.com>
Am Donnerstag, dem 19.12.2024 um 11:25 +0900 schrieb Maxim Cournoyer:
> 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.
What about
(map search-patch
(delete "glibc-2.39-git-updates.patch" %glibc-patches))
?
prev parent reply other threads:[~2024-12-22 19:21 UTC|newest]
Thread overview: 7+ 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
2024-12-20 7:00 ` Liliana Prikler via Bug reports for GNU Guix [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=41e8919d208dfdfc0a50b456286c0de2d0b1ad20.camel@tugraz.at \
--to=bug-guix@gnu.org \
--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@tugraz.at \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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 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.