From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/glibc: drop bogus IGNORE_CVES entries
Date: Fri, 07 Feb 2025 20:41:50 +0100 [thread overview]
Message-ID: <877c61ee4h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250203215155.1175999-2-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Mon, 3 Feb 2025 22:51:51 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> When glibc was bumped from 2.39 to 2.40 in commit
> 74cb378aff231c4f4605d7f479b9ae1a7a4e1fb6 ("package/{glibc, localdef}:
> bump to version 2.40"), the IGNORE_CVES entries should have been
> dropped, as they were applicable to the 2.39 branch. Drop them now.
> We did verify the pkg-stats output, and those CVEs don't show up as
> affecting glibc even after this change, as expected.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2024.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-07 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:51 [Buildroot] [PATCH 0/2] Bump glibc to 2.41 Thomas Petazzoni via buildroot
2025-02-03 21:51 ` [Buildroot] [PATCH 1/2] package/glibc: drop bogus IGNORE_CVES entries Thomas Petazzoni via buildroot
2025-02-04 11:29 ` Peter Korsgaard
2025-02-07 19:41 ` Peter Korsgaard [this message]
2025-02-03 21:51 ` [Buildroot] [PATCH 2/2] package/{glibc, localedef}: bump to version 2.41 Thomas Petazzoni via buildroot
2025-02-04 11:29 ` Peter Korsgaard
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=877c61ee4h.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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.
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.