From: Takayasu Ito <ypa.takayasu.ito@gmail.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 04/11] migration-guides/release-notes-5.2.rst: add security fixes
Date: Mon, 21 Apr 2025 00:27:28 +0900 [thread overview]
Message-ID: <267b150e-0dd9-43de-8cdf-25324dd78e03@gmail.com> (raw)
In-Reply-To: <D97VVLZXMTW9.P853JF4BXI1F@bootlin.com>
Hi Antonin,
The decision is based on the upstream release notes and accompanying information.
As for gstreamer, three update commits have been made.
gstreamer1.0: upgrade 1.24.6 -> 1.24.9
https://git.yoctoproject.org/poky/commit/meta/recipes-multimedia/gstreamer?h=walnascar&id=0770b0 ecea8accb0edb9137595b2c7e0b94bb69b
gstreamer1.0: upgrade 1.24.9 -> 1.24.10
https://git.yoctoproject.org/poky/commit/?h=walnascar&id=d84 bc502cc610cbda9bf19e0320537287bf8a674
gstreamer1.0: upgrade 1.24.10 -> 1.24.12
https://git.yoctoproject.org/poky/commit/?h=walnascar&id= 925d5f1c725ceeb36c180b38a22dfdedd0dfc220
Release information for these updates is found at
https://gstreamer.freedesktop.org/news/
In it, it is stated that the security fixe is included in the 1.24.9 and 1.24.10 releases.
The details are confirmed at
https://gstreamer.freedesktop.org/security/
We can confirm that GStreamer-SA-2024-0004 through GStreamer-SA-2024-0030 were addressed in this release of walnascar.
On 2025/04/16 16:27, Antonin Godard wrote:
> Hi Takayasu,
>
> On Wed Apr 16, 2025 at 12:34 AM CEST, Takayasu Ito wrote:
>> Hi Antonin,
>>
>> I could not post the patch because I did not have the development environment with me due to machine trouble.
>
> Okay, that's fine.
>
> Could you please explain how you obtained these results?
> It's not straightforward for me to assert the validity of your changes. I would
> just need a way to reproduce the results you obtained. cve-check, maybe?
>
> Antonin
>
--
Takayasu Ito
Yocto Project Ambassador
ypa.takayasu.ito@gmail.com
next prev parent reply other threads:[~2025-04-20 15:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 13:07 [PATCH 00/11] Final release note updates for 5.2 Antonin Godard
2025-03-28 13:07 ` [PATCH 01/11] migration-guides/release-notes-5.2.rst: add the list of contributors Antonin Godard
2025-03-28 13:07 ` [PATCH 02/11] migration-guides/release-notes-5.2.rst: add recipe upgrades Antonin Godard
2025-03-28 13:07 ` [PATCH 03/11] migration-guides/release-notes-5.2.rst: add LICENSE recipe changes Antonin Godard
2025-03-28 13:07 ` [PATCH 04/11] migration-guides/release-notes-5.2.rst: add security fixes Antonin Godard
2025-04-12 16:38 ` [docs] " Takayasu Ito
2025-04-15 11:56 ` Antonin Godard
2025-04-15 22:34 ` Takayasu Ito
2025-04-16 7:27 ` Antonin Godard
2025-04-20 15:27 ` Takayasu Ito [this message]
2025-03-28 13:07 ` [PATCH 05/11] migration-guides/release-notes-5.2.rst: add an entry for addfragments Antonin Godard
2025-03-28 13:07 ` [PATCH 06/11] migration-guides/migration-5.2.rst: final update for 5.2 Antonin Godard
2025-03-28 13:07 ` [PATCH 07/11] ref-manual/system-requirements.rst: update list of supported distributions Antonin Godard
2025-03-28 13:07 ` [PATCH 08/11] poky.yaml.in: bump minimum required Python version to 3.9 Antonin Godard
2025-03-28 13:07 ` [PATCH 09/11] ref-manual/variables.rst: document the GRUB_MKIMAGE_OPTS variable Antonin Godard
2025-03-28 13:07 ` [PATCH 10/11] ref-manual/variables.rst: document the SPDX_PACKAGE_VERSION variable Antonin Godard
2025-03-28 13:07 ` [PATCH 11/11] migration-guides/{migration,release-note}-5.2: update for 5.2 release Antonin Godard
2025-03-28 16:03 ` [docs] " Quentin Schulz
2025-03-28 16:47 ` Richard Purdie
2025-03-31 8:32 ` Quentin Schulz
2025-04-03 15:39 ` Richard Purdie
2025-03-28 14:44 ` [docs] [PATCH 00/11] Final release note updates for 5.2 Yoann Congal
2025-03-28 14:49 ` Antonin Godard
2025-03-28 14:52 ` Yoann Congal
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=267b150e-0dd9-43de-8cdf-25324dd78e03@gmail.com \
--to=ypa.takayasu.ito@gmail.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox