From patchwork Sat Feb 1 13:20:40 2025 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 56391 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id A2BDEC0218A for ; Sat, 1 Feb 2025 13:20:49 +0000 (UTC) Received: from a27-192.smtp-out.us-west-2.amazonses.com (a27-192.smtp-out.us-west-2.amazonses.com [54.240.27.192]) by mx.groups.io with SMTP id smtpd.web11.42618.1738416041146712329 for ; Sat, 01 Feb 2025 05:20:41 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=rnkzp2s7ci3kogmesvov2nwn7wcc2dgx header.b=dL6DNfVQ; dkim=pass header.i=@amazonses.com header.s=7v7vs6w47njt4pimodk5mmttbegzsi6n header.b=UKCIqa2B; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.192, mailfrom: 01010194c1aba92e-cb823746-fc44-4c23-b74a-5ca8dcf95dc5-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=rnkzp2s7ci3kogmesvov2nwn7wcc2dgx; d=yoctoproject.org; t=1738416040; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=HSX/yEhWKs6KhdfcH5RbN0P6hJPBnBUxeFPFoIpngQw=; b=dL6DNfVQ8/I44RFWLyHeRHAtbtu4fFUMpmXvRP9sEPK33UExMdQY2GZHVC+aklJO XoqazRvqRD0dEFeVQ7vb0YeXbHYFB1plH2wAC1TX992SVwafx4D3BfK0YIVjmSQKmyW MgHnltgxxxpAruA5nGlkdbKiFgcZ14YZaSQ24RRU= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=7v7vs6w47njt4pimodk5mmttbegzsi6n; d=amazonses.com; t=1738416040; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=HSX/yEhWKs6KhdfcH5RbN0P6hJPBnBUxeFPFoIpngQw=; b=UKCIqa2B8gvjhC5Jwx4JbsF4s6Ul8VjhlhMrWSgWjGhFjIzPmyJNYhmbkFKbHRy/ p5g5V8OtnjXYAcp73uzG0kLy+od7Tw47FDH3Mu7wSYWEhoDmUitw6I7tTeZ0+eXAMK8 DQT9WQUKo3xcsExuEDJfoJit0Wg8Y5teOPsLK8Vs= MIME-Version: 1.0 From: auh@yoctoproject.org To: Khem Raj , Khem Raj Cc: openembedded-core@lists.openembedded.org Subject: [AUH] libxcrypt,libxcrypt-compat: upgrading to 4.4.38,4.4.38 FAILED Message-ID: <01010194c1aba92e-cb823746-fc44-4c23-b74a-5ca8dcf95dc5-000000@us-west-2.amazonses.com> Date: Sat, 1 Feb 2025 13:20:40 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2025.02.01-54.240.27.192 List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Sat, 01 Feb 2025 13:20:49 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/210506 Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libxcrypt,libxcrypt-compat* 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-libxcrypt-compat-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 5c7132495bb441653e1fe29011cc1eae342bc394 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Sat, 1 Feb 2025 05:07:46 +0000 Subject: [PATCH] libxcrypt,libxcrypt-compat: 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%) diff --git a/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch b/meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch index 879950bbe3..a6d4d8e96b 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 c80b411d0323b4a93aae9ef65ca17242b711df6c Mon Sep 17 00:00:00 2001 From: Richard Purdie 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