Message ID | 01010194c1abd159-f2c132e9-3e65-44ed-99e8-3aa0e56e5760-000000@us-west-2.amazonses.com |
---|---|
State | New |
Headers | show |
Series | [AUH] mmc-utils: upgrading to 67b9be6429d7b01e9e6057ead013e7049e34b273 SUCCEEDED | expand |
diff --git a/meta/recipes-devtools/mmc/mmc-utils_git.bb b/meta/recipes-devtools/mmc/mmc-utils_git.bb index 7bf21a1fe2..9f9cc967c0 100644 --- a/meta/recipes-devtools/mmc/mmc-utils_git.bb +++ b/meta/recipes-devtools/mmc/mmc-utils_git.bb @@ -5,7 +5,7 @@ LICENSE = "GPL-2.0-only" LIC_FILES_CHKSUM = "file://mmc.c;beginline=1;endline=20;md5=fae32792e20f4d27ade1c5a762d16b7d" SRCBRANCH ?= "master" -SRCREV = "523d8f3cfb219d800f45860892e742e3a355f1bb" +SRCREV = "67b9be6429d7b01e9e6057ead013e7049e34b273" PV = "0.1+git"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *mmc-utils* to *67b9be6429d7b01e9e6057ead013e7049e34b273* has Succeeded. Next steps: - apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 80683cd2036fbfbf6d89c6218b075d2917dd329b Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sat, 1 Feb 2025 07:54:21 +0000 Subject: [PATCH] mmc-utils: upgrade to latest revision --- meta/recipes-devtools/mmc/mmc-utils_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)