| Message ID | 0101019509a15e77-4b93ebd5-fbac-437e-843a-8fbf5d257582-000000@us-west-2.amazonses.com |
|---|---|
| State | New |
| Headers | show |
| Series | [AUH] libxcrypt-compat,libxcrypt: upgrading to 4.4.38,4.4.38 FAILED | expand |
diff --git a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch index 879950bbe3..6e91efe1ff 100644 --- a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch +++ b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch @@ -1,4 +1,4 @@ -From 1e94a03541e35718dc1eaa8023e0ec3cf2de369b Mon Sep 17 00:00:00 2001 +From 9670e74ad2175356637af20be3a98b5714cbfe16 Mon Sep 17 00:00:00 2001 From: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Fri, 30 Apr 2021 10:35:02 +0100 Subject: [PATCH] libxcrypt: Update to 4.4.19 release and fix symbol version diff --git a/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.37.bb b/meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.38.bb similarity index 100% rename from meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.37.bb rename to meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.38.bb diff --git a/meta/recipes-core/libxcrypt/libxcrypt.inc b/meta/recipes-core/libxcrypt/libxcrypt.inc index 9ecb333fb9..247499565d 100644 --- a/meta/recipes-core/libxcrypt/libxcrypt.inc +++ b/meta/recipes-core/libxcrypt/libxcrypt.inc @@ -12,7 +12,7 @@ inherit autotools pkgconfig SRC_URI = "git://github.com/besser82/libxcrypt.git;branch=${SRCBRANCH};protocol=https \ file://fix_cflags_handling.patch \ " -SRCREV = "e5714d1f0a477f91ce3986fa63651c7710f0e183" +SRCREV = "55ea777e8d567e5e86ffac917c28815ac54cc341" SRCBRANCH ?= "master" PROVIDES = "virtual/crypt" diff --git a/meta/recipes-core/libxcrypt/libxcrypt_4.4.37.bb b/meta/recipes-core/libxcrypt/libxcrypt_4.4.38.bb similarity index 100% rename from meta/recipes-core/libxcrypt/libxcrypt_4.4.37.bb rename to meta/recipes-core/libxcrypt/libxcrypt_4.4.38.bb
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libxcrypt-compat,libxcrypt* to *4.4.38,4.4.38* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-libxcrypt-compat-libxcrypt-upgrade-4.4.37-4.4.38-4.4.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 8136917141a5022294714c72cb3354a12609edb9 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sat, 15 Feb 2025 05:05:51 +0000 Subject: [PATCH] libxcrypt-compat,libxcrypt: upgrade 4.4.37 -> 4.4.38,4.4.37 -> 4.4.38 --- meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch | 2 +- .../{libxcrypt-compat_4.4.37.bb => libxcrypt-compat_4.4.38.bb} | 0 meta/recipes-core/libxcrypt/libxcrypt.inc | 2 +- .../libxcrypt/{libxcrypt_4.4.37.bb => libxcrypt_4.4.38.bb} | 0 4 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-core/libxcrypt/{libxcrypt-compat_4.4.37.bb => libxcrypt-compat_4.4.38.bb} (100%) rename meta/recipes-core/libxcrypt/{libxcrypt_4.4.37.bb => libxcrypt_4.4.38.bb} (100%)