From: michael.opdenacker@bootlin.com
To: openembedded-core@lists.openembedded.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 1/3] alsa-lib: upgrade 1.2.8 -> 1.2.9
Date: Tue, 16 May 2023 20:30:06 +0200 [thread overview]
Message-ID: <20230516183009.1874105-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
.../alsa/{alsa-lib_1.2.8.bb => alsa-lib_1.2.9.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/alsa/{alsa-lib_1.2.8.bb => alsa-lib_1.2.9.bb} (94%)
diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.2.8.bb b/meta/recipes-multimedia/alsa/alsa-lib_1.2.9.bb
similarity index 94%
rename from meta/recipes-multimedia/alsa/alsa-lib_1.2.8.bb
rename to meta/recipes-multimedia/alsa/alsa-lib_1.2.9.bb
index bf968c920b..a8bf09904d 100644
--- a/meta/recipes-multimedia/alsa/alsa-lib_1.2.8.bb
+++ b/meta/recipes-multimedia/alsa/alsa-lib_1.2.9.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=a916467b91076e631dd8edb7424769c7 \
"
SRC_URI = "https://www.alsa-project.org/files/pub/lib/${BP}.tar.bz2"
-SRC_URI[sha256sum] = "1ab01b74e33425ca99c2e36c0844fd6888273193bd898240fe8f93accbcbf347"
+SRC_URI[sha256sum] = "dc9c643fdc4ccfd0572cc685858dd41e08afb583f30460b317e4188275f615b2"
inherit autotools pkgconfig
--
2.34.1
next reply other threads:[~2023-05-16 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 18:30 michael.opdenacker [this message]
2023-05-16 18:30 ` [PATCH] bitbake.conf: add "xz" to HOSTTOOLS michael.opdenacker
2023-05-16 18:30 ` [PATCH 2/3] alsa-ucm-conf: upgrade 1.2.8 -> 1.2.9 michael.opdenacker
2023-05-16 18:30 ` [PATCH 3/3] alsa-utils: " michael.opdenacker
[not found] ` <175FB334169DDB45.20583@lists.openembedded.org>
2023-05-16 18:35 ` [OE-core] [PATCH] bitbake.conf: add "xz" to HOSTTOOLS Michael Opdenacker
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=20230516183009.1874105-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox