Message ID | 01010197c6c9e86b-994ca8fd-eb7e-450b-b0db-7df5e55cc3a4-000000@us-west-2.amazonses.com |
---|---|
State | New |
Headers | show |
Series | [AUH] mmc-utils: upgrading to d8a8358a7207bd81d0c38dca2cf27a48bf411341 SUCCEEDED | expand |
diff --git a/meta/recipes-devtools/mmc/mmc-utils_git.bb b/meta/recipes-devtools/mmc/mmc-utils_git.bb index f3944aebf0..79ce796092 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 = "c515ea2e1cebfbf9d81aa6a5c1bf67a79d2a7e58" +SRCREV = "d8a8358a7207bd81d0c38dca2cf27a48bf411341" 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 *d8a8358a7207bd81d0c38dca2cf27a48bf411341* 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 8e016bf9792d84560f1f52bebf116c66c35237f7 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Tue, 1 Jul 2025 08:32:14 +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(-)