Message ID | 0101018aec71b735-9f6b3204-65b1-46ca-ba08-caf2cb2392b1-000000@us-west-2.amazonses.com |
---|---|
State | New |
Headers | show |
Series | [AUH] mmc-utils: upgrading to 80271e9a6fd0db9cb3a85d024664da886e94315c SUCCEEDED | expand |
diff --git a/meta/recipes-devtools/mmc/mmc-utils_git.bb b/meta/recipes-devtools/mmc/mmc-utils_git.bb index 2d02927af7..913ce23907 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 = "613495ecaca97a19fa7f8f3ea23306472b36453c" +SRCREV = "80271e9a6fd0db9cb3a85d024664da886e94315c" PV = "0.1+git"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mmc-utils* to *80271e9a6fd0db9cb3a85d024664da886e94315c* 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 294d511c72666619673f3dcc17dfb2a2f6cd983d Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sun, 1 Oct 2023 08:44:33 +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(-)