libxcrypt-compat: upgrading to 4.4.20 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxcrypt-compat* to *4.4.20* has Succeeded.
Next steps:
- apply the patch: git am 0001-libxcrypt-compat-upgrade-4.4.19-4.4.20.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
packages/core2-32-poky-linux/libxcrypt-compat: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-dbg: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-dbg: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-dev: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-dev: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-doc: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-doc: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-locale: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-locale: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-src: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-src: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-staticdev: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat-staticdev: PV changed from "4.4.19" to "4.4.20" packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat: PKGV changed from 4.4.19 [default] to 4.4.20 [default] packages/core2-32-poky-linux/libxcrypt-compat/libxcrypt-compat: PV changed from "4.4.19" to "4.4.20"
From 66ffe84286bd38c167af29550cf76dd45e90d11f Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Sat, 15 May 2021 03:51:20 +0000
Subject: [PATCH] libxcrypt-compat: upgrade 4.4.19 -> 4.4.20
---
.../libxcrypt/files/fix_cflags_handling.patch | 17 +++++++++++++----
...pat_4.4.19.bb => libxcrypt-compat_4.4.20.bb} | 0
meta/recipes-core/libxcrypt/libxcrypt.inc | 2 +-
3 files changed, 14 insertions(+), 5 deletions(-)
rename meta/recipes-core/libxcrypt/{libxcrypt-compat_4.4.19.bb => libxcrypt-compat_4.4.20.bb} (100%)meta/recipes-core/libxcrypt/files/fix_cflags_handling.patch +13 -4
@@ -1,3 +1,8 @@ +From fd9a46695594c3cd836ecb7d959f03f605e69a2f Mon Sep 17 00:00:00 2001 +From: Richard Purdie <[email protected]> +Date: Fri, 30 Apr 2021 10:35:02 +0100 +Subject: [PATCH] libxcrypt: Update to 4.4.19 release and fix symbol version + If you pass CFLAGS with a leading space, " " gets passed to popen and convinces gcc to try and open a file called " ". This results in a confusing error message like:
@@ -9,8 +14,12 @@ Avoid this by stripping empty elements out of CFLAGS. Upstream-Status: Submitted [https://github.com/besser82/libxcrypt/pull/126] Signed-off-by: Richard Purdie <[email protected]> -Index: a/build-aux/compute-symver-floor -=================================================================== +--- + build-aux/compute-symver-floor | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/build-aux/compute-symver-floor b/build-aux/compute-symver-floor +index 4ec82e1..8117342 100644 --- a/build-aux/compute-symver-floor +++ b/build-aux/compute-symver-floor @@ -36,6 +36,8 @@ sub preprocessor_check {
@@ -20,5 +29,5 @@ Index: a/build-aux/compute-symver-floor + # Remove empty elements, particularly leading ones which cause issues with popen below + @CFLAGS = grep {$_} @CFLAGS; - # We call ensure_C_locale here, not from the main section, - # because this sub might not get called at all, in which + # Remove empty elements, particularly leading ones which + # cause issues with popen below.
meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.20.bb renamed from meta/recipes-core/libxcrypt/libxcrypt-compat_4.4.19.bb +0 -0
meta/recipes-core/libxcrypt/libxcrypt.inc +1 -1
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://LICENSING;md5=afed27a72ae2a8075978299eebaa1f5d \ inherit autotools pkgconfig SRC_URI = "git://github.com/besser82/libxcrypt.git;branch=${SRCBRANCH}" -SRCREV = "c79119414d7e30017d7b49566e7e4ea35112bdc8" +SRCREV = "e73ff0137de5152e69e8abb0bd260541804dfe5a" SRCBRANCH ?= "develop" SRC_URI += "file://fix_cflags_handling.patch"
Signature · 1 line
2.27.0