Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lei Maohui <leimaohui@fujitsu.com>
To: Alexander Kanavin <alex@linutronix.de>
Cc: Jose Quaresma <quaresma.jose@gmail.com>,
	Anuj Mittal <anuj.mittal@intel.com>,
	openembedded-core@lists.openembedded.org,
	Lei Maohui <leimaohui@fujitsu.com>
Subject: [OE-core] [PATCH v4 07/10] gstreamer1.0-plugins-good: upgrade 1.24.12 -> 1.26.0
Date: Wed,  2 Apr 2025 17:07:46 +0800	[thread overview]
Message-ID: <20250402090749.2119-8-leimaohui@fujitsu.com> (raw)
In-Reply-To: <20250402090749.2119-1-leimaohui@fujitsu.com>

Signed-off-by: Lei Maohui <leimaohui@fujitsu.com>
---
 ...gins-good_1.24.12.bb => gstreamer1.0-plugins-good_1.26.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-good_1.24.12.bb => gstreamer1.0-plugins-good_1.26.0.bb} (97%)

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.24.12.bb b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.26.0.bb
similarity index 97%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.24.12.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.26.0.bb
index 9cc2d462f6..a2c6426c34 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.24.12.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.26.0.bb
@@ -6,7 +6,7 @@ BUGTRACKER = "https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues
 
 SRC_URI = "https://gstreamer.freedesktop.org/src/gst-plugins-good/gst-plugins-good-${PV}.tar.xz"
 
-SRC_URI[sha256sum] = "d0e66e2f935d1575f6adbef7d0a2b3faba7360344383c51bf0233b39e0489a64"
+SRC_URI[sha256sum] = "9e18f139ef69ad0867c2dfbb8fe1d1736d76df11aac83f60e8d3adb1e2eaf03b"
 
 S = "${WORKDIR}/gst-plugins-good-${PV}"
 
-- 
2.43.0



  parent reply	other threads:[~2025-04-02  9:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  9:07 [OE-core] [PATCH v4 01/10] gst-devtools: upgrade 1.24.12 -> 1.26.0 Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH] python3-webcolors: upgrade 24.8.0 -> 24.11.1 Lei Maohui
2025-04-02  9:56   ` Richard Purdie
2025-04-02 10:03     ` Martin Jansa
2025-04-02 10:31       ` Maohui Lei (Fujitsu)
2025-04-02 11:09         ` Richard Purdie
2025-04-03  0:50           ` Khem Raj
2025-04-03  1:31           ` Maohui Lei (Fujitsu)
2025-04-02  9:07 ` [OE-core] [PATCH v4 02/10] gstreamer1.0: upgrade 1.24.12 -> 1.26.0 Lei Maohui
2025-04-02  9:48   ` Jose Quaresma
2025-04-02  9:57     ` Maohui Lei (Fujitsu)
2025-04-02  9:07 ` [OE-core] [PATCH v4 03/10] gstreamer1.0-libav: " Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH v4 04/10] gstreamer1.0-vaapi: " Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH v4 05/10] gtreamer1.0-rtsp-server: " Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH v4 06/10] gstreamer1.0-plugins-base: " Lei Maohui
2025-04-02  9:07 ` Lei Maohui [this message]
2025-04-02  9:07 ` [OE-core] [PATCH v4 08/10] gstreamer1.0-plugins-ugly: " Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH v4 09/10] gstreamer1.0-python: " Lei Maohui
2025-04-02  9:07 ` [OE-core] [PATCH v4 10/10] gstreamer1.0-plugins-bad: " Lei Maohui

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=20250402090749.2119-8-leimaohui@fujitsu.com \
    --to=leimaohui@fujitsu.com \
    --cc=alex@linutronix.de \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quaresma.jose@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox