similarity index 91%
rename from meta/recipes-support/mpfr/mpfr_4.2.0.bb
rename to meta/recipes-support/mpfr/mpfr_4.2.1.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=1ebbd3e34237af26da5dc08a4e440464 \
DEPENDS = "gmp autoconf-archive-native"
SRC_URI = "https://www.mpfr.org/mpfr-${PV}/mpfr-${PV}.tar.xz"
-SRC_URI[sha256sum] = "06a378df13501248c1b2db5aa977a2c8126ae849a9d9b7be2546fb4a9c26d993"
+SRC_URI[sha256sum] = "277807353a6726978996945af13e52829e3abd7a9a5b7fb2793894e18f1fcbb2"
UPSTREAM_CHECK_URI = "http://www.mpfr.org/mpfr-current/"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mpfr* to *4.2.1* has Succeeded. Next steps: - apply the patch: git am 0001-mpfr-upgrade-4.2.0-4.2.1.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 f0bdf5298b4e8fcc3b51ab32ec01859729104fb3 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sat, 2 Sep 2023 09:21:26 +0000 Subject: [PATCH] mpfr: upgrade 4.2.0 -> 4.2.1 --- meta/recipes-support/mpfr/{mpfr_4.2.0.bb => mpfr_4.2.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/mpfr/{mpfr_4.2.0.bb => mpfr_4.2.1.bb} (91%)