From: Otavio Salvador <otavio@ossystems.com.br>
To: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: [PATCH 02/24] alsa-ucm-conf: upgrade 1.2.6.2 -> 1.2.6.3
Date: Mon, 3 Jan 2022 13:18:32 -0300 [thread overview]
Message-ID: <20220103161854.301148-2-otavio@ossystems.com.br> (raw)
In-Reply-To: <20220103161854.301148-1-otavio@ossystems.com.br>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
.../alsa/{alsa-ucm-conf_1.2.6.2.bb => alsa-ucm-conf_1.2.6.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/alsa/{alsa-ucm-conf_1.2.6.2.bb => alsa-ucm-conf_1.2.6.3.bb} (89%)
diff --git a/meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.2.bb b/meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.3.bb
similarity index 89%
rename from meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.2.bb
rename to meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.3.bb
index 10860e61a0..a493269063 100644
--- a/meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.2.bb
+++ b/meta/recipes-multimedia/alsa/alsa-ucm-conf_1.2.6.3.bb
@@ -8,7 +8,7 @@ LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=20d74d74db9741697903372ad001d3b4"
SRC_URI = "https://www.alsa-project.org/files/pub/lib/${BP}.tar.bz2"
-SRC_URI[sha256sum] = "8be24fb9fe789ee2778ae6f32e18e8043fe7f8bc735871e9d17c68a04566a822"
+SRC_URI[sha256sum] = "b8a03aa387a624a2f65edc201bf777421190b60529a92087646823afbd96c5cd"
# Something went wrong at upstream tarballing
inherit allarch
--
2.34.0
next prev parent reply other threads:[~2022-01-03 16:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:18 [PATCH 01/24] acpica: upgrade 20210930 -> 20211217 Otavio Salvador
2022-01-03 16:18 ` Otavio Salvador [this message]
2022-01-03 16:18 ` [PATCH 03/24] asciidoc: upgrade 10.0.2 -> 10.1.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 04/24] bind: upgrade 9.16.23 -> 9.16.24 Otavio Salvador
2022-01-03 16:18 ` [PATCH 05/24] e2fsprogs: upgrade 1.46.4 -> 1.46.5 Otavio Salvador
2022-01-03 17:42 ` [OE-core] " Richard Purdie
2022-01-03 18:26 ` Otavio Salvador
2022-01-04 10:44 ` Richard Purdie
2022-01-03 16:18 ` [PATCH 06/24] expat: upgrade 2.4.1 -> 2.4.2 Otavio Salvador
2022-01-03 16:18 ` [PATCH 07/24] gnupg: upgrade 2.3.3 -> 2.3.4 Otavio Salvador
2022-01-03 16:18 ` [PATCH 08/24] kea: upgrade 2.0.0 -> 2.0.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 09/24] libmicrohttpd: upgrade 0.9.73 -> 0.9.75 Otavio Salvador
2022-01-03 16:18 ` [PATCH 10/24] libxcrypt-compat: upgrade 4.4.26 -> 4.4.27 Otavio Salvador
2022-01-03 17:43 ` [OE-core] " Richard Purdie
2022-01-03 16:18 ` [PATCH 11/24] meson: upgrade 0.60.2 -> 0.60.3 Otavio Salvador
2022-01-03 19:09 ` [OE-core] " Alexander Kanavin
2022-01-03 22:19 ` Richard Purdie
2022-01-03 16:18 ` [PATCH 12/24] mmc-utils: upgrade to latest revision Otavio Salvador
2022-01-03 16:18 ` [PATCH 13/24] python3-attrs: upgrade 21.2.0 -> 21.4.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 14/24] python3-cython: upgrade 0.29.25 -> 0.29.26 Otavio Salvador
2022-01-03 16:18 ` [PATCH 15/24] python3-dtschema: upgrade 2021.10 -> 2021.12 Otavio Salvador
2022-01-03 16:18 ` [PATCH 16/24] python3-hypothesis: upgrade 6.31.4 -> 6.34.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 17/24] python3-importlib-metadata: upgrade 4.9.0 -> 4.10.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 18/24] python3-pygments: upgrade 2.10.0 -> 2.11.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 19/24] python3-ruamel-yaml: upgrade 0.17.17 -> 0.17.19 Otavio Salvador
2022-01-03 16:18 ` [PATCH 20/24] python3-setuptools: upgrade 59.5.0 -> 60.2.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 21/24] python3-tomli: upgrade 1.2.2 -> 2.0.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 22/24] python3-zipp: upgrade 3.6.0 -> 3.7.0 Otavio Salvador
2022-01-03 16:18 ` [PATCH 23/24] sqlite3: upgrade 3.37.0 -> 3.37.1 Otavio Salvador
2022-01-03 16:18 ` [PATCH 24/24] stress-ng: upgrade 0.13.08 -> 0.13.09 Otavio Salvador
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=20220103161854.301148-2-otavio@ossystems.com.br \
--to=otavio@ossystems.com.br \
--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