Message ID | 0101018f34e291a8-0b5124cc-100d-4121-9f70-259a3fc2eb6e-000000@us-west-2.amazonses.com |
---|---|
State | New |
Headers | show |
Series | [AUH] mmc-utils: upgrading to f757f413dea4a143ad7c3b48b8264176f0499a82 SUCCEEDED | expand |
diff --git a/meta/recipes-devtools/mmc/mmc-utils_git.bb b/meta/recipes-devtools/mmc/mmc-utils_git.bb index a7e4d369ff..7c6be93a9c 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 = "b5ca140312d279ad2f22068fd72a6230eea13436" +SRCREV = "f757f413dea4a143ad7c3b48b8264176f0499a82" 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 *f757f413dea4a143ad7c3b48b8264176f0499a82* 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 d718f7b5e7a24d486ab6b18806a3f50e62bd6ba4 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Wed, 1 May 2024 06:15:42 +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(-)