date:20210315

2021-03-15 Thread Scott Branden via lists.openembedded.org

The meson determinism issue is the same frozenset issue we encountered with
python itself. Remove the problematic pyc file until upstream work out the
best way to address the issue (as with core python).

Signed-off-by: Richard Purdie 
---
 meta/lib/oeqa/selftest/cases/reproducible.py |  1 -
 meta/recipes-devtools/meson/meson.inc| 14 ++
 2 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index d301c8dd888..1945a12c319 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -33,7 +33,6 @@ exclude_packages = [
'go-runtime',
'go_',
'go-',
-   'meson',
'ovmf-shell-efi',
'ruby-ri-docs'
]
diff --git a/meta/recipes-devtools/meson/meson.inc 
b/meta/recipes-devtools/meson/meson.inc
index 8454d18c284..fc3ca85faeb 100644
--- a/meta/recipes-devtools/meson/meson.inc
+++ b/meta/recipes-devtools/meson/meson.inc
@@ -23,6 +23,10 @@ SRC_URI_append_class-native = " \
 file://0002-Support-building-allarch-recipes-again.patch \
 "
 
+# remove at next version upgrade or when output changes
+PR = "r1"
+HASHEQUIV_HASH_VERSION .= ".1"
+
 UPSTREAM_CHECK_URI = "https://github.com/mesonbuild/meson/releases;
 UPSTREAM_CHECK_REGEX = "meson-(?P\d+(\.\d+)+)\.tar"
 
@@ -31,3 +35,13 @@ inherit setuptools3
 RDEPENDS_${PN} = "ninja python3-modules python3-pkg-resources"
 
 FILES_${PN} += "${datadir}/polkit-1"
+
+do_install_append () {
+   # As per the same issue in the python recipe itself:
+   # Unfortunately the following pyc files are non-deterministc due to 
'frozenset'
+   # being written without strict ordering, even with PYTHONHASHSEED = 0
+   # Upstream is discussing ways to solve the issue properly, until then 
let's
+   # just not install the problematic files.
+   # More info: http://benno.id.au/blog/2013/01/15/python-determinism
+   rm 
${D}${libdir}/python*/site-packages/mesonbuild/dependencies/__pycache__/mpi.cpython*
+}
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149545): 
https://lists.openembedded.org/g/openembedded-core/message/149545
Mute This Topic: https://lists.openembedded.org/mt/81364976/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] unwanted linux kernel image added to /boot directory

2021-03-15 Thread Khem Raj

On Mon, Mar 15, 2021 at 4:40 PM Scott Branden via
lists.openembedded.org
 wrote:
>
> Hello,
>
> There seems to be a problem when a kernel module is added to an initramfs 
> image.
>
> As soon as I add a recipe which installs an external kernel module into an 
> initramfs image it automatically installs the linux kernel image in a /boot 
> directory.
>
> This is really bad as it increases the size of the initramfs image.
>
> /boot/Image should not be installed in the image when an external kernel 
> module is added to an image.
>
> Can someone suggest a fix to this issue?
>

try

IMAGE_INSTALL_remove = "kernel-image-${KERNEL_IMAGETYPE}"

or set

KERNEL_IMAGE = ""

> Thanks,
>  Scott
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149544): 
https://lists.openembedded.org/g/openembedded-core/message/149544
Mute This Topic: https://lists.openembedded.org/mt/81364677/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] unwanted linux kernel image added to /boot directory

Hello,

There seems to be a problem when a kernel module is added to an initramfs image.

As soon as I add a recipe which installs an external kernel module into an 
initramfs image it automatically installs the linux kernel image in a /boot 
directory.

This is really bad as it increases the size of the initramfs image.

/boot/Image should not be installed in the image when an external kernel module 
is added to an image.

Can someone suggest a fix to this issue?

Thanks,
 Scott


smime.p7s
Description: S/MIME Cryptographic Signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149543): 
https://lists.openembedded.org/g/openembedded-core/message/149543
Mute This Topic: https://lists.openembedded.org/mt/81364677/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 3/4] u-boot: Use a different Key for SPL signing

2021-03-15 Thread Dan Zhang

Hi Klaus,

Can we make the patch not only support sign u-boot fitimage with
different key, but also allow sign later?
Similar to kernel-fitimage.bbclass::fitimage_assemble(), step 1~6
create a "sign-able"  fit-image and step 7 do the sign.

Can we add a new control variable i.e. DO_UBOOT_SIGN which control
whether we sign the image during build time.

It is desired to be able to "just sign" the "sign-able" image with
"any key" later, instead of need rebuilding the whole image.
i.e. Create a signing service, which can accessing to the official
production key, to sign the image. We don't want to have this signing
service setup complex building environment and rebuild the image.

BRs
Dan Zhang

> From: Klaus Heinrich Kiwi 
> To: openembedded-core@lists.openembedded.org
> Cc: j...@jms.id.au, and...@aj.id.au, open...@lists.ozlabs.org, Klaus Heinrich 
> Kiwi 
> Bcc:
> Date: Mon, 15 Mar 2021 13:58:05 -0300
> Subject: [PATCH 3/4] u-boot: Use a different Key for SPL signing
> Duplicate the variables governing u-boot signing so that we can have a
> different set of keys/parameters signing the SPL.
>
> Signed-off-by: Klaus Heinrich Kiwi 
> ---
>  meta/classes/uboot-config.bbclass |  2 ++
>  meta/classes/uboot-sign.bbclass   | 55 ---
>  2 files changed, 46 insertions(+), 11 deletions(-)
>
> diff --git a/meta/classes/uboot-config.bbclass 
> b/meta/classes/uboot-config.bbclass
> index 31487c1418..3bba02828b 100644
> --- a/meta/classes/uboot-config.bbclass
> +++ b/meta/classes/uboot-config.bbclass
> @@ -61,6 +61,7 @@ UBOOT_EXTLINUX_SYMLINK ?= 
> "${UBOOT_EXTLINUX_CONF_NAME}-${MACHINE}-${PR}"
>
>  # Options for the device tree compiler passed to mkimage '-D' feature:
>  UBOOT_MKIMAGE_DTCOPTS ??= ""
> +SPL_MKIMAGE_DTCOPTS ??= ""
>
>  # mkimage command
>  UBOOT_MKIMAGE ?= "uboot-mkimage"
> @@ -68,6 +69,7 @@ UBOOT_MKIMAGE_SIGN ?= "${UBOOT_MKIMAGE}"
>
>  # Arguments passed to mkimage for signing
>  UBOOT_MKIMAGE_SIGN_ARGS ?= ""
> +SPL_MKIMAGE_SIGN_ARGS ?= ""
>
>  python () {
>  ubootmachine = d.getVar("UBOOT_MACHINE")
> diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
> index 86380f2234..2ec93e0b8e 100644
> --- a/meta/classes/uboot-sign.bbclass
> +++ b/meta/classes/uboot-sign.bbclass
> @@ -59,27 +59,34 @@ SPL_NODTB_IMAGE ?= 
> "${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${
>  SPL_NODTB_BINARY ?= "u-boot-spl-nodtb.bin"
>  SPL_NODTB_SYMLINK ?= 
> "${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${MACHINE}${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[1]}"
>
DO_UBOOT_SIGN ?= "1"
> -# fitImage Hash Algo
> +# Kernel / U-Boot fitImage Hash Algo
>  FIT_HASH_ALG ?= "sha256"
> +UBOOT_FIT_HASH_ALG ?= "sha256"
>
> -# fitImage Signature Algo
> +# Kernel / U-Boot fitImage Signature Algo
>  FIT_SIGN_ALG ?= "rsa2048"
> +UBOOT_FIT_SIGN_ALG ?= "rsa2048"
>
> -# Generate keys for signing fitImage
> +# Generate keys for signing Kernel / U-Boot fitImage
>  FIT_GENERATE_KEYS ?= "0"
> +UBOOT_FIT_GENERATE_KEYS ?= "0"
>
> -# Size of private key in number of bits
> +# Size of private keys in number of bits
>  FIT_SIGN_NUMBITS ?= "2048"
> +UBOOT_FIT_SIGN_NUMBITS ?= "2048"
>
>  # args to openssl genrsa (Default is just the public exponent)
>  FIT_KEY_GENRSA_ARGS ?= "-F4"
> +UBOOT_FIT_KEY_GENRSA_ARGS ?= "-F4"
>
>  # args to openssl req (Default is -batch for non interactive mode and
>  # -new for new certificate)
>  FIT_KEY_REQ_ARGS ?= "-batch -new"
> +UBOOT_FIT_KEY_REQ_ARGS ?= "-batch -new"
>
>  # Standard format for public key certificate
>  FIT_KEY_SIGN_PKCS ?= "-x509"
> +UBOOT_FIT_KEY_SIGN_PKCS ?= "-x509"
>
>  # Functions on this bbclass can apply to either U-boot or Kernel,
>  # depending on the scenario
> @@ -280,6 +287,32 @@ do_generate_rsa_keys() {
> -out 
> "${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".crt
> fi
> fi
> +
> +   if [ "${SPL_SIGN_ENABLE}" = "0" ] && [ "${UBOOT_FIT_GENERATE_KEYS}" = 
> "1" ]; then
> +   bbwarn "UBOOT_FIT_GENERATE_KEYS is set to 1 eventhough 
> SPL_SIGN_ENABLE is set to 0. The keys will not be generated as they won't be 
> used."
> +   fi
> +
> +   if [ "${SPL_SIGN_ENABLE}" = "1" ] && [ "${UBOOT_FIT_GENERATE_KEYS}" = 
> "1" ]; then
> +
> +   # Generate keys only if they don't already exist
> +   if [ ! -f "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".key ] || \
> +   [ ! -f "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".crt 
> ]; then
> +
> +   # make directory if it does not already exist
> +   mkdir -p "${SPL_SIGN_KEYDIR}"
> +
> +   echo "Generating RSA private key for signing U-Boot 
> fitImage"
> +   openssl genrsa ${UBOOT_FIT_KEY_GENRSA_ARGS} -out \
> +   "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".key \
> +   "${UBOOT_FIT_SIGN_NUMBITS}"
> +
> +   echo "Generating

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

On Mon, 2021-03-15 at 13:57 +, Richard Purdie via lists.openembedded.org 
wrote:
> On Mon, 2021-03-15 at 14:55 +0100, Martin Jansa wrote:
> > On Mon, Mar 15, 2021 at 12:21:37PM +, Richard Purdie wrote:
> > > On Mon, 2021-03-15 at 11:50 +, Luca Boccassi wrote:
> > > > On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> > > > > On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > > > > > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > > > > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > > > > > From: Luca Boccassi 
> > > > > > > > 
> > > > > > > > Recently util-linux gained an (optional) build dependency on 
> > > > > > > > libcryptsetup.
> > > > > > > > But libcryptsetup build-depends on util-linux for blkid 
> > > > > > > > (optional, can be disabled)
> > > > > > > > and uuid (mandatory).
> > > > > > > > Split out util-linux-uuid in a different recipe to break the 
> > > > > > > > cycle.
> > > > > > > > 
> > > > > > > > https://github.com/karelzak/util-linux/pull/898
> > > > > > > > 
> > > > > > > > Signed-off-by: Luca Boccassi 
> > > > > > > 
> > > > > > > Unfortunately I noticed we had a performance regression in 
> > > > > > > buildtimes in 
> > > > > > > recent changes. The closest I have this narrowed down to so far:
> > > > > > > 
> > > > > > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > > > > > 
> > > > > > > suggests it may be this change. I have more tests queued to 
> > > > > > > confirm
> > > > > > > that definitively, if so we'll have to figure out why as this 
> > > > > > > shouldn't
> > > > > > > really happen, its an 8% regression :(.
> > > > > > 
> > > > > > Very strange that a single recipe could do that - is there something
> > > > > > wrong in the new .bb that I missed and could cause this?
> > > > > 
> > > > > I'm wondering if it is because we're building util-linux twice now and
> > > > > there is some key choke point in the dependency chain. I have no 
> > > > > evidence
> > > > > for that yet, it is just speculation though.
> > > > 
> > > > With the autoconf options I've set, on my laptop it takes 32s to do
> > > > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > > > 
> > > > Only 3 libraries are built with this combination: libcommon.a,
> > > > libtcolors.a, and libuuid.a/so. No executables or anything else is
> > > > built. It doesn't look like libtcolors is actually needed, I'll see if
> > > > I can prepare a patch to skip it, but I don't think it will buy more
> > > > than 1s, it's just two object files.
> > > > 
> > > > The good news is that meson support is about to land upstream, which
> > > > should be significantly faster than autoconf + make:
> > > > 
> > > > https://github.com/karelzak/util-linux/commits/topic/meson
> > > 
> > > Meson definitely improves the speed! I was wondering if it was from
> > > configure for example.
> > > 
> > > I now have more performance test results in (takes time to interleave 
> > > them with testing of master):
> > > 
> > > https://autobuilder.yocto.io/pub/non-release/20210315-1/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210315005048_6bb1621815.html
> > > 
> > > and I think this means it isn't from the util-linux change but one of 
> > > another three. I'm not entirely convinced those changes could do this
> > > but it is what the data says. 
> > > 
> > > I've queued more bisection to narrow it down from there...
> > 
> > BTW: this split also needs manual cleanup in the TMPDIR, right?
> 
> It shouldn't. The system should spot that util-linux has changed and uninstall
> it from the sysroots as it goes. There is something not working right there :(

I was wrong about that, the system doesn't have code for this, it has code for
the sysroots but not for other sstate tasks.

I think this is an oversight and we need to simplify things and make this 
cleanup
happen pre-build, much like the "unreachable" tasks cleanup happens today. If we
do make this happen, we probably need to add parallelism as the number of stale
sstate tasks being cleaned could be substantial.

Cheers,

Richard








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149541): 
https://lists.openembedded.org/g/openembedded-core/message/149541
Mute This Topic: https://lists.openembedded.org/mt/81254724/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: Fix CVE-2021-27645

2021-03-15 Thread Denys Dmytriyenko

https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable.2FLTS_Patch_Acceptance_Policies

Stable/LTS Patch Acceptance Policies

Potentially Acceptable:
* Bug fix only version upgrades for upstreams with a good stable process

Unacceptable:
* General version upgrades


So, unless there's a bugfix-only minor release of glibc, e.g. 2.31.1, 
upgrading to 2.32 or 2.33 in stable branches is highly unlikely, as both 
2.32 and 2.33 have long lists of major changes:

https://sourceware.org/pipermail/libc-announce/2020/29.html
https://sourceware.org/pipermail/libc-announce/2021/30.html

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964


On Sun, Mar 14, 2021 at 12:20:00AM +0100, Anatol Belski wrote:
> Hi,
> 
> looking at the state of the upstream glibc 2.31, pulling the latest
> upstream might be more suitable than cherry-picking patches. Depending
> on the recipe maintainers opinion, it might be a good time time to do
> so as some other CVE issues are fixed there, too.
> 
> Thanks
> 
> Anatol
> 
> On Fri, 2021-03-12 at 23:15 +, Jamaluddin, Khairul Rohaizzat wrote:
> > Just did some checking for versions glibc-2.31 and glibc-2.32 (used
> > in dunfell and gatesgarth respectively), both of these versions
> > cannot use this patch as these versions doesn't have the file
> > involved, netgroupcache.c
> > 
> > 
> > Thank you & Kind regards,
> > Khairul
> > 
> > -Original Message-
> > From: Jamaluddin, Khairul Rohaizzat 
> > Sent: Saturday, March 13, 2021 3:34 AM
> > To: Khem Raj 
> > Cc: Patches and discussions about the oe-core layer
> > 
> > Subject: RE: [OE-core] [PATCH] glibc: Fix CVE-2021-27645
> > 
> > Yes, seems to be in the list as well..
> > The version for both branch is within the versions mentioned in the
> > CVE too.
> > 
> > 
> > Thank you & Kind regards,
> > Khairul
> > 
> > -Original Message-
> > From:
> > openembedded-core@lists.openembedded.org 
> >  > > On Behalf Of Khem Raj
> > Sent: Friday, March 12, 2021 7:56 AM
> > To: Jamaluddin, Khairul Rohaizzat
> > 
> > Cc: Patches and discussions about the oe-core layer
> > 
> > Subject: Re: [OE-core] [PATCH] glibc: Fix CVE-2021-27645
> > 
> > On Thu, Mar 11, 2021 at 7:21 AM Jamaluddin, Khairul Rohaizzat
> >  wrote:
> > > 
> > > From: Khairul Rohaizzat Jamaluddin
> > > 
> > > 
> > > CVE:
> > > CVE-2021-27645
> > > 
> > 
> > lgtm. Do we need it for dunfell and gatesgarth as well ?
> > 
> > > Signed-off-by: Khairul Rohaizzat Jamaluddin 
> > > 
> > > ---
> > >  .../glibc/glibc/CVE-2021-27645.patch  | 51
> > > +++
> > >  meta/recipes-core/glibc/glibc_2.33.bb |  1 +
> > >  2 files changed, 52 insertions(+)
> > >  create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-
> > > 27645.patch
> > > 
> > > diff --git a/meta/recipes-core/glibc/glibc/CVE-2021-27645.patch
> > > b/meta/recipes-core/glibc/glibc/CVE-2021-27645.patch
> > > new file mode 100644
> > > index 00..26c5c0d2a9
> > > --- /dev/null
> > > +++ b/meta/recipes-core/glibc/glibc/CVE-2021-27645.patch
> > > @@ -0,0 +1,51 @@
> > > +From dca565886b5e8bd7966e15f0ca42ee5cff686673 Mon Sep 17 00:00:00
> > > +2001
> > > +From: DJ Delorie 
> > > +Date: Thu, 25 Feb 2021 16:08:21 -0500
> > > +Subject: [PATCH] nscd: Fix double free in netgroupcache [BZ
> > > #27462]
> > > +
> > > +In commit 745664bd798ec8fd50438605948eea594179fba1 a use-after-
> > > free 
> > > +was fixed, but this led to an occasional double-free.  This patch 
> > > +tracks the "live" allocation better.
> > > +
> > > +Tested manually by a third party.
> > > +
> > > +Related: RHBZ 1927877
> > > +
> > > +Reviewed-by: Siddhesh Poyarekar 
> > > +Reviewed-by: Carlos O'Donell 
> > > +
> > > +Upstream-Status: Backport
> > > +[https://sourceware.org/git/?p=glibc.git;a=commit;h=dca565886b5e8bd79
> > > +66e15f0ca42ee5cff686673]
> > > +
> > > +CVE: CVE-2021-27645
> > > +
> > > +Reviewed-by: Carlos O'Donell 
> > > +Signed-off-by: Khairul Rohaizzat Jamaluddin 
> > > +
> > > +---
> > > + nscd/netgroupcache.c | 4 ++--
> > > + 1 file changed, 2 insertions(+), 2 deletions(-)
> > > +
> > > +diff --git a/nscd/netgroupcache.c b/nscd/netgroupcache.c index 
> > > +dba6ceec1b..ad2daddafd 100644
> > > +--- a/nscd/netgroupcache.c
> > >  b/nscd/netgroupcache.c
> > > +@@ -248,7 +248,7 @@ addgetnetgrentX (struct database_dyn *db, int
> > > fd, request_header *req,
> > > +    : NULL);
> > > +   ndomain = (ndomain ? newbuf +
> > > ndomaindiff
> > > +  : NULL);
> > > +-  buffer = newbuf;
> > > ++  *tofreep = buffer = newbuf;
> > > + }
> > > +
> > > +   nhost = memcpy (buffer + bufused,
> > > @@
> > > +-319,7 +319,7 @@ addgetnetgrentX (struct database_dyn *db,

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2021-03-15 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 364
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149539): 
https://lists.openembedded.org/g/openembedded-core/message/149539
Mute This Topic: https://lists.openembedded.org/mt/81358455/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] libedit: upgrade 20191231-3.1 -> 20210216-3.1

2021-03-15 Thread Khem Raj

---
 .../{libedit_20191231-3.1.bb => libedit_20210216-3.1.bb}   | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-devtools/libedit/{libedit_20191231-3.1.bb => 
libedit_20210216-3.1.bb} (82%)

diff --git a/meta/recipes-devtools/libedit/libedit_20191231-3.1.bb 
b/meta/recipes-devtools/libedit/libedit_20210216-3.1.bb
similarity index 82%
rename from meta/recipes-devtools/libedit/libedit_20191231-3.1.bb
rename to meta/recipes-devtools/libedit/libedit_20210216-3.1.bb
index 8d2d57a930..97aceaf716 100644
--- a/meta/recipes-devtools/libedit/libedit_20191231-3.1.bb
+++ b/meta/recipes-devtools/libedit/libedit_20210216-3.1.bb
@@ -13,8 +13,7 @@ inherit autotools
 SRC_URI = "http://www.thrysoee.dk/editline/${BP}.tar.gz \
file://stdc-predef.patch \
   "
-SRC_URI[md5sum] = "2e22a51131de94ff2df24901f7cfe416"
-SRC_URI[sha256sum] = 
"dbb82cb7e116a5f8025d35ef5b4f7d4a3cdd0a3909a146a39112095a2d229071"
+SRC_URI[sha256sum] = 
"2283f741d2aab935c8c52c04b57bf952d02c2c02e651172f8ac811f77b1fc77a"
 
 BBCLASSEXTEND = "native nativesdk"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149538): 
https://lists.openembedded.org/g/openembedded-core/message/149538
Mute This Topic: https://lists.openembedded.org/mt/81357037/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 4/4] oe-selftest: Add U-Boot fitImage signing testcases

Derived from the similar kernel fitImage sign testcase, the U-Boot
fitImage testcases will test both the standalone (only SPL_SIGN_ENABLE
set) as well as cascaded (both UBOOT_SIGN_ENABLE as well as
SPL_SIGN_ENABLE) scenarios.

Signed-off-by: Klaus Heinrich Kiwi 
---
 meta/lib/oeqa/selftest/cases/fitimage.py | 293 +++
 1 file changed, 293 insertions(+)

diff --git a/meta/lib/oeqa/selftest/cases/fitimage.py 
b/meta/lib/oeqa/selftest/cases/fitimage.py
index 02692de822..ece1ad460b 100644
--- a/meta/lib/oeqa/selftest/cases/fitimage.py
+++ b/meta/lib/oeqa/selftest/cases/fitimage.py
@@ -231,6 +231,299 @@ UBOOT_MKIMAGE_SIGN_ARGS = "-c 'a smart comment'"
 result = runCmd('grep "### uboot-mkimage signing wrapper message" 
%s/log.do_assemble_fitimage' % tempdir, ignore_status=True)
 self.assertEqual(result.status, 0, 'UBOOT_MKIMAGE_SIGN did not work')
 
+def test_sign_standalone_uboot_fit_image(self):
+"""
+Summary: Check if U-Boot FIT image and Image Tree Source (its) are
+ created and signed correctly for the scenario where only
+ the U-Boot proper fitImage is being signed.
+Expected:1) U-Boot its and FIT image are built successfully
+ 2) Scanning the its file indicates signing is enabled
+as requested by SPL_SIGN_ENABLE (using keys generated
+via UBOOT_FIT_GENERATE_KEYS)
+ 3) Dumping the FIT image indicates signature values
+are present
+ 4) Examination of the do_uboot_assemble_fitimage
+ runfile/logfile indicate that UBOOT_MKIMAGE, 
UBOOT_MKIMAGE_SIGN
+ and SPL_MKIMAGE_SIGN_ARGS are working as expected.
+Product: oe-core
+Author:  Klaus Heinrich Kiwi  based upon
+ work by Paul Eggleton  and
+ Usama Arif 
+"""
+config = """
+# There's no U-boot deconfig with CONFIG_FIT_SIGNATURE yet, so we need at
+# least CONFIG_SPL_LOAD_FIT and CONFIG_SPL_OF_CONTROL set
+MACHINE = "beaglebone-yocto"
+UBOOT_MACHINE = "am57xx_evm_defconfig"
+USER_CLASSES = " test-mkimage-wrapper "
+SPL_SIGN_ENABLE = "1"
+SPL_SIGN_KEYNAME = "spl-oe-selftest"
+SPL_SIGN_KEYDIR = "${TOPDIR}/signing-keys"
+UBOOT_DTB_BINARY = "u-boot.dtb"
+UBOOT_ENTRYPOINT  = "0x8000"
+UBOOT_LOADADDRESS = "0x8000"
+UBOOT_DTB_LOADADDRESS = "0x8200"
+UBOOT_ARCH = "arm"
+SPL_MKIMAGE_DTCOPTS = "-I dts -O dtb -p 2000"
+SPL_MKIMAGE_SIGN_ARGS = "-c 'a smart U-Boot comment'"
+UBOOT_EXTLINUX = "0"
+UBOOT_FIT_GENERATE_KEYS = "1"
+UBOOT_FIT_HASH_ALG = "sha256"
+"""
+self.write_config(config)
+
+# this scenario exercises standalone u-boot fitImage sign
+bitbake("u-boot")
+
+image_type = "core-image-minimal"
+deploy_dir_image = get_bb_var('DEPLOY_DIR_IMAGE')
+machine = get_bb_var('MACHINE')
+fitimage_its_path = os.path.join(deploy_dir_image,
+"u-boot-its-%s" % (machine,))
+fitimage_path = os.path.join(deploy_dir_image,
+"u-boot-fitImage-%s" % (machine,))
+
+self.assertTrue(os.path.exists(fitimage_its_path),
+"%s image tree source doesn't exist" % (fitimage_its_path))
+self.assertTrue(os.path.exists(fitimage_path),
+"%s FIT image doesn't exist" % (fitimage_path))
+
+req_itspaths = [
+['/', 'images', 'uboot'],
+['/', 'images', 'uboot', 'signature'],
+['/', 'images', 'fdt'],
+['/', 'images', 'fdt', 'signature'],
+]
+
+itspath = []
+itspaths = []
+linect = 0
+sigs = {}
+with open(fitimage_its_path) as its_file:
+linect += 1
+for line in its_file:
+line = line.strip()
+if line.endswith('};'):
+itspath.pop()
+elif line.endswith('{'):
+itspath.append(line[:-1].strip())
+itspaths.append(itspath[:])
+elif itspath and itspath[-1] == 'signature':
+itsdotpath = '.'.join(itspath)
+if not itsdotpath in sigs:
+sigs[itsdotpath] = {}
+if not '=' in line or not line.endswith(';'):
+self.fail('Unexpected formatting in %s sigs section 
line %d:%s' % (fitimage_its_path, linect, line))
+key, value = line.split('=', 1)
+sigs[itsdotpath][key.rstrip()] = value.lstrip().rstrip(';')
+
+for reqpath in req_itspaths:
+if not reqpath in itspaths:
+self.fail('Missing section in its file: %s' % reqpath)
+
+reqsigvalues_image = {
+'algo': '"sha256,rsa2048"',
+'key-name-hint': '"spl-oe-selftest"',
+}
+
+for itspath, values in sigs.items():
+

[OE-core] [PATCH 2/4] u-boot: Add infrastructure to SPL verified boot

Add the necessary infrastructure to create a U-boot proper fitimage,
sign it (using the same keys as the kernel-fitimage), and put the public
key in the SPL binary so that verified SPL boot can be accomplished.

Signed-off-by: Klaus Heinrich Kiwi 
---
 meta/classes/kernel-fitimage.bbclass |  11 +-
 meta/classes/uboot-sign.bbclass  | 335 +--
 2 files changed, 321 insertions(+), 25 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 76e2e6c136..cbc8d93fec 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -694,6 +694,15 @@ kernel_do_deploy_append() {
# ${UBOOT_DTB_IMAGE} since it contains ${PV} which is 
aimed
# for u-boot, but we are in kernel env now.
install -m 0644 ${B}/u-boot-${MACHINE}*.dtb 
"$deployDir/"
+   if [ "${SPL_SIGN_ENABLE}" = "1" -a -n "${UBOOT_BINARY}" 
-a -n "${SPL_DTB_BINARY}" ] ; then
+   # If we're also signing the uboot fit, now we 
need to
+   # deploy it, it's its file, as well as 
u-boot-spl.dtb
+   install -m 0644 ${B}/u-boot-spl-${MACHINE}*.dtb 
"$deployDir/"
+   echo "Copying u-boot-fitImage file..."
+   install -m 0644 ${B}/u-boot-fitImage-* 
"$deployDir/"
+   echo "Copying u-boot-its file..."
+   install -m 0644 ${B}/u-boot-its-* "$deployDir/"
+   fi
fi
fi
 }
@@ -711,4 +720,4 @@ python () {
 bb.build.deltask('do_assemble_fitimage', d)
 bb.build.deltask('generate_rsa_keys', d)
 bb.build.addtask('generate_rsa_keys', 
'do_assemble_fitimage_initramfs', 'do_bundle_initramfs', d)
-}
\ No newline at end of file
+}
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index d57bef6669..86380f2234 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -36,23 +36,27 @@ inherit uboot-config
 
 # Signature activation.
 UBOOT_SIGN_ENABLE ?= "0"
+SPL_SIGN_ENABLE ?= "0"
 
 # Default value for deployment filenames.
 UBOOT_DTB_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.dtb"
 UBOOT_DTB_BINARY ?= "u-boot.dtb"
 UBOOT_DTB_SYMLINK ?= "u-boot-${MACHINE}.dtb"
-UBOOT_NODTB_IMAGE ?= "u-boot-nodtb-${MACHINE}-${PV}-${PR}.${UBOOT_SUFFIX}"
-UBOOT_NODTB_BINARY ?= "u-boot-nodtb.${UBOOT_SUFFIX}"
-UBOOT_NODTB_SYMLINK ?= "u-boot-nodtb-${MACHINE}.${UBOOT_SUFFIX}"
-UBOOT_ITS_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.its"
+UBOOT_NODTB_IMAGE ?= "u-boot-nodtb-${MACHINE}-${PV}-${PR}.bin"
+UBOOT_NODTB_BINARY ?= "u-boot-nodtb.bin"
+UBOOT_NODTB_SYMLINK ?= "u-boot-nodtb-${MACHINE}.bin"
+UBOOT_ITS_IMAGE ?= "u-boot-its-${MACHINE}-${PV}-${PR}"
 UBOOT_ITS ?= "u-boot.its"
-UBOOT_ITS_SYMLINK ?= "u-boot-${MACHINE}.its"
-SPL_DIR ?= "${@os.path.dirname(d.getVar("SPL_BINARY")) or '.'}"
+UBOOT_ITS_SYMLINK ?= "u-boot-its-${MACHINE}"
+UBOOT_FITIMAGE_IMAGE ?= "u-boot-fitImage-${MACHINE}-${PV}-${PR}"
+UBOOT_FITIMAGE_BINARY ?= "u-boot-fitImage"
+UBOOT_FITIMAGE_SYMLINK ?= "u-boot-fitImage-${MACHINE}"
+SPL_DIR ?= "spl/"
 SPL_DTB_IMAGE ?= "u-boot-spl-${MACHINE}-${PV}-${PR}.dtb"
 SPL_DTB_BINARY ?= "u-boot-spl.dtb"
 SPL_DTB_SYMLINK ?= "u-boot-spl-${MACHINE}.dtb"
 SPL_NODTB_IMAGE ?= 
"${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${MACHINE}-${PV}-${PR}${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[1]}"
-SPL_NODTB_BINARY ?= 
"${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[1]}"
+SPL_NODTB_BINARY ?= "u-boot-spl-nodtb.bin"
 SPL_NODTB_SYMLINK ?= 
"${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${MACHINE}${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[1]}"
 
 # fitImage Hash Algo
@@ -77,8 +81,18 @@ FIT_KEY_REQ_ARGS ?= "-batch -new"
 # Standard format for public key certificate
 FIT_KEY_SIGN_PKCS ?= "-x509"
 
-# Functions in this bbclass is for u-boot only
+# Functions on this bbclass can apply to either U-boot or Kernel,
+# depending on the scenario
 UBOOT_PN = "${@d.getVar('PREFERRED_PROVIDER_u-boot') or 'u-boot'}"
+KERNEL_PN = "${@d.getVar('PREFERRED_PROVIDER_virtual/kernel')}"
+
+# We need u-boot-tools-native if we're about to sign the SPL
+python() {
+if d.getVar('SPL_SIGN_ENABLE') == '1':
+depends = d.getVar("DEPENDS")
+depends = "%s u-boot-tools-native dtc-native" % depends
+d.setVar("DEPENDS", depends)
+}
 
 concat_dtb_helper() {
if [ -e "${UBOOT_DTB_BINARY}" ]; then
@@ -92,21 +106,59 @@ concat_dtb_helper() {
ln -sf ${UBOOT_NODTB_IMAGE} ${DEPLOYDIR}/${UBOOT_NODTB_BINARY}
fi
 
-   # Concatenate U-Boot w/o DTB & DTB with public key
-   # (cf. kernel-fitimage.bbclass for more details)
-   deployed_uboot_dtb_binary='${DEPLOY_DIR_IMAGE}/${UBOOT_DTB_IMAGE}'
-   if

[OE-core] [PATCH 1/4] u-boot: Move definitions to common locations

Move some definitions from u-boot.inc into uboot-config.bbclass and
similarly from kernel-fitimage.bbclass into uboot-sign.bbclass, so that
they can be useful when signing the U-boot proper fitimage, for a
verified-boot SPL.

Signed-off-by: Klaus Heinrich Kiwi 
---
 meta/classes/kernel-fitimage.bbclass | 58 
 meta/classes/uboot-config.bbclass| 56 +++
 meta/classes/uboot-sign.bbclass  | 35 +
 meta/recipes-bsp/u-boot/u-boot.inc   | 46 --
 4 files changed, 91 insertions(+), 104 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index f5082c93df..76e2e6c136 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -53,30 +53,6 @@ python __anonymous () {
 d.appendVarFlag('do_assemble_fitimage_initramfs', 'depends', ' 
%s:do_populate_sysroot' % uboot_pn)
 }
 
-# Options for the device tree compiler passed to mkimage '-D' feature:
-UBOOT_MKIMAGE_DTCOPTS ??= ""
-
-# fitImage Hash Algo
-FIT_HASH_ALG ?= "sha256"
-
-# fitImage Signature Algo
-FIT_SIGN_ALG ?= "rsa2048"
-
-# Generate keys for signing fitImage
-FIT_GENERATE_KEYS ?= "0"
-
-# Size of private key in number of bits
-FIT_SIGN_NUMBITS ?= "2048"
-
-# args to openssl genrsa (Default is just the public exponent)
-FIT_KEY_GENRSA_ARGS ?= "-F4"
-
-# args to openssl req (Default is -batch for non interactive mode and
-# -new for new certificate)
-FIT_KEY_REQ_ARGS ?= "-batch -new"
-
-# Standard format for public key certificate
-FIT_KEY_SIGN_PKCS ?= "-x509"
 
 # Description string
 FIT_DESC ?= "U-Boot fitImage for ${DISTRO_NAME}/${PV}/${MACHINE}"
@@ -84,13 +60,6 @@ FIT_DESC ?= "U-Boot fitImage for 
${DISTRO_NAME}/${PV}/${MACHINE}"
 # Sign individual images as well
 FIT_SIGN_INDIVIDUAL ?= "0"
 
-# mkimage command
-UBOOT_MKIMAGE ?= "uboot-mkimage"
-UBOOT_MKIMAGE_SIGN ?= "${UBOOT_MKIMAGE}"
-
-# Arguments passed to mkimage for signing
-UBOOT_MKIMAGE_SIGN_ARGS ?= ""
-
 #
 # Emit the fitImage ITS header
 #
@@ -692,33 +661,6 @@ do_assemble_fitimage_initramfs() {
 
 addtask assemble_fitimage_initramfs before do_deploy after do_bundle_initramfs
 
-do_generate_rsa_keys() {
-   if [ "${UBOOT_SIGN_ENABLE}" = "0" ] && [ "${FIT_GENERATE_KEYS}" = "1" 
]; then
-   bbwarn "FIT_GENERATE_KEYS is set to 1 eventhough 
UBOOT_SIGN_ENABLE is set to 0. The keys will not be generated as they won't be 
used."
-   fi
-
-   if [ "${UBOOT_SIGN_ENABLE}" = "1" ] && [ "${FIT_GENERATE_KEYS}" = "1" 
]; then
-
-   # Generate keys only if they don't already exist
-   if [ ! -f "${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".key ] || 
\
-   [ ! -f 
"${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".crt]; then
-
-   # make directory if it does not already exist
-   mkdir -p "${UBOOT_SIGN_KEYDIR}"
-
-   echo "Generating RSA private key for signing fitImage"
-   openssl genrsa ${FIT_KEY_GENRSA_ARGS} -out \
-   
"${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".key \
-   "${FIT_SIGN_NUMBITS}"
-
-   echo "Generating certificate for signing fitImage"
-   openssl req ${FIT_KEY_REQ_ARGS} "${FIT_KEY_SIGN_PKCS}" \
-   -key 
"${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".key \
-   -out 
"${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".crt
-   fi
-   fi
-}
-
 addtask generate_rsa_keys before do_assemble_fitimage after do_compile
 
 kernel_do_deploy[vardepsexclude] = "DATETIME"
diff --git a/meta/classes/uboot-config.bbclass 
b/meta/classes/uboot-config.bbclass
index 89ff970fcc..31487c1418 100644
--- a/meta/classes/uboot-config.bbclass
+++ b/meta/classes/uboot-config.bbclass
@@ -11,7 +11,63 @@
 #
 # Copyright 2013, 2014 (C) O.S. Systems Software LTDA.
 
+# Some versions of u-boot use .bin and others use .img.  By default use .bin
+# but enable individual recipes to change this value.
+UBOOT_SUFFIX ??= "bin"
 UBOOT_BINARY ?= "u-boot.${UBOOT_SUFFIX}"
+UBOOT_BINARYNAME ?= "${@os.path.splitext(d.getVar("UBOOT_BINARY"))[0]}"
+UBOOT_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.${UBOOT_SUFFIX}"
+UBOOT_SYMLINK ?= "u-boot-${MACHINE}.${UBOOT_SUFFIX}"
+UBOOT_MAKE_TARGET ?= "all"
+
+# Output the ELF generated. Some platforms can use the ELF file and directly
+# load it (JTAG booting, QEMU) additionally the ELF can be used for debugging
+# purposes.
+UBOOT_ELF ?= ""
+UBOOT_ELF_SUFFIX ?= "elf"
+UBOOT_ELF_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.${UBOOT_ELF_SUFFIX}"
+UBOOT_ELF_BINARY ?= "u-boot.${UBOOT_ELF_SUFFIX}"
+UBOOT_ELF_SYMLINK ?= "u-boot-${MACHINE}.${UBOOT_ELF_SUFFIX}"
+
+# Some versions of u-boot build an SPL (Second Program Loader) image that
+# should be packaged along with the u-boot binary as well as placed in the
+# deploy directory.

[OE-core] [PATCH 3/4] u-boot: Use a different Key for SPL signing

Duplicate the variables governing u-boot signing so that we can have a
different set of keys/parameters signing the SPL.

Signed-off-by: Klaus Heinrich Kiwi 
---
 meta/classes/uboot-config.bbclass |  2 ++
 meta/classes/uboot-sign.bbclass   | 55 ---
 2 files changed, 46 insertions(+), 11 deletions(-)

diff --git a/meta/classes/uboot-config.bbclass 
b/meta/classes/uboot-config.bbclass
index 31487c1418..3bba02828b 100644
--- a/meta/classes/uboot-config.bbclass
+++ b/meta/classes/uboot-config.bbclass
@@ -61,6 +61,7 @@ UBOOT_EXTLINUX_SYMLINK ?= 
"${UBOOT_EXTLINUX_CONF_NAME}-${MACHINE}-${PR}"
 
 # Options for the device tree compiler passed to mkimage '-D' feature:
 UBOOT_MKIMAGE_DTCOPTS ??= ""
+SPL_MKIMAGE_DTCOPTS ??= ""
 
 # mkimage command
 UBOOT_MKIMAGE ?= "uboot-mkimage"
@@ -68,6 +69,7 @@ UBOOT_MKIMAGE_SIGN ?= "${UBOOT_MKIMAGE}"
 
 # Arguments passed to mkimage for signing
 UBOOT_MKIMAGE_SIGN_ARGS ?= ""
+SPL_MKIMAGE_SIGN_ARGS ?= ""
 
 python () {
 ubootmachine = d.getVar("UBOOT_MACHINE")
diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
index 86380f2234..2ec93e0b8e 100644
--- a/meta/classes/uboot-sign.bbclass
+++ b/meta/classes/uboot-sign.bbclass
@@ -59,27 +59,34 @@ SPL_NODTB_IMAGE ?= 
"${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${
 SPL_NODTB_BINARY ?= "u-boot-spl-nodtb.bin"
 SPL_NODTB_SYMLINK ?= 
"${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[0]}-nodtb-${MACHINE}${@os.path.splitext(d.getVar("SPL_BINARYNAME"))[1]}"
 
-# fitImage Hash Algo
+# Kernel / U-Boot fitImage Hash Algo
 FIT_HASH_ALG ?= "sha256"
+UBOOT_FIT_HASH_ALG ?= "sha256"
 
-# fitImage Signature Algo
+# Kernel / U-Boot fitImage Signature Algo
 FIT_SIGN_ALG ?= "rsa2048"
+UBOOT_FIT_SIGN_ALG ?= "rsa2048"
 
-# Generate keys for signing fitImage
+# Generate keys for signing Kernel / U-Boot fitImage
 FIT_GENERATE_KEYS ?= "0"
+UBOOT_FIT_GENERATE_KEYS ?= "0"
 
-# Size of private key in number of bits
+# Size of private keys in number of bits
 FIT_SIGN_NUMBITS ?= "2048"
+UBOOT_FIT_SIGN_NUMBITS ?= "2048"
 
 # args to openssl genrsa (Default is just the public exponent)
 FIT_KEY_GENRSA_ARGS ?= "-F4"
+UBOOT_FIT_KEY_GENRSA_ARGS ?= "-F4"
 
 # args to openssl req (Default is -batch for non interactive mode and
 # -new for new certificate)
 FIT_KEY_REQ_ARGS ?= "-batch -new"
+UBOOT_FIT_KEY_REQ_ARGS ?= "-batch -new"
 
 # Standard format for public key certificate
 FIT_KEY_SIGN_PKCS ?= "-x509"
+UBOOT_FIT_KEY_SIGN_PKCS ?= "-x509"
 
 # Functions on this bbclass can apply to either U-boot or Kernel,
 # depending on the scenario
@@ -280,6 +287,32 @@ do_generate_rsa_keys() {
-out 
"${UBOOT_SIGN_KEYDIR}/${UBOOT_SIGN_KEYNAME}".crt
fi
fi
+
+   if [ "${SPL_SIGN_ENABLE}" = "0" ] && [ "${UBOOT_FIT_GENERATE_KEYS}" = 
"1" ]; then
+   bbwarn "UBOOT_FIT_GENERATE_KEYS is set to 1 eventhough 
SPL_SIGN_ENABLE is set to 0. The keys will not be generated as they won't be 
used."
+   fi
+
+   if [ "${SPL_SIGN_ENABLE}" = "1" ] && [ "${UBOOT_FIT_GENERATE_KEYS}" = 
"1" ]; then
+
+   # Generate keys only if they don't already exist
+   if [ ! -f "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".key ] || \
+   [ ! -f "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".crt ]; 
then
+
+   # make directory if it does not already exist
+   mkdir -p "${SPL_SIGN_KEYDIR}"
+
+   echo "Generating RSA private key for signing U-Boot 
fitImage"
+   openssl genrsa ${UBOOT_FIT_KEY_GENRSA_ARGS} -out \
+   "${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".key \
+   "${UBOOT_FIT_SIGN_NUMBITS}"
+
+   echo "Generating certificate for signing U-Boot 
fitImage"
+   openssl req ${FIT_KEY_REQ_ARGS} 
"${UBOOT_FIT_KEY_SIGN_PKCS}" \
+   -key 
"${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".key \
+   -out 
"${SPL_SIGN_KEYDIR}/${SPL_SIGN_KEYNAME}".crt
+   fi
+   fi
+
 }
 
 addtask generate_rsa_keys before do_uboot_assemble_fitimage after do_compile
@@ -292,9 +325,9 @@ uboot_fitimage_assemble() {
uboot_dtb="${3}"
uboot_bin="${4}"
spl_dtb="${5}"
-   uboot_csum="${FIT_HASH_ALG}"
-   uboot_sign_algo="${FIT_SIGN_ALG}"
-   uboot_sign_keyname="${UBOOT_SIGN_KEYNAME}"
+   uboot_csum="${UBOOT_FIT_HASH_ALG}"
+   uboot_sign_algo="${UBOOT_FIT_SIGN_ALG}"
+   uboot_sign_keyname="${SPL_SIGN_KEYNAME}"
 
rm -f ${uboot_its} ${uboot_bin}
 
@@ -349,7 +382,7 @@ EOF
# Assemble the U-boot FIT image
#
${UBOOT_MKIMAGE} \
-   ${@'-D "${UBOOT_MKIMAGE_DTCOPTS}"' if 
len('${UBOOT_MKIMAGE_DTCOPTS}') else ''} \
+   ${@'-D "${SPL_MKIMAGE_DTCOPTS}"' if 
len('${SPL_MKIMAGE_DTCOPTS}') else ''} \
-f ${uboot_its} \

[OE-core] [PATCH 0/4] u-boot: Support for SPL verified boot

This patch series aims at extending U-Boot's verified boot support to
also include SPL.

Presently, setting UBOOT_SIGN_ENABLE instructs the classes uboot-sign
and kernel-fitimage to create and sign a Linux Kernel fitImage. This
proposal introduces the variable SPL_SIGN_ENABLE that aims at (re-)
creating the U-Boot (proper) uImage fitImage and signing it.

In order to accomplish this, the first patch moves some of necessary
infrastructure (variables, functions) used to sign the Kernel
fitImage to more common locations, and then essentially duplicates the
method currently used to sign the Kernel fitImage to also sign the
U-Boot fitImage.

In the UBOOT_SIGN_ENABLE = "1" scenario, nothing really changes: The
Kernel fitImage is created, then signed, and the pubkey is added to
u-boot.dtb which is concatenated with the u-boot-nodtb.bin to create
the u-boot final image.

In case SPL_SIGN_ENABLE = "1", The U-Boot PN will take care of (re-)
creating the U-Boot fitImage (using custom .its script) after compile,
sign it, and contatenate the u-boot-spl.dtb (with the public key) with
u-boot-spl-nodtb.bin to create the final U-Boot SPl on deploy.

In case both UBOOT_SIGN_ENABLE and SPL_SIGN_ENABLE are set, the Kernel
PN will take care of creating and signing the U-Boot fitImage (becase
we need to also sign the FDT image containing the Kernel pubkey), and
take care of deploying it.

One caveat is that when moving between the scenarios above, the user
might need to remove the tmp/ directory, since there could be a
collision for some of the files deployed into the images directory,
since the configuration may determine which PN does that.

I added oe-selftest testcases and also tested this on upstream OpenBMC
with AST2600 BMC devices.


 meta/classes/kernel-fitimage.bbclass |  69 +++-
 meta/classes/uboot-config.bbclass|  58 +
 meta/classes/uboot-sign.bbclass  | 395
-
 meta/lib/oeqa/selftest/cases/fitimage.py | 293
++
 meta/recipes-bsp/u-boot/u-boot.inc   |  46 ---
 5 files changed, 736 insertions(+), 125 deletions(-)


Signed-off-by: Klaus Heinrich Kiwi 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149533): 
https://lists.openembedded.org/g/openembedded-core/message/149533
Mute This Topic: https://lists.openembedded.org/mt/81354682/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] libxkbcommon: upgrading to 1.1.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxkbcommon* to *1.1.0* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-libxkbcommon-upgrade-1.0.3-1.1.0.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/libxkbcommon: SRC_URI changed from 
"http://xkbcommon.org/download/libxkbcommon-1.0.3.tar.xz; to 
"http://xkbcommon.org/download/libxkbcommon-1.1.0.tar.xz;
packages/core2-32-poky-linux/libxkbcommon: PV changed from "1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon: PKGV changed from 1.0.3 [default] to 
1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dbg: PV changed from 
"1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dbg: PKGV changed from 
1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PKGSIZE changed 
from 311263 to 330460 (+6%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PV changed from 
"1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-dev: PKGV changed from 
1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-doc: PV changed from 
"1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-doc: PKGV changed from 
1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-locale: PV changed from 
"1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-locale: PKGV changed 
from 1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PKGSIZE changed 
from 1348341 to 1365371 (+1%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PV changed from 
"1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-src: PKGV changed from 
1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-staticdev: PV changed 
from "1.0.3" to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon-staticdev: PKGV changed 
from 1.0.3 [default] to 1.1.0 [default]
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon: PKGSIZE changed from 
430010 to 434106 (+1%)
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon: PV changed from "1.0.3" 
to "1.1.0"
packages/core2-32-poky-linux/libxkbcommon/libxkbcommon: PKGV changed from 1.0.3 
[default] to 1.1.0 [default]
>From 9a264549a1e5774a9e45076643f7f203b35a35f7 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 13:28:50 +
Subject: [PATCH] libxkbcommon: upgrade 1.0.3 -> 1.1.0

---
 .../xorg-lib/{libxkbcommon_1.0.3.bb => libxkbcommon_1.1.0.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xorg-lib/{libxkbcommon_1.0.3.bb => libxkbcommon_1.1.0.bb} (92%)

diff --git a/meta/recipes-graphics/xorg-lib/libxkbcommon_1.0.3.bb b/meta/recipes-graphics/xorg-lib/libxkbcommon_1.1.0.bb
similarity index 92%
rename from meta/recipes-graphics/xorg-lib/libxkbcommon_1.0.3.bb
rename to meta/recipes-graphics/xorg-lib/libxkbcommon_1.1.0.bb
index 99f55f4a14..a1dbda0e06 100644
--- a/meta/recipes-graphics/xorg-lib/libxkbcommon_1.0.3.bb
+++ b/meta/recipes-graphics/xorg-lib/libxkbcommon_1.1.0.bb
@@ -9,7 +9,7 @@ DEPENDS = "util-macros flex-native bison-native"
 
 SRC_URI = "http://xkbcommon.org/download/${BPN}-${PV}.tar.xz;
 
-SRC_URI[sha256sum] = "a2202f851e072b84e64a395212cbd976ee18a8ee602008b0bad02a13247dbc52"
+SRC_URI[sha256sum] = "412cfcca596f92914ea1a66ad244804d73a5ff20b6d86459951e7ad20576c246"
 
 UPSTREAM_CHECK_URI = "http://xkbcommon.org/;
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149521): 
https://lists.openembedded.org/g/openembedded-core/message/149521
Mute This Topic: https://lists.openembedded.org/mt/81354134/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] gnutls: upgrading to 3.7.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnutls* to *3.7.1* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-gnutls-upgrade-3.7.0-3.7.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
>From 2eff972f828ace6f7c90036fe9d07a435f486a0f Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 15:30:13 +
Subject: [PATCH] gnutls: upgrade 3.7.0 -> 3.7.1

---
 .../recipes-support/gnutls/{gnutls_3.7.0.bb => gnutls_3.7.1.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/gnutls/{gnutls_3.7.0.bb => gnutls_3.7.1.bb} (96%)

diff --git a/meta/recipes-support/gnutls/gnutls_3.7.0.bb b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
similarity index 96%
rename from meta/recipes-support/gnutls/gnutls_3.7.0.bb
rename to meta/recipes-support/gnutls/gnutls_3.7.1.bb
index 1aa94ece3a..51d472c828 100644
--- a/meta/recipes-support/gnutls/gnutls_3.7.0.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.7.1.bb
@@ -23,7 +23,7 @@ SRC_URI = "https://www.gnupg.org/ftp/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar
file://arm_eabi.patch \
"
 
-SRC_URI[sha256sum] = "49e2a22691d252c9f24a9829b293a8f359095bc5a818351f05f1c0a5188a1df8"
+SRC_URI[sha256sum] = "3777d7963eca5e06eb315686163b7b3f5045e2baac5e54e038ace9835e5cac6f"
 
 inherit autotools texinfo pkgconfig gettext lib_package gtk-doc
 
-- 
2.17.1

packages/core2-32-poky-linux/gnutls/gnutls-bin: PV changed from "3.7.0" to 
"3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-bin: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PV changed from "3.7.0" to 
"3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PKGSIZE changed from 10114568 
to 10124900 (+0%)
packages/core2-32-poky-linux/gnutls/gnutls-dbg: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-dev: PV changed from "3.7.0" to 
"3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-dev: PKGSIZE changed from 568366 to 
568423 (+0%)
packages/core2-32-poky-linux/gnutls/gnutls-dev: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-doc: PV changed from "3.7.0" to 
"3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-doc: PKGSIZE changed from 4307771 to 
4308680 (+0%)
packages/core2-32-poky-linux/gnutls/gnutls-doc: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-cs: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-cs: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-de: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-de: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-eo: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-eo: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-es: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-es: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-fi: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-fi: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-fr: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-fr: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-it: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-it: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-ms: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-ms: PKGSIZE changed from 
18136 to 19230 (+6%)
packages/core2-32-poky-linux/gnutls/gnutls-locale-ms: PKGV changed from 3.7.0 
[default] to 3.7.1 [default]
packages/core2-32-poky-linux/gnutls/gnutls-locale-nl: PV changed from "3.7.0" 
to "3.7.1"
packages/core2-32-poky-linux/gnutls/gnutls-locale-nl: PKGV changed from

[OE-core] [AUH] lttng-modules: upgrading to 2.12.5 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-modules* to *2.12.5* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-lttng-modules-upgrade-2.12.4-2.12.5.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/qemux86-poky-linux/lttng-modules/kernel-module-lttng-clock-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-clock-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-clock-plugin-test-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-clock-plugin-test-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-kprobes-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-kprobes-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-kretprobes-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-kretprobes-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-lib-ring-buffer-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-lib-ring-buffer-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-block-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-block-5.10.21-yocto-standard:
 PKGSIZE changed from 35584 to 35740 (+0%)
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-block-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-btrfs-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-btrfs-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-compaction-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-compaction-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-ext4-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-ext4-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-gpio-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-gpio-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-i2c-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-i2c-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-irq-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-irq-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-jbd2-5.10.21-yocto-standard:
 PKGV changed from 2.12.4 [default] to 2.12.5 [default]
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-jbd2-5.10.21-yocto-standard:
 PV changed from "2.12.4" to "2.12.5"
packages/qemux86-poky-linux/lttng-modules/kernel-module-lttng-probe-kmem-5.10.21-yocto-standard:
 PKGV changed from

[OE-core] [AUH] Upgrade status: 2021-03-15

Recipe upgrade statistics:

* Succeeded: 39
gnu-efi, 3.0.13, Yi Zhao 
openssh, 8.5p1, Armin Kuster 
autoconf-archive, 2021.02.19, Robert Yang 
bison, 3.7.6, Chen Qi 
btrfs-tools, 5.11, Wang Mingyu 
createrepo-c, 0.17.1, Alexander Kanavin 
dnf, 4.6.1, Alexander Kanavin 
e2fsprogs, 1.46.2, Robert Yang 
gptfdisk, 1.0.7, Alexander Kanavin 
libedit, 20210216-3.1, Khem Raj 
liburi-perl, 5.08, Tim Orling 
python3-hypothesis, 6.8.1, Tim Orling 
python3-importlib-metadata, 3.7.3, Tim Orling 

python3-setuptools-scm, 5.0.2, Tim Orling 

python3-setuptools, 54.1.2, Oleksandr Kravchuk 

less, 580, Yi Zhao 
msmtp, 1.8.15, Wang Mingyu 
stress-ng, 0.12.05, Anuj Mittal 
sudo, 1.9.6, Chen Qi 
zstd, 1.4.9, Alexander Kanavin 
epiphany, 3.38.3, Alexander Kanavin 
gtk+3, 3.24.27, Ross Burton 
pango, 1.48.3, Ross Burton 
piglit, 1.0-new-commits-available, Ross Burton 
vulkan-headers, 1.2.170.0, Anuj Mittal 
libinput, 1.17.0, Ross Burton 
libxkbcommon, 1.1.0, Armin Kuster 
xorgproto, 2021.3, Armin Kuster 
babeltrace2, 2.0.4, Alexander Kanavin 
lttng-modules, 2.12.5, Richard Purdie 

lttng-tools, 2.12.3, Richard Purdie 
wpebackend-fdo, 1.8.1, Alexander Kanavin 
acl, 2.3.0, Chen Qi 
diffoscope, 169, Joshua Watt 
gnutls, 3.7.1, Armin Kuster 
libcap, 2.49, Yi Zhao 
rng-tools, 6.12, Anuj Mittal 
sqlite3, 3.35.0, Anuj Mittal 
vte, 0.62.3, Anuj Mittal 
* Failed(do_compile): 11
bind, 9.16.12, Armin Kuster 
systemd-boot, 247.4, Chen Qi 
systemd, 247.4, Chen Qi 
cmake, 3.19.6, Pascal Bach 
git, 2.30.2, Robert Yang 
go-runtime, 1.16.2, Khem Raj 
go, 1.16.2, Khem Raj 
procps, 3.3.17, Alexander Kanavin 
spirv-tools, 2020.7, Jose Quaresma 
vulkan-loader, 1.2.170.0, Anuj Mittal 
vulkan-tools, 1.2.170.0, Anuj Mittal 
* Failed (devtool error): 12
apt, 2.2.2, Aníbal Limón 
automake, 1.16.3, Robert Yang 
gnu-config, 20210125-new-commits-available, Robert Yang 

libdnf, 0.60.0, Alexander Kanavin 
strace, 5.11, Robert Yang 
asciidoc, 9.1.0, Yi Zhao 
gdk-pixbuf, 2.42.2, Ross Burton 
adwaita-icon-theme, 3.38.0, Ross Burton 
libhandy, 1.2.0, Alexander Kanavin 
mesa, 21.0.0, Otavio Salvador 
vulkan-samples, git-new-commits-available, Ross Burton 

attr, 2.5.0, Chen Qi 

TOTAL: attempted=62 succeeded=39(62.90%) failed=23(37.10%)

Recipe upgrade statistics per Maintainer:

Tim Orling 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149532): 
https://lists.openembedded.org/g/openembedded-core/message/149532
Mute This Topic: https://lists.openembedded.org/mt/81354145/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] wpebackend-fdo: upgrading to 1.8.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wpebackend-fdo* to *1.8.1* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-wpebackend-fdo-upgrade-1.8.0-1.8.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
packages/core2-32-poky-linux/wpebackend-fdo: PKGV changed from 1.8.0 [default] 
to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo: PV changed from "1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo: SRC_URI changed from 
"https://wpewebkit.org/releases/wpebackend-fdo-1.8.0.tar.xz; to 
"https://wpewebkit.org/releases/wpebackend-fdo-1.8.1.tar.xz;
Changes to packages/core2-32-poky-linux/wpebackend-fdo (sysroot):
  /usr/lib/libWPEBackend-fdo-1.0.so.1 changed symlink target from 
libWPEBackend-fdo-1.0.so.1.6.3 to libWPEBackend-fdo-1.0.so.1.6.4
  /usr/lib/libWPEBackend-fdo-1.0.so.1.6.3 moved to 
/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dbg: PKGV changed 
from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dbg: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dbg: PV changed from 
"1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dbg: PKGSIZE changed 
from 117 to 1230520 (+5%)
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dev: PKGV changed 
from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dev: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dev: PV changed from 
"1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-dev: PKGSIZE changed 
from 35669 to 35603 (-0%)
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-doc: PKGV changed 
from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-doc: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-doc: PV changed from 
"1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-locale: PKGV changed 
from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-locale: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-locale: PV changed 
from "1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-src: PKGV changed 
from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-src: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-src: PV changed from 
"1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-src: PKGSIZE changed 
from 254273 to 255123 (+0%)
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-staticdev: PKGV 
changed from 1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-staticdev: FILELIST: 
removed "/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo-staticdev: PV 
changed from "1.8.0" to "1.8.1"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo: PKGV changed from 
1.8.0 [default] to 1.8.1 [default]
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo: FILELIST: removed 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.3", added 
"/usr/lib/libWPEBackend-fdo-1.0.so.1.6.4"
packages/core2-32-poky-linux/wpebackend-fdo/wpebackend-fdo: PV changed from 
"1.8.0" to "1.8.1"
>From 9f46ead35a99afa370ba6dc71f734e15d6c534a5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 14:32:10 +
Subject: [PATCH] wpebackend-fdo: upgrade 1.8.0 -> 1.8.1

---
 .../webkit/{wpebackend-fdo_1.8.0.bb => wpebackend-fdo_1.8.1.bb} | 2 +-

[OE-core] [AUH] libinput: upgrading to 1.17.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libinput* to *1.17.0* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-libinput-upgrade-1.16.4-1.17.0.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/libinput: SRC_URI changed from 
"http://www.freedesktop.org/software/libinput/libinput-1.16.4.tar.xz 
file://run-ptest file://determinism.patch" to 
"http://www.freedesktop.org/software/libinput/libinput-1.17.0.tar.xz 
file://run-ptest file://determinism.patch"
packages/core2-32-poky-linux/libinput: PKGV changed from 1.16.4 [default] to 
1.17.0 [default]
packages/core2-32-poky-linux/libinput: PV changed from "1.16.4" to "1.17.0"
packages/core2-32-poky-linux/libinput/libinput-bin: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-bin: PV changed from "1.16.4" to 
"1.17.0"
packages/core2-32-poky-linux/libinput/libinput-bin: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-dbg: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-dbg: PV changed from "1.16.4" to 
"1.17.0"
packages/core2-32-poky-linux/libinput/libinput-dbg: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-dbg: PKGSIZE changed from 
4480232 to 4863520 (+9%)
packages/core2-32-poky-linux/libinput/libinput-dev: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-dev: PV changed from "1.16.4" to 
"1.17.0"
packages/core2-32-poky-linux/libinput/libinput-dev: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-dev: PKGSIZE changed from 191975 
to 191967 (-0%)
packages/core2-32-poky-linux/libinput/libinput-doc: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-doc: PV changed from "1.16.4" to 
"1.17.0"
packages/core2-32-poky-linux/libinput/libinput-doc: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-doc: PKGSIZE changed from 38565 
to 41407 (+7%)
packages/core2-32-poky-linux/libinput/libinput-locale: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-locale: PV changed from "1.16.4" 
to "1.17.0"
packages/core2-32-poky-linux/libinput/libinput-locale: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-ptest: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-ptest: PV changed from "1.16.4" 
to "1.17.0"
packages/core2-32-poky-linux/libinput/libinput-ptest: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-ptest: PKGSIZE changed from 
1138598 to 1179126 (+4%)
packages/core2-32-poky-linux/libinput/libinput-src: PKGV changed from 1.16.4 
[default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-src: PV changed from "1.16.4" to 
"1.17.0"
packages/core2-32-poky-linux/libinput/libinput-src: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"
packages/core2-32-poky-linux/libinput/libinput-src: PKGSIZE changed from 
3154797 to 3222080 (+2%)
packages/core2-32-poky-linux/libinput/libinput-staticdev: PKGV changed from 
1.16.4 [default] to 1.17.0 [default]
packages/core2-32-poky-linux/libinput/libinput-staticdev: PV changed from 
"1.16.4" to "1.17.0"
packages/core2-32-poky-linux/libinput/libinput-staticdev: FILELIST: added 
"/usr/libexec/libinput/libinput-analyze-recording 
/usr/libexec/libinput/libinput-analyze-touch-down-state"

[OE-core] [AUH] vulkan-tools: upgrading to 1.2.170.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.2.170.0* 
has Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-vulkan-tools-upgrade-1.2.162.1-1.2.170.0.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
>From 8ec397bc7d5c8a81a7017daa8e5731aabfdd84e4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 13:00:01 +
Subject: [PATCH] vulkan-tools: upgrade 1.2.162.1 -> 1.2.170.0

---
 .../{vulkan-tools_1.2.162.1.bb => vulkan-tools_1.2.170.0.bb}| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/vulkan/{vulkan-tools_1.2.162.1.bb => vulkan-tools_1.2.170.0.bb} (95%)

diff --git a/meta/recipes-graphics/vulkan/vulkan-tools_1.2.162.1.bb b/meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb
similarity index 95%
rename from meta/recipes-graphics/vulkan/vulkan-tools_1.2.162.1.bb
rename to meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb
index a5c3bbcb14..3d3d58aa9e 100644
--- a/meta/recipes-graphics/vulkan/vulkan-tools_1.2.162.1.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb
@@ -7,7 +7,7 @@ SECTION = "libs"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
 SRC_URI = "git://github.com/KhronosGroup/Vulkan-Tools.git;branch=sdk-1.2.162"
-SRCREV = "8f0c2e40d4134f53f82ce48de72c7be92baa6b3d"
+SRCREV = "88ea55de928a08ba5c5f65a93d1e7c8f666fc43f"
 
 S = "${WORKDIR}/git"
 
-- 
2.17.1

Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 814 .bb files complete (813 cached, 1 parsed). 1438 targets, 31 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-3448ddf0362ea1f5e5689eca51bda51080b628da"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:3448ddf0362ea1f5e5689eca51bda51080b628da"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 214 Local 205 Network 0 Missed 9 Current 526 (95% match, 
98% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 1578 of 2330 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb:do_fetch)
NOTE: recipe vulkan-tools-1.2.170.0-r0: task do_fetch: Started
WARNING: vulkan-tools-1.2.170.0-r0 do_fetch: Failed to fetch URL 
git://github.com/KhronosGroup/Vulkan-Tools.git;branch=sdk-1.2.162, attempting 
MIRRORS if available
ERROR: vulkan-tools-1.2.170.0-r0 do_fetch: Fetcher failure: Unable to find 
revision 88ea55de928a08ba5c5f65a93d1e7c8f666fc43f in branch sdk-1.2.162 even 
from upstream
ERROR: vulkan-tools-1.2.170.0-r0 do_fetch: Fetcher failure for URL: 
'git://github.com/KhronosGroup/Vulkan-Tools.git;branch=sdk-1.2.162'. Unable to 
fetch URL from any source.
ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-32-poky-linux/vulkan-tools/1.2.170.0-r0/temp/log.do_fetch.31734
NOTE: recipe vulkan-tools-1.2.170.0-r0: task do_fetch: Failed
ERROR: Task 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb:do_fetch)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 2315 tasks of which 2314 didn't need to be rerun 
and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

Summary: 1 task failed:
  
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-tools_1.2.170.0.bb:do_fetch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149522):

[OE-core] [AUH] acl: upgrading to 2.3.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acl* to *2.3.0* has Succeeded.

Next steps:
- apply the patch: git am 0001-acl-upgrade-2.2.53-2.3.0.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/acl/acl-dbg: PKGV changed from 2.2.53 [default] to 
2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-dbg: PKGSIZE changed from 297356 to 296780 
(-0%)
packages/core2-32-poky-linux/acl/acl-dbg: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-dev: PKGV changed from 2.2.53 [default] to 
2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-dev: PKGSIZE changed from 6533 to 6531 
(-0%)
packages/core2-32-poky-linux/acl/acl-dev: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-doc: PKGV changed from 2.2.53 [default] to 
2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-doc: PKGSIZE changed from 224926 to 225254 
(+0%)
packages/core2-32-poky-linux/acl/acl-doc: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-de: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-de: PKGSIZE changed from 6803 to 
8722 (+28%)
packages/core2-32-poky-linux/acl/acl-locale-de: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-en+boldquot: PKGV changed from 
2.2.53 [default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-en+boldquot: PKGSIZE changed from 
8499 to 8581 (+1%)
packages/core2-32-poky-linux/acl/acl-locale-en+boldquot: PV changed from 
"2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-en+quot: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-en+quot: PKGSIZE changed from 8415 
to 8497 (+1%)
packages/core2-32-poky-linux/acl/acl-locale-en+quot: PV changed from "2.2.53" 
to "2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-es: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-es: PKGSIZE changed from 7013 to 
6972 (-1%)
packages/core2-32-poky-linux/acl/acl-locale-es: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-fr: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-fr: PKGSIZE changed from 6718 to 
6677 (-1%)
packages/core2-32-poky-linux/acl/acl-locale-fr: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-gl: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-gl: PKGSIZE changed from 7011 to 
6970 (-1%)
packages/core2-32-poky-linux/acl/acl-locale-gl: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-pl: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-pl: PKGSIZE changed from 7045 to 
7004 (-1%)
packages/core2-32-poky-linux/acl/acl-locale-pl: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-locale-sv: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-locale-sv: PKGSIZE changed from 6653 to 
6612 (-1%)
packages/core2-32-poky-linux/acl/acl-locale-sv: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl-ptest: PKGV changed from 2.2.53 [default] 
to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-ptest: PKGSIZE changed from 787342 to 
787357 (+0%)
packages/core2-32-poky-linux/acl/acl-ptest: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-src: PKGV changed from 2.2.53 [default] to 
2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-src: PKGSIZE changed from 205672 to 206897 
(+1%)
packages/core2-32-poky-linux/acl/acl-src: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl/acl-staticdev: PKGV changed from 2.2.53 
[default] to 2.3.0 [default]
packages/core2-32-poky-linux/acl/acl-staticdev: PV changed from "2.2.53" to 
"2.3.0"
packages/core2-32-poky-linux/acl/acl: PKGV changed from 2.2.53 [default] to 
2.3.0 [default]
packages/core2-32-poky-linux/acl/acl: PKGSIZE changed from 78756 to 78612 (-0%)
packages/core2-32-poky-linux/acl/acl: PV changed from "2.2.53" to "2.3.0"
packages/core2-32-poky-linux/acl:

[OE-core] [AUH] pango: upgrading to 1.48.3 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pango* to *1.48.3* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-pango-upgrade-1.48.2-1.48.3.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/pango: PV changed from "1.48.2" to "1.48.3"
packages/core2-32-poky-linux/pango: SRC_URI changed from 
"https://ftp.gnome.org/pub/GNOME/sources/pango/1.48/pango-1.48.2.tar.xz;name=archive;
 to 
"https://ftp.gnome.org/pub/GNOME/sources/pango/1.48/pango-1.48.3.tar.xz;name=archive;
packages/core2-32-poky-linux/pango: PKGV changed from 1.48.2 [default] to 
1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-dbg: PKGSIZE changed from 1968392 to 
1977188 (+0%)
packages/core2-32-poky-linux/pango/pango-dbg: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-dbg: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-dbg: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3 /usr/lib/libpango-1.0.so.0.4800.3 
/usr/lib/libpangocairo-1.0.so.0.4800.3 /usr/lib/libpangoft2-1.0.so.0.4800.3"
packages/core2-32-poky-linux/pango/pango-dev: PKGSIZE changed from 1501222 to 
1434514 (-4%)
packages/core2-32-poky-linux/pango/pango-dev: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-dev: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-dev: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3 /usr/lib/libpango-1.0.so.0.4800.3 
/usr/lib/libpangocairo-1.0.so.0.4800.3 /usr/lib/libpangoft2-1.0.so.0.4800.3"
packages/core2-32-poky-linux/pango/pango-doc: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-doc: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-doc: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3 /usr/lib/libpango-1.0.so.0.4800.3 
/usr/lib/libpangocairo-1.0.so.0.4800.3 /usr/lib/libpangoft2-1.0.so.0.4800.3"
packages/core2-32-poky-linux/pango/pango-locale: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-locale: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-locale: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3 /usr/lib/libpango-1.0.so.0.4800.3 
/usr/lib/libpangocairo-1.0.so.0.4800.3 /usr/lib/libpangoft2-1.0.so.0.4800.3"
packages/core2-32-poky-linux/pango/pango-ptest: PKGSIZE changed from 1292918 to 
1293399 (+0%)
packages/core2-32-poky-linux/pango/pango-ptest: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-ptest: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-ptest: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3 /usr/lib/libpango-1.0.so.0.4800.3 
/usr/lib/libpangocairo-1.0.so.0.4800.3 /usr/lib/libpangoft2-1.0.so.0.4800.3"
packages/core2-32-poky-linux/pango/pango-src: PKGSIZE changed from 1848489 to 
1858425 (+1%)
packages/core2-32-poky-linux/pango/pango-src: PV changed from "1.48.2" to 
"1.48.3"
packages/core2-32-poky-linux/pango/pango-src: PKGV changed from 1.48.2 
[default] to 1.48.3 [default]
packages/core2-32-poky-linux/pango/pango-src: FILELIST: removed 
"/usr/lib/libpangoxft-1.0.so.0.4800.2 /usr/lib/libpangocairo-1.0.so.0.4800.2 
/usr/lib/libpango-1.0.so.0.4800.2 /usr/lib/libpangoft2-1.0.so.0.4800.2", added 
"/usr/lib/libpangoxft-1.0.so.0.4800.3

[OE-core] [AUH] python3-setuptools: upgrading to 54.1.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to 
*54.1.2* has Succeeded.

Next steps:
- apply the patch: git am 
0001-python3-setuptools-upgrade-54.1.1-54.1.2.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/python3-setuptools: PV changed from "54.1.1" to 
"54.1.2"
packages/core2-32-poky-linux/python3-setuptools: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-54.1.1.tar.gz
 file://0001-change-shebang-to-python3.patch" to 
"https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-54.1.2.tar.gz
 file://0001-change-shebang-to-python3.patch"
packages/core2-32-poky-linux/python3-setuptools: PKGV changed from 54.1.1 
[default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PV 
changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: 
PV changed from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: 
PKGV changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PV changed 
from "54.1.1" to "54.1.2"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGV 
changed from 54.1.1 [default] to 54.1.2 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGSIZE 
changed from 3028858 to 3029297 (+0%)
Changes to packages/core2-32-poky-linux/python3-setuptools (sysroot):
  /usr/lib/python3.9/site-packages/setuptools-54.1.1-py3.9.egg-info moved to 
/usr/lib/python3.9/site-packages/setuptools-54.1.2-py3.9.egg-info
Changes to packages/x86_64-linux/python3-setuptools-native (sysroot):
  /usr/lib/python3.9/site-packages/setuptools-54.1.1-py3.9.egg-info moved to 
/usr/lib/python3.9/site-packages/setuptools-54.1.2-py3.9.egg-info
>From c4c78a5b2cdcc566ff6aa64e71e6ec89ecf10d02 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:28:22 +
Subject: [PATCH] python3-setuptools: upgrade 54.1.1 -> 54.1.2

---
 ...0001-conditionally-do-not-fetch-code-by-easy_install.patch | 4 ++--
 ...hon3-setuptools_54.1.1.bb => python3-setuptools_54.1.2.bb} | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-devtools/python/{python3-setuptools_54.1.1.bb => python3-setuptools_54.1.2.bb} (94%)

diff --git a/meta/recipes-devtools/python/files/0001-conditionally-do-not-fetch-code-by-easy_install.patch b/meta/recipes-devtools/python/files/0001-conditionally-do-not-fetch-code-by-easy_install.patch
index 680edbe704..517d2c3421 100644
--- a/meta/recipes-devtools/python/files/0001-conditionally-do-not-fetch-code-by-easy_install.patch
+++ b/meta/recipes-devtools/python/files/0001-conditionally-do-not-fetch-code-by-easy_install.patch
@@ -1,4 +1,4 @@
-From 6380cc63f79abe8b8404c9be5ed5f213a70c8c6a Mon Sep 17 00:00:00

[OE-core] [AUH] adwaita-icon-theme: upgrading to 3.38.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *adwaita-icon-theme* to 
*3.38.0* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  finish -f adwaita-icon-theme 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-gnome/gnome
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 815 .bb files complete (813 cached, 2 parsed). 1441 targets, 31 
skipped, 0 masked, 0 errors.
ERROR: Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 121, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 131, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-gnome/gnome/conf/layer.conf
 not found

ERROR: Unable to parse 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-gnome/gnome/conf/layer.conf:
 [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-gnome/gnome/conf/layer.conf
 not found
Traceback (most recent call last):
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 162, in wrapped
return func(fn, *args)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 187, in parse_config_file
return bb.parse.handle(fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 107, in handle
return h['handle'](fn, data, include)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
 line 121, in handle
abs_fn = resolve_file(fn, data)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py",
 line 131, in resolve_file
raise IOError(errno.ENOENT, "file %s not found" % fn)
FileNotFoundError: [Errno 2] file 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-gnome/gnome/conf/layer.conf
 not found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 334, in 
ret = main()
  File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", 
line 321, in main
ret = args.func(args, config, basepath, workspace)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 2112, in finish
updated, appendfile, removed = _update_recipe(args.recipename, workspace, 
rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, 
no_report_remove=removing_original, initial_rev=args.initial_rev, 
dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, 
force_patch_refresh=args.force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1818, in _update_recipe
updated, appendf, removed = _update_recipe_patch(recipename, workspace, 
srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, 
initial_rev, dry_run_outdir, force_patch_refresh)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py",
 line 1675, in _update_recipe_patch
redirect_output=dry_run_outdir)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 705, in bbappend_recipe
appendpath, pathok = get_bbappend_path(rd, destlayerdir, wildcardver)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", 
line 632, in get_bbappend_path
confdata = bb.cookerdata.parse_config_file(destlayerconf, confdata)
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py",
 line 167, in wrapped
raise bb.BBHandledException()
bb.BBHandledException



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all

[OE-core] [AUH] piglit: upgrading to 0a7f9cfbb62f9d1b1ef9d22f6d9f212a89aa06f3 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to 
*0a7f9cfbb62f9d1b1ef9d22f6d9f212a89aa06f3* has Succeeded.

Next steps:
- apply the patch: git am 0001-piglit-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
packages/core2-32-poky-linux/piglit: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit: PKGV changed from 
1.0+gitrAUTOINC+d4d9353b72 [default] to 1.0+gitrAUTOINC+0a7f9cfbb6 [default]
packages/core2-32-poky-linux/piglit/piglit-bash-completion: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-dbg: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-dev: RDEPENDS: removed "piglit (['= 
1.0+gitr0+d4d9353b72-r0'])", added "piglit (['= 1.0+gitr0+0a7f9cfbb6-r0'])"
packages/core2-32-poky-linux/piglit/piglit-dev: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-doc: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-locale: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-src: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-staticdev: RDEPENDS: removed 
"piglit-dev (['= 1.0+gitr0+d4d9353b72-r0'])", added "piglit-dev (['= 
1.0+gitr0+0a7f9cfbb6-r0'])"
packages/core2-32-poky-linux/piglit/piglit-staticdev: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit: PKGSIZE changed from 2041747147 to 
2041751065 (+0%)
packages/core2-32-poky-linux/piglit/piglit: PV changed from 
"1.0+gitrAUTOINC+d4d9353b72" to "1.0+gitrAUTOINC+0a7f9cfbb6"
packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
>From 01fd87bb36894228b22dd937f8f43c8118725995 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 12:46:44 +
Subject: [PATCH] piglit: upgrade to latest revision

---
 meta/recipes-graphics/piglit/piglit_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/piglit/piglit_git.bb b/meta/recipes-graphics/piglit/piglit_git.bb
index 14f4c75a2c..03528b4390 100644
--- a/meta/recipes-graphics/piglit/piglit_git.bb
+++ b/meta/recipes-graphics/piglit/piglit_git.bb
@@ -18,7 +18,7 @@ SRC_URI = "git://gitlab.freedesktop.org/mesa/piglit.git;protocol=https \
"
 UPSTREAM_CHECK_COMMITS = "1"
 
-SRCREV = "d4d9353b7290ed22cb7349226a8e4017402d3f02"
+SRCREV = "0a7f9cfbb62f9d1b1ef9d22f6d9f212a89aa06f3"
 # (when PV goes above 1.0 remove the trailing r)
 PV = "1.0+gitr${SRCPV}"
 
-- 
2.17.1

packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 
1.0+gitr0+d4d9353b72 to 1.0+gitr0+0a7f9cfbb6
packages/core2-32-poky-linux/piglit/piglit-dev: RDEPENDS: removed "piglit (['= 
1.0+gitr0+d4d9353b72-r0'])", added "piglit (['= 1.0+gitr0+0a7f9cfbb6-r0'])"

[OE-core] [AUH] strace: upgrading to 5.11 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *strace* to *5.11* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe strace failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-d59dba4f368eccc5d279e56034ea018c19a612ba"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:d59dba4f368eccc5d279e56034ea018c19a612ba"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 22 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching https://strace.io/files/5.11/strace-5.11.tar.xz...
Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 815 .bb files complete (813 cached, 2 parsed). 1439 targets, 31 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-d59dba4f368eccc5d279e56034ea018c19a612ba"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:d59dba4f368eccc5d279e56034ea018c19a612ba"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 18 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   1% || ETA:  0:00:05
Adding changed files:   3% |#   | ETA:  0:00:04
Adding changed files:   5% |#   | ETA:  0:00:04
Adding changed files:   6% |##  | ETA:  0:00:03
Adding changed files:   8% |### | ETA:  0:00:03
Adding changed files:  10% |### | ETA:  0:00:03
Adding changed files:  11% || ETA:  0:00:02
Adding changed files:  13% || ETA:  0:00:03
Adding changed files:  15% |#   | ETA:  0:00:02
Adding changed files:  16% |##  | ETA:  0:00:02
Adding changed files:  18% |##  | ETA:  0:00:02
Adding changed files:  20% |### | ETA:  0:00:02
Adding changed files:  22% |### | ETA:  0:00:02
Adding changed files:  23% || ETA:  0:00:02
Adding changed files:  25% |#   | ETA:  0:00:02
Adding changed files:  27% |#   | ETA:  0:00:02
Adding changed files:  28% |##  | ETA:  0:00:02
Adding changed files:  30% |##  | ETA:  0:00:02
Adding changed files:  32% |### | ETA:  0:00:02
Adding changed files:  33% || ETA:  0:00:02
Adding changed files:  35% || ETA:  0:00:02
Adding changed files:  37% |#   | ETA:  0:00:01
Adding changed files:  38% |##  | ETA:  0:00:01
Adding changed files:  40% |##  | ETA:  0:00:01
Adding changed files:  42% |### | ETA:  0:00:01
Adding changed files:  44% |### | ETA:  0:00:01
Adding changed

[OE-core] [AUH] vulkan-headers: upgrading to 1.2.170.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-headers* to 
*1.2.170.0* has Succeeded.

Next steps:
- apply the patch: git am 
0001-vulkan-headers-upgrade-1.2.162.0-1.2.170.0.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/vulkan-headers: PV changed from "1.2.162.0" to 
"1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers: PKGV changed from 1.2.162.0 
[default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dbg: PV changed from 
"1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dbg: PKGV changed 
from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dev: PV changed from 
"1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dev: PKGSIZE changed 
from 5230965 to 5378238 (+3%)
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dev: PKGV changed 
from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-doc: PV changed from 
"1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-doc: PKGV changed 
from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-locale: PV changed 
from "1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-locale: PKGV changed 
from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-src: PV changed from 
"1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-src: PKGV changed 
from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-staticdev: PV 
changed from "1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-staticdev: PKGV 
changed from 1.2.162.0 [default] to 1.2.170.0 [default]
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers: PV changed from 
"1.2.162.0" to "1.2.170.0"
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers: PKGSIZE changed 
from 4384952 to 4673787 (+7%)
packages/core2-32-poky-linux/vulkan-headers/vulkan-headers: PKGV changed from 
1.2.162.0 [default] to 1.2.170.0 [default]
>From 3750245d058a20a8a09b9ee2cf9267548f7bf791 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 12:53:07 +
Subject: [PATCH] vulkan-headers: upgrade 1.2.162.0 -> 1.2.170.0

---
 ...{vulkan-headers_1.2.162.0.bb => vulkan-headers_1.2.170.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/vulkan/{vulkan-headers_1.2.162.0.bb => vulkan-headers_1.2.170.0.bb} (93%)

diff --git a/meta/recipes-graphics/vulkan/vulkan-headers_1.2.162.0.bb b/meta/recipes-graphics/vulkan/vulkan-headers_1.2.170.0.bb
similarity index 93%
rename from meta/recipes-graphics/vulkan/vulkan-headers_1.2.162.0.bb
rename to meta/recipes-graphics/vulkan/vulkan-headers_1.2.170.0.bb
index 19ae67cdd4..4c9c94f3d2 100644
--- a/meta/recipes-graphics/vulkan/vulkan-headers_1.2.162.0.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-headers_1.2.170.0.bb
@@ -11,7 +11,7 @@ LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
 SRC_URI = "git://github.com/KhronosGroup/Vulkan-Headers.git;branch=master"
 
-SRCREV = "87aaa16d4c8e1ac70f8f04acdcd46eed4bd77209"
+SRCREV = "1d99b835ec3cd5a7fb2f2a2dd9a615ee2d1f0101"
 
 S = "${WORKDIR}/git"
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149512): 
https://lists.openembedded.org/g/openembedded-core/message/149512
Mute This Topic: https://lists.openembedded.org/mt/81354125/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] vulkan-loader: upgrading to 1.2.170.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-loader* to *1.2.170.0* 
has Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 
0001-vulkan-loader-upgrade-1.2.162.0-1.2.170.0.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
>From a841f9009003f369f763d9fa32cfbdf2c00f3e6e Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 12:54:24 +
Subject: [PATCH] vulkan-loader: upgrade 1.2.162.0 -> 1.2.170.0

---
 ...name-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch | 40 ---
 2.162.0.bb => vulkan-loader_1.2.170.0.bb} |  6 +--
 2 files changed, 2 insertions(+), 44 deletions(-)
 delete mode 100644 meta/recipes-graphics/vulkan/vulkan-loader/0001-Rename-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch
 rename meta/recipes-graphics/vulkan/{vulkan-loader_1.2.162.0.bb => vulkan-loader_1.2.170.0.bb} (87%)

diff --git a/meta/recipes-graphics/vulkan/vulkan-loader/0001-Rename-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch b/meta/recipes-graphics/vulkan/vulkan-loader/0001-Rename-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch
deleted file mode 100644
index 26b1a40f26..00
--- a/meta/recipes-graphics/vulkan/vulkan-loader/0001-Rename-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From 5ae24ece75f2caa69216da7075334711642f5588 Mon Sep 17 00:00:00 2001
-From: Michel Zou 
-Date: Wed, 16 Dec 2020 15:03:23 +0100
-Subject: [PATCH] Rename LIB_SUFFIX to VULKAN_LIB_SUFFIX
-
-Closes #527
-
-Upstream-Status: Backport [https://github.com/KhronosGroup/Vulkan-Loader/commit/66a23ac8c566299343668f094de50798a5f4a0e4]
-Signed-off-by: Alexander Kanavin 

- loader/CMakeLists.txt | 2 +-
- loader/vulkan.pc.in   | 2 +-
- 2 files changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/loader/CMakeLists.txt b/loader/CMakeLists.txt
-index 659511855..ba9f460f1 100644
 a/loader/CMakeLists.txt
-+++ b/loader/CMakeLists.txt
-@@ -327,7 +327,7 @@ if(PKG_CONFIG_FOUND)
- set(PRIVATE_LIBS "${PRIVATE_LIBS} -l${LIB}")
- endforeach()
- if(WIN32)
--set(LIB_SUFFIX "-1")
-+set(VULKAN_LIB_SUFFIX "-1")
- endif ()
- configure_file("vulkan.pc.in" "vulkan.pc" @ONLY)
- install(FILES "${CMAKE_CURRENT_BINARY_DIR}/vulkan.pc" DESTINATION "${CMAKE_INSTALL_LIBDIR}/pkgconfig")
-diff --git a/loader/vulkan.pc.in b/loader/vulkan.pc.in
-index fc17cb1f3..44049ee34 100644
 a/loader/vulkan.pc.in
-+++ b/loader/vulkan.pc.in
-@@ -6,7 +6,7 @@ includedir=@CMAKE_INSTALL_FULL_INCLUDEDIR@
- Name: @CMAKE_PROJECT_NAME@
- Description: Vulkan Loader
- Version: @VK_API_VERSION@
--Libs: -L${libdir} -lvulkan@LIB_SUFFIX@
-+Libs: -L${libdir} -lvulkan@VULKAN_LIB_SUFFIX@
- Libs.private: @PRIVATE_LIBS@
- Cflags: -I${includedir}
- 
diff --git a/meta/recipes-graphics/vulkan/vulkan-loader_1.2.162.0.bb b/meta/recipes-graphics/vulkan/vulkan-loader_1.2.170.0.bb
similarity index 87%
rename from meta/recipes-graphics/vulkan/vulkan-loader_1.2.162.0.bb
rename to meta/recipes-graphics/vulkan/vulkan-loader_1.2.170.0.bb
index d39e7af975..492651c86b 100644
--- a/meta/recipes-graphics/vulkan/vulkan-loader_1.2.162.0.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-loader_1.2.170.0.bb
@@ -9,10 +9,8 @@ SECTION = "libs"
 
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=7dbefed23242760aa3475ee42801c5ac"
-SRC_URI = "git://github.com/KhronosGroup/Vulkan-Loader.git \
-   file://0001-Rename-LIB_SUFFIX-to-VULKAN_LIB_SUFFIX.patch \
-   "
-SRCREV = "7a313093b5c4af964d50a5a64e73d7df6152ea3f"
+SRC_URI = "git://github.com/KhronosGroup/Vulkan-Loader.git"
+SRCREV = "c5678a03db383fd0dc5bfb8e9a383043bdbcb57b"
 
 S = "${WORKDIR}/git"
 
-- 
2.17.1

Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 814 .bb files complete (813 cached, 1 parsed). 1438 targets, 31 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"

[OE-core] [AUH] attr: upgrading to 2.5.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *attr* to *2.5.0* has Failed 
(devtool error).

Detailed error information:

The following devtool command failed:  upgrade attr -V 2.5.0
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-382355db0b322e8aef7d64ee3d5bf198db6fa2f0"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:382355db0b322e8aef7d64ee3d5bf198db6fa2f0"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 3 Local 0 Network 0 Missed 3 Current 17 (0% match, 85% 
complete)
NOTE: Executing Tasks
ERROR: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:devtool_post_unpack(d)
 0003:
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/meta/classes/devtool-source.bbclass',
 lineno: 150, function: devtool_post_unpack
 0146:"doesn't use any source or the correct source "
 0147:"directory could not be determined" % d.getVar('PN'))
 0148:
 0149:devbranch = d.getVar('DEVTOOL_DEVBRANCH')
 *** 0150:setup_git_repo(srcsubdir, d.getVar('PV'), devbranch, d=d)
 0151:
 0152:(stdout, _) = bb.process.run('git rev-parse HEAD', cwd=srcsubdir)
 0153:initial_rev = stdout.rstrip()
 0154:with open(os.path.join(tempdir, 'initial_rev'), 'w') as f:
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/__init__.py',
 lineno: 233, function: setup_git_repo
 0229:with open(excludefile, 'w') as f:
 0230:for line in excludes:
 0231:f.write(line)
 0232:
 *** 0233:bb.process.run('git checkout -b %s' % devbranch, cwd=repodir)
 0234:bb.process.run('git tag -f %s' % basetag, cwd=repodir)
 0235:
 0236:def recipe_to_append(recipefile, config, wildcard=False):
 0237:"""
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/process.py', 
lineno: 184, function: run
 0180:if not stderr is None:
 0181:stderr = stderr.decode("utf-8")
 0182:
 0183:if pipe.returncode != 0:
 *** 0184:raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
 0185:return stdout, stderr
Exception: bb.process.ExecutionError: Execution of 'git checkout -b 
devtool-orig' failed with exit code 128:
fatal: not a git repository (or any of the parent directories): .git


ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/attr/2.4.48-r0/devtooltmp-mtduh9qp/temp/log.do_unpack.37152
NOTE: Tasks Summary: Attempted 81 tasks of which 76 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
ERROR: Extracting source for attr failed



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149520): 
https://lists.openembedded.org/g/openembedded-core/message/149520
Mute This Topic: https://lists.openembedded.org/mt/81354133/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] epiphany: upgrading to 3.38.3 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *epiphany* to *3.38.3* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-epiphany-upgrade-3.38.2-3.38.3.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/epiphany/epiphany-dbg: PKGSIZE changed from 
4213512 to 4213992 (+0%)
packages/core2-32-poky-linux/epiphany/epiphany-dbg: PV changed from "3.38.2" to 
"3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-dbg: PKGV changed from 3.38.2 
[default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-dev: PV changed from "3.38.2" to 
"3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-dev: PKGV changed from 3.38.2 
[default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-doc: PV changed from "3.38.2" to 
"3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-doc: PKGV changed from 3.38.2 
[default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-af: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-af: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-am: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-am: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-an: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-an: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-ar: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-ar: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-as: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-as: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-ast: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-ast: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-az: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-az: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-be+latin: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-be+latin: PKGV changed 
from 3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-be: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-be: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-bg: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-bg: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-bn-in: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-bn-in: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-bn: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-bn: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-br: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-br: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-bs: PV changed from 
"3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-bs: PKGV changed from 
3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-ca+valencia: PV changed 
from "3.38.2" to "3.38.3"
packages/core2-32-poky-linux/epiphany/epiphany-locale-ca+valencia: PKGV changed 
from 3.38.2 [default] to 3.38.3 [default]
packages/core2-32-poky-linux/epiphany/epiphany-locale-ca: PV changed from 
"3.38.2" to "3.38.3"

[OE-core] [AUH] vulkan-samples: upgrading to 9776715b96b14705579c505f586cb2427b272ca6 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to 
*9776715b96b14705579c505f586cb2427b272ca6* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade vulkan-samples -S 
9776715b96b14705579c505f586cb2427b272ca6
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-3448ddf0362ea1f5e5689eca51bda51080b628da"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:3448ddf0362ea1f5e5689eca51bda51080b628da"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
ERROR: Command Error: 'sh -c 
'PATCHFILE="0001-CMakeLists.txt-do-not-hardcode-lib-as-installation-t.patch" 
git -c user.name="OpenEmbedded" -c user.email="oe.patch@oe" commit -F 
/tmp/tmpevk8lx24 --author="Alexander Kanavin " 
--date="Sun, 1 Nov 2020 23:19:22 +"'' exited with 0  Output:
stdout: On branch devtool-orig
Changes not staged for commit:
modified:   third_party/spirv-cross (modified content)

no changes added to commit

stderr: 
ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/vulkan-samples/git-r0/devtooltmp-2z8i4ml1/temp/log.do_patch.28777
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
ERROR: Extracting source for vulkan-samples failed



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149513): 
https://lists.openembedded.org/g/openembedded-core/message/149513
Mute This Topic: https://lists.openembedded.org/mt/81354126/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] less: upgrading to 580 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *less* to *580* has Succeeded.

Next steps:
- apply the patch: git am 0001-less-upgrade-563-580.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/less: PV changed from "563" to "580"
packages/core2-32-poky-linux/less: PKGV changed from 563 [default] to 580 
[default]
packages/core2-32-poky-linux/less: SRC_URI changed from 
"http://www.greenwoodsoftware.com/less/less-563.tar.gz; to 
"http://www.greenwoodsoftware.com/less/less-580.tar.gz;
packages/core2-32-poky-linux/less/less-dbg: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-dbg: PKGV changed from 563 [default] to 
580 [default]
packages/core2-32-poky-linux/less/less-dbg: PKGSIZE changed from 473888 to 
495596 (+5%)
packages/core2-32-poky-linux/less/less-dev: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-dev: PKGV changed from 563 [default] to 
580 [default]
packages/core2-32-poky-linux/less/less-doc: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-doc: PKGV changed from 563 [default] to 
580 [default]
packages/core2-32-poky-linux/less/less-doc: PKGSIZE changed from 81648 to 86068 
(+5%)
packages/core2-32-poky-linux/less/less-locale: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-locale: PKGV changed from 563 [default] 
to 580 [default]
packages/core2-32-poky-linux/less/less-src: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-src: PKGV changed from 563 [default] to 
580 [default]
packages/core2-32-poky-linux/less/less-src: PKGSIZE changed from 628556 to 
668068 (+6%)
packages/core2-32-poky-linux/less/less-staticdev: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less-staticdev: PKGV changed from 563 
[default] to 580 [default]
packages/core2-32-poky-linux/less/less: PV changed from "563" to "580"
packages/core2-32-poky-linux/less/less: PKGV changed from 563 [default] to 580 
[default]
packages/core2-32-poky-linux/less/less: PKGSIZE changed from 234048 to 242696 
(+4%)
>From d565ef720dbb64874d917117d0c06eb2cf0b4028 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:44:54 +
Subject: [PATCH] less: upgrade 563 -> 580

---
 meta/recipes-extended/less/{less_563.bb => less_580.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/less/{less_563.bb => less_580.bb} (93%)

diff --git a/meta/recipes-extended/less/less_563.bb b/meta/recipes-extended/less/less_580.bb
similarity index 93%
rename from meta/recipes-extended/less/less_563.bb
rename to meta/recipes-extended/less/less_580.bb
index 123522b5dc..7181347695 100644
--- a/meta/recipes-extended/less/less_563.bb
+++ b/meta/recipes-extended/less/less_580.bb
@@ -28,7 +28,7 @@ DEPENDS = "ncurses"
 SRC_URI = "http://www.greenwoodsoftware.com/${BPN}/${BPN}-${PV}.tar.gz \
 	  "
 
-SRC_URI[sha256sum] = "ce5b6d2b9fc4442d7a07c93ab128d2dff2ce09a1d4f2d055b95cf28dd0dc9a9a"
+SRC_URI[sha256sum] = "5b5c606e3de2e8d93929342c89e71861a4a6766210f65e1c05a75f8cf62fa287"
 
 UPSTREAM_CHECK_URI = "http://www.greenwoodsoftware.com/less/download.html;
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149505): 
https://lists.openembedded.org/g/openembedded-core/message/149505
Mute This Topic: https://lists.openembedded.org/mt/81354118/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] gdk-pixbuf: upgrading to 2.42.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gdk-pixbuf* to *2.42.2* has 
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe gdk-pixbuf failed.
NOTE: Starting bitbake server...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches 
to represent these
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-cb6cb0f26ced9b9297a66c1584e426a4c5faee09"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:cb6cb0f26ced9b9297a66c1584e426a4c5faee09"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 22 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://ftp.gnome.org/pub/GNOME/sources/gdk-pixbuf/2.42/gdk-pixbuf-2.42.2.tar.xz...
Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 815 .bb files complete (813 cached, 2 parsed). 1439 targets, 31 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-cb6cb0f26ced9b9297a66c1584e426a4c5faee09"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:cb6cb0f26ced9b9297a66c1584e426a4c5faee09"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 18 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files: 100% || Time: 0:00:00
WARNING: Command 'git rebase 6150413d90398b738340a94ca9108a3a03ffa176' failed:
First, rewinding head to replay your work on top of it...
Applying: gdk-pixbuf: add an option so that loader errors are fatal
Applying: Work-around thumbnailer cross-compile failure
Applying: Generate loaders.cache using a native tool when cross-compiling
Applying: Do not run tests when building
Using index info to reconstruct a base tree...
M   tests/meson.build
Falling back to patching base and 3-way merge...
Auto-merging tests/meson.build
CONFLICT (content): Merge conflict in tests/meson.build
error: Failed to merge in the changes.
Patch failed at 0004 Do not run tests when building
Use 'git am --show-current-patch' to see the failed patch

Resolve all conflicts manually, mark them as resolved with
"git add/rm ", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase 
--abort".

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/gdk-pixbuf
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/gdk-pixbuf/gdk-pixbuf_2.42.2.bb




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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149508): 
https://lists.openembedded.org/g/openembedded-core/message/149508
Mute This Topic: https://lists.openembedded.org/mt/81354121/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub

[OE-core] [AUH] mesa: upgrading to 21.0.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mesa* to *21.0.0* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe mesa failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-c593a17477c3c4a50600195b3c6fd8098add2ce7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:c593a17477c3c4a50600195b3c6fd8098add2ce7"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 22 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Extracting upgraded version source...
INFO: Fetching https://mesa.freedesktop.org/archive/mesa-21.0.0.tar.xz...
Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 815 .bb files complete (813 cached, 2 parsed). 1439 targets, 31 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-c593a17477c3c4a50600195b3c6fd8098add2ce7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:c593a17477c3c4a50600195b3c6fd8098add2ce7"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 18 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   5% |#   | ETA:  0:00:02
Adding changed files:  10% |### | ETA:  0:00:02
Adding changed files:  16% |#   | ETA:  0:00:01
Adding changed files:  21% |### | ETA:  0:00:01
Adding changed files:  27% |#   | ETA:  0:00:01
Adding changed files:  32% |### | ETA:  0:00:01
Adding changed files:  38% |#   | ETA:  0:00:01
Adding changed files:  43% |### | ETA:  0:00:01
Adding changed files:  49% |#   | ETA:  0:00:00
Adding changed files:  54% |### | ETA:  0:00:00
Adding changed files:  60% |#   | ETA:  0:00:00
Adding changed files:  65% |### | ETA:  0:00:00
Adding changed files:  71% |#   | ETA:  0:00:00
Adding changed files:  76% |### | ETA:  0:00:00
Adding changed files:  82% |#   | ETA:  0:00:00
Adding changed files:  87% |### | ETA:  0:00:00
Adding changed files:  93% |#   | ETA:  0:00:00
Adding changed files:  98% |### | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:01
WARNING: Command 'git rebase 2f3211ac5dffc5e3d66806e2c503dd3b4a7b01e1' failed:
First, rewinding head to replay your work on top of it...
Applying: meson.build: check for all linux host_os combinations
Using index info to reconstruct a base tree...
M   meson.build
Falling back to patching base and 3-way merge...
Auto-merging meson.build
CONFLICT (content): Merge conflict in meson.build
error: Failed to merge in the changes.
Patch failed at 0001 meson.build: check for all linux host_os combinations
Use 'git am --show-current-patch' to see the failed patch

Resolve all conflicts manually, mark them as resolved

[OE-core] [AUH] python3-importlib-metadata: upgrading to 3.7.3 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-importlib-metadata* 
to *3.7.3* has Succeeded.

Next steps:
- apply the patch: git am 
0001-python3-importlib-metadata-upgrade-3.4.0-3.7.3.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/python3-importlib-metadata: PV changed from 
"3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata: PKGV changed from 
3.4.0 [default] to 3.7.3 [default]
packages/core2-32-poky-linux/python3-importlib-metadata: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/i/importlib_metadata/importlib_metadata-3.4.0.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/i/importlib_metadata/importlib_metadata-3.7.3.tar.gz;
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dbg:
 FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/importlib_metadata-3.4.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/importlib_metadata-3.7.3-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/importlib_metadata/_itertools.py 
/usr/lib/python3.9/site-packages/importlib_metadata/__pycache__/_itertools.cpython-39.pyc"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dbg:
 PV changed from "3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dbg:
 PKGV changed from 3.4.0 [default] to 3.7.3 [default]
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dev:
 FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/importlib_metadata-3.4.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/importlib_metadata-3.7.3-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/importlib_metadata/_itertools.py 
/usr/lib/python3.9/site-packages/importlib_metadata/__pycache__/_itertools.cpython-39.pyc"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dev:
 PV changed from "3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-dev:
 PKGV changed from 3.4.0 [default] to 3.7.3 [default]
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-doc:
 FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/importlib_metadata-3.4.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/importlib_metadata-3.7.3-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/importlib_metadata/_itertools.py 
/usr/lib/python3.9/site-packages/importlib_metadata/__pycache__/_itertools.cpython-39.pyc"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-doc:
 PV changed from "3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-doc:
 PKGV changed from 3.4.0 [default] to 3.7.3 [default]
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-locale:
 FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/importlib_metadata-3.4.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/importlib_metadata-3.7.3-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/importlib_metadata/_itertools.py 
/usr/lib/python3.9/site-packages/importlib_metadata/__pycache__/_itertools.cpython-39.pyc"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-locale:
 PV changed from "3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-locale:
 PKGV changed from 3.4.0 [default] to 3.7.3 [default]
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-src:
 FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/importlib_metadata-3.4.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/importlib_metadata-3.7.3-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/importlib_metadata/_itertools.py 
/usr/lib/python3.9/site-packages/importlib_metadata/__pycache__/_itertools.cpython-39.pyc"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-src:
 PV changed from "3.4.0" to "3.7.3"
packages/core2-32-poky-linux/python3-importlib-metadata/python3-importlib-metadata-src:
 PKGV changed from 3.4.0 [default] to 3.7.3

[OE-core] [AUH] liburi-perl: upgrading to 5.08 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *liburi-perl* to *5.08* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-liburi-perl-upgrade-1.74-5.08.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
>From c5386a59167e869725f72ade077a6665e232a3a9 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:11:56 +
Subject: [PATCH] liburi-perl: upgrade 1.74 -> 5.08

---
 .../perl/{liburi-perl_1.74.bb => liburi-perl_5.08.bb}  | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-devtools/perl/{liburi-perl_1.74.bb => liburi-perl_5.08.bb} (90%)

diff --git a/meta/recipes-devtools/perl/liburi-perl_1.74.bb b/meta/recipes-devtools/perl/liburi-perl_5.08.bb
similarity index 90%
rename from meta/recipes-devtools/perl/liburi-perl_1.74.bb
rename to meta/recipes-devtools/perl/liburi-perl_5.08.bb
index c27765bcbc..06509df5eb 100644
--- a/meta/recipes-devtools/perl/liburi-perl_1.74.bb
+++ b/meta/recipes-devtools/perl/liburi-perl_5.08.bb
@@ -13,8 +13,7 @@ DEPENDS += "perl"
 
 SRC_URI = "http://www.cpan.org/authors/id/E/ET/ETHER/URI-${PV}.tar.gz;
 
-SRC_URI[md5sum] = "892f7183b178af40f205ba37128225db"
-SRC_URI[sha256sum] = "a9c254f45f89cb1dd946b689dfe433095404532a4543bdaab0b71ce0fdcdd53d"
+SRC_URI[sha256sum] = "7e2c6fe3b1d5947da334fa558a96e748aaa619213b85bcdce5b5347d4d26c46e"
 
 S = "${WORKDIR}/URI-${PV}"
 
-- 
2.17.1

packages/core2-32-poky-linux/liburi-perl: PKGV changed from 1.74 [default] to 
5.08 [default]
packages/core2-32-poky-linux/liburi-perl: SRC_URI changed from 
"http://www.cpan.org/authors/id/E/ET/ETHER/URI-1.74.tar.gz 
file://ptest-perl/run-ptest" to 
"http://www.cpan.org/authors/id/E/ET/ETHER/URI-5.08.tar.gz 
file://ptest-perl/run-ptest"
packages/core2-32-poky-linux/liburi-perl: PV changed from "1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dbg: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dbg: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dbg: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dev: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dev: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-dev: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-doc: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-doc: PKGSIZE changed from 
97358 to 97589 (+0%)
packages/core2-32-poky-linux/liburi-perl/liburi-perl-doc: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-doc: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-locale: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-locale: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-locale: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-ptest: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-ptest: PKGSIZE changed 
from 124887 to 125418 (+0%)
packages/core2-32-poky-linux/liburi-perl/liburi-perl-ptest: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-ptest: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-src: PKGV changed from 
1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-src: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-src: PV changed from 
"1.74" to "5.08"
packages/core2-32-poky-linux/liburi-perl/liburi-perl-staticdev: PKGV changed 
from 1.74 [default] to 5.08 [default]
packages/core2-32-poky-linux/liburi-perl/liburi-perl-staticdev: FILELIST: added 
"/usr/lib/perl5/vendor_perl/5.32.1/URI/nntps.pm"

[OE-core] [AUH] stress-ng: upgrading to 0.12.05 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.12.05* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.12.04-0.12.05.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/stress-ng: SRC_URI changed from 
"https://kernel.ubuntu.com/~cking/tarballs/stress-ng/stress-ng-0.12.04.tar.xz 
file://0001-Do-not-preserve-ownership-when-installing-example-jo.patch 
file://no_daddr_t.patch" to 
"https://kernel.ubuntu.com/~cking/tarballs/stress-ng/stress-ng-0.12.05.tar.xz 
file://0001-Do-not-preserve-ownership-when-installing-example-jo.patch 
file://no_daddr_t.patch"
packages/core2-32-poky-linux/stress-ng: PV changed from "0.12.04" to "0.12.05"
packages/core2-32-poky-linux/stress-ng: PKGV changed from 0.12.04 [default] to 
0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-bash-completion: PV changed 
from "0.12.04" to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-bash-completion: PKGV changed 
from 0.12.04 [default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-dbg: PV changed from "0.12.04" 
to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-dbg: PKGV changed from 0.12.04 
[default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-dbg: PKGSIZE changed from 
5816824 to 5839508 (+0%)
packages/core2-32-poky-linux/stress-ng/stress-ng-dev: PV changed from "0.12.04" 
to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-dev: PKGV changed from 0.12.04 
[default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-doc: PV changed from "0.12.04" 
to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-doc: PKGV changed from 0.12.04 
[default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-doc: PKGSIZE changed from 
51062 to 51286 (+0%)
packages/core2-32-poky-linux/stress-ng/stress-ng-locale: PV changed from 
"0.12.04" to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-locale: PKGV changed from 
0.12.04 [default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-src: PV changed from "0.12.04" 
to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-src: PKGV changed from 0.12.04 
[default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng-src: PKGSIZE changed from 
2896769 to 2910603 (+0%)
packages/core2-32-poky-linux/stress-ng/stress-ng-staticdev: PV changed from 
"0.12.04" to "0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng-staticdev: PKGV changed from 
0.12.04 [default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng: PV changed from "0.12.04" to 
"0.12.05"
packages/core2-32-poky-linux/stress-ng/stress-ng: PKGV changed from 0.12.04 
[default] to 0.12.05 [default]
packages/core2-32-poky-linux/stress-ng/stress-ng: PKGSIZE changed from 4139304 
to 4143464 (+0%)
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1438 targets, 49 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the armv7vet2hf-neon sysroot...done.
Removing 1 recipes from the qemuarm sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "qemuarm"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-6a855e2c5a84c839f1e4965290ac9fd27358e53d"
TUNE_FEATURES= "arm armv7ve vfp thumb neon callconvention-hard"
TARGET_FPU   = "hard"
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:6a855e2c5a84c839f1e4965290ac9fd27358e53d"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 30 Local 19 Network 0 Missed 11 Current 640 (63% match, 
98% complete)
NOTE: Executing Tasks
NOTE: Running setscene task 657 of 670 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-extended/procps/procps_3.3.16.bb:do_package_write_rpm_setscene)
NOTE: recipe procps-3.3.16-r0: task

[OE-core] [AUH] asciidoc: upgrading to 9.1.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *asciidoc* to *9.1.0* has
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe asciidoc failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.2+snapshot-d59dba4f368eccc5d279e56034ea018c19a612ba"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:d59dba4f368eccc5d279e56034ea018c19a612ba"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0% match, 100%
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Extracting upgraded version source...
WARNING: Command 'git rebase 9705d428439530104ce55d0ba12e8ef9d1b57ad1' failed:
First, rewinding head to replay your work on top of it...
Applying: asciidoc: specify XML catalogue to use
Using index info to reconstruct a base tree...
M a2x.py
Falling back to patching base and 3-way merge...
Auto-merging a2x.py
CONFLICT (content): Merge conflict in a2x.py
error: Failed to merge in the changes.
Patch failed at 0001 asciidoc: specify XML catalogue to use
Use 'git am --show-current-patch' to see the failed patch

Resolve all conflicts manually, mark them as resolved with
"git add/rm ", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase
--abort".

You will need to resolve conflicts in order to complete the upgrade.
INFO: Using source tree as build directory since recipe inherits
autotools-brokensep
INFO: Upgraded source extracted to
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/asciidoc
INFO: New recipe is
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/asciidoc/asciidoc_9.1.0.bb

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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149496):
https://lists.openembedded.org/g/openembedded-core/message/149496
Mute This Topic: https://lists.openembedded.org/mt/81354109/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] msmtp: upgrading to 1.8.15 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *msmtp* to *1.8.15* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-msmtp-upgrade-1.8.14-1.8.15.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/msmtp: PKGV changed from 1.8.14 [default] to 
1.8.15 [default]
packages/core2-32-poky-linux/msmtp: PV changed from "1.8.14" to "1.8.15"
packages/core2-32-poky-linux/msmtp: SRC_URI changed from 
"https://marlam.de/msmtp/releases/msmtp-1.8.14.tar.xz; to 
"https://marlam.de/msmtp/releases/msmtp-1.8.15.tar.xz;
packages/core2-32-poky-linux/msmtp/msmtp-dbg: PKGSIZE changed from 299168 to 
300836 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-dbg: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-dbg: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-dev: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-dev: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-doc: PKGSIZE changed from 101192 to 
101427 (+0%)
packages/core2-32-poky-linux/msmtp/msmtp-doc: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-doc: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-de: PKGSIZE changed from 35796 
to 36269 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-de: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-de: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-eo: PKGSIZE changed from 33850 
to 34281 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-eo: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-eo: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-fr: PKGSIZE changed from 36560 
to 36998 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-fr: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-fr: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-pt-br: PKGSIZE changed from 
36422 to 36879 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-pt-br: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-pt-br: PV changed from "1.8.14" 
to "1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-sr: PKGSIZE changed from 44228 
to 44726 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-sr: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-sr: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-ta: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-ta: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-locale-uk: PKGSIZE changed from 45915 
to 46504 (+1%)
packages/core2-32-poky-linux/msmtp/msmtp-locale-uk: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-locale-uk: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-src: PKGSIZE changed from 477631 to 
479797 (+0%)
packages/core2-32-poky-linux/msmtp/msmtp-src: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-src: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp-staticdev: PKGV changed from 1.8.14 
[default] to 1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp-staticdev: PV changed from "1.8.14" to 
"1.8.15"
packages/core2-32-poky-linux/msmtp/msmtp: PKGV changed from 1.8.14 [default] to 
1.8.15 [default]
packages/core2-32-poky-linux/msmtp/msmtp: PV changed from "1.8.14" to "1.8.15"
>From a69ab8f917b68218192a059404579d572aeedfdc Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:49:34 +
Subject: [PATCH] msmtp: upgrade 1.8.14 -> 1.8.15

---
 .../recipes-extended/msmtp/{msmtp_1.8.14.bb => msmtp_1.8.15.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename

[OE-core] [AUH] gtk+3: upgrading to 3.24.27 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.27* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-gtk-3-upgrade-3.24.25-3.24.27.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/gtk+3/gtk+3-dbg: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-dbg: PKGSIZE changed from 23643040 to 
23646940 (+0%)
packages/core2-32-poky-linux/gtk+3/gtk+3-dbg: PV changed from "3.24.25" to 
"3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-demo: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-demo: PV changed from "3.24.25" to 
"3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-dev: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-dev: PKGSIZE changed from 14325530 to 
14325546 (+0%)
packages/core2-32-poky-linux/gtk+3/gtk+3-dev: PV changed from "3.24.25" to 
"3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-doc: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-doc: PV changed from "3.24.25" to 
"3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-af: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-af: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-am: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-am: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-an: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-an: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ang: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ang: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ar: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ar: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-as: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-as: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ast: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-ast: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-az-ir: PKGV changed from 
3.24.25 [default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-az-ir: PV changed from 
"3.24.25" to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-az: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-az: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-be+latin: PKGV changed from 
3.24.25 [default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-be+latin: PV changed from 
"3.24.25" to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-be: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-be: PKGSIZE changed from 398853 
to 399093 (+0%)
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-be: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bg: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bg: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bn-in: PKGV changed from 
3.24.25 [default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bn-in: PV changed from 
"3.24.25" to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bn: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-bn: PV changed from "3.24.25" 
to "3.24.27"
packages/core2-32-poky-linux/gtk+3/gtk+3-locale-br: PKGV changed from 3.24.25 
[default] to 3.24.27 [default]

[OE-core] [AUH] zstd: upgrading to 1.4.9 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *zstd* to *1.4.9* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-zstd-upgrade-1.4.8-1.4.9.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/zstd: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd: PKGV changed from 1.4.8 [default] to 1.4.9 
[default]
Changes to packages/core2-32-poky-linux/zstd (sysroot):
  /usr/lib/libzstd.so.1 changed symlink target from libzstd.so.1.4.8 to 
libzstd.so.1.4.9
  /usr/lib/libzstd.so changed symlink target from libzstd.so.1.4.8 to 
libzstd.so.1.4.9
  /usr/lib/libzstd.so.1.4.8 moved to /usr/lib/libzstd.so.1.4.9
packages/core2-32-poky-linux/zstd/zstd-dbg: PKGSIZE changed from 12087232 to 
12421032 (+3%)
packages/core2-32-poky-linux/zstd/zstd-dbg: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd/zstd-dbg: PKGV changed from 1.4.8 [default] 
to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-dbg: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd-dev: PKGSIZE changed from 161044 to 
163579 (+2%)
packages/core2-32-poky-linux/zstd/zstd-dev: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd/zstd-dev: PKGV changed from 1.4.8 [default] 
to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-dev: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd-doc: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd/zstd-doc: PKGV changed from 1.4.8 [default] 
to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-doc: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd-locale: PV changed from "1.4.8" to 
"1.4.9"
packages/core2-32-poky-linux/zstd/zstd-locale: PKGV changed from 1.4.8 
[default] to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-locale: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd-src: PKGSIZE changed from 2552959 to 
2588703 (+1%)
packages/core2-32-poky-linux/zstd/zstd-src: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd/zstd-src: PKGV changed from 1.4.8 [default] 
to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-src: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd-staticdev: PKGSIZE changed from 5018098 
to 5019710 (+0%)
packages/core2-32-poky-linux/zstd/zstd-staticdev: PV changed from "1.4.8" to 
"1.4.9"
packages/core2-32-poky-linux/zstd/zstd-staticdev: PKGV changed from 1.4.8 
[default] to 1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd-staticdev: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
packages/core2-32-poky-linux/zstd/zstd: PKGSIZE changed from 1776335 to 1796815 
(+1%)
packages/core2-32-poky-linux/zstd/zstd: PV changed from "1.4.8" to "1.4.9"
packages/core2-32-poky-linux/zstd/zstd: PKGV changed from 1.4.8 [default] to 
1.4.9 [default]
packages/core2-32-poky-linux/zstd/zstd: FILELIST: removed 
"/usr/lib/libzstd.so.1.4.8", added "/usr/lib/libzstd.so.1.4.9"
>From 9bb433c915c72b9528b05bd8a6b15c9ccece6831 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 07:24:13 +
Subject: [PATCH] zstd: upgrade 1.4.8 -> 1.4.9

---
 ...rt-all-wildcard-file-list-expansions.patch | 19 ++-
 .../zstd/{zstd_1.4.8.bb => zstd_1.4.9.bb} |  2 +-
 2 files changed, 11 insertions(+), 10 deletions(-)
 rename meta/recipes-extended/zstd/{zstd_1.4.8.bb => zstd_1.4.9.bb} (95%)

diff --git a/meta/recipes-extended/zstd/zstd/0001-Makefile-sort-all-wildcard-file-list-expansions.patch b/meta/recipes-extended/zstd/zstd/0001-Makefile-sort-all-wildcard-file-list-expansions.patch
index 178124a2ef..cd0835cdbe 100644
--- a/meta/recipes-extended/zstd/zstd/0001-Makefile-sort-all-wildcard-file-list-expansions.patch
+++ b/meta/recipes-extended/zstd/zstd/0001-Makefile-sort-all-wildcard-file-list-expansions.patch
@@ -1,4 +1,4 @@
-From 8d01b0753162681dcdbb7cf56f1e393c261e3eb0 Mon Sep 17 00:00:00 2001
+From

[OE-core] [AUH] sudo: upgrading to 1.9.6 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sudo* to *1.9.6* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-sudo-upgrade-1.9.5p2-1.9.6.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/sudo: PV changed from "1.9.5p2" to "1.9.6"
packages/core2-32-poky-linux/sudo: SRC_URI changed from 
"https://www.sudo.ws/dist/sudo-1.9.5p2.tar.gz file://sudo.pam 
file://0001-sudo.conf.in-fix-conflict-with-multilib.patch" to 
"https://www.sudo.ws/dist/sudo-1.9.6.tar.gz file://sudo.pam 
file://0001-sudo.conf.in-fix-conflict-with-multilib.patch"
packages/core2-32-poky-linux/sudo: PKGV changed from 1.9.5p2 [default] to 1.9.6 
[default]
packages/core2-32-poky-linux/sudo/sudo-dbg: PV changed from "1.9.5p2" to "1.9.6"
packages/core2-32-poky-linux/sudo/sudo-dbg: PKGSIZE changed from 3671396 to 
3778920 (+3%)
packages/core2-32-poky-linux/sudo/sudo-dbg: PKGV changed from 1.9.5p2 [default] 
to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-dev: PV changed from "1.9.5p2" to "1.9.6"
packages/core2-32-poky-linux/sudo/sudo-dev: PKGV changed from 1.9.5p2 [default] 
to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-doc: PV changed from "1.9.5p2" to "1.9.6"
packages/core2-32-poky-linux/sudo/sudo-doc: PKGSIZE changed from 647108 to 
2575585 (+298%)
packages/core2-32-poky-linux/sudo/sudo-doc: PKGV changed from 1.9.5p2 [default] 
to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-lib: PV changed from "1.9.5p2" to "1.9.6"
packages/core2-32-poky-linux/sudo/sudo-lib: PKGSIZE changed from 827168 to 
831232 (+0%)
packages/core2-32-poky-linux/sudo/sudo-lib: PKGV changed from 1.9.5p2 [default] 
to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-ast: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-ast: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-ca: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-ca: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-cs: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-cs: PKGSIZE changed from 86538 to 
87493 (+1%)
packages/core2-32-poky-linux/sudo/sudo-locale-cs: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-da: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-da: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-de: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-de: PKGSIZE changed from 90665 to 
91660 (+1%)
packages/core2-32-poky-linux/sudo/sudo-locale-de: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-el: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-el: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-eo: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-eo: PKGSIZE changed from 83324 to 
84426 (+1%)
packages/core2-32-poky-linux/sudo/sudo-locale-eo: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-es: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-es: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-eu: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-eu: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-fi: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-fi: PKGSIZE changed from 77261 to 
88869 (+15%)
packages/core2-32-poky-linux/sudo/sudo-locale-fi: PKGV changed from 1.9.5p2 
[default] to 1.9.6 [default]
packages/core2-32-poky-linux/sudo/sudo-locale-fr: PV changed from "1.9.5p2" to 
"1.9.6"
packages/core2-32-poky-linux/sudo/sudo-locale-fr: PKGSIZE changed from 94269 to 
95504 (+1%)
packages/core2-32-poky-linux/sudo/sudo-locale-fr: PKGV changed from 1.9.5p2

[OE-core] [AUH] libhandy: upgrading to 1.2.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libhandy* to *1.2.0* has 
Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe libhandy failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-c593a17477c3c4a50600195b3c6fd8098add2ce7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:c593a17477c3c4a50600195b3c6fd8098add2ce7"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Extracting upgraded version source...
WARNING: Command 'git rebase 7b38a860ffcec6c2ad28153358cc3d037ddb618f' failed:
First, rewinding head to replay your work on top of it...
Applying: Release 1.0.3
Using index info to reconstruct a base tree...
M   NEWS
M   data/packaging/rpm/libhandy.spec
M   debian/changelog
M   meson.build
Falling back to patching base and 3-way merge...
Auto-merging meson.build
CONFLICT (content): Merge conflict in meson.build
Auto-merging debian/changelog
CONFLICT (content): Merge conflict in debian/changelog
Auto-merging data/packaging/rpm/libhandy.spec
CONFLICT (content): Merge conflict in data/packaging/rpm/libhandy.spec
Auto-merging NEWS
CONFLICT (content): Merge conflict in NEWS
error: Failed to merge in the changes.
Patch failed at 0001 Release 1.0.3
Use 'git am --show-current-patch' to see the failed patch

Resolve all conflicts manually, mark them as resolved with
"git add/rm ", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase 
--abort".

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/libhandy
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libhandy/libhandy_1.2.0.bb



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149507): 
https://lists.openembedded.org/g/openembedded-core/message/149507
Mute This Topic: https://lists.openembedded.org/mt/81354120/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] python3-setuptools-scm: upgrading to 5.0.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools-scm* to 
*5.0.2* has Succeeded.

Next steps:
- apply the patch: git am 
0001-python3-setuptools-scm-upgrade-5.0.1-5.0.2.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/python3-setuptools-scm: PKGV changed from 5.0.1 
[default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/s/setuptools_scm/setuptools_scm-5.0.1.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/s/setuptools_scm/setuptools_scm-5.0.2.tar.gz;
packages/core2-32-poky-linux/python3-setuptools-scm: PV changed from "5.0.1" to 
"5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dbg: 
PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dbg: 
PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dev: 
PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dev: 
PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-doc: 
PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-doc: 
PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-locale:
 PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-locale:
 PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-src: 
PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-src: 
PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-staticdev:
 PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-staticdev:
 PV changed from "5.0.1" to "5.0.2"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: 
PKGSIZE changed from 121854 to 123393 (+1%)
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: 
PKGV changed from 5.0.1 [default] to 5.0.2 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: PV 
changed from "5.0.1" to "5.0.2"
Changes to packages/core2-32-poky-linux/python3-setuptools-scm (sysroot):
  /usr/lib/python3.9/site-packages/setuptools_scm-5.0.1-py3.9.egg-info moved to 
/usr/lib/python3.9/site-packages/setuptools_scm-5.0.2-py3.9.egg-info
Changes to packages/x86_64-linux/python3-setuptools-scm-native (sysroot):
  /usr/lib/python3.9/site-packages/setuptools_scm-5.0.1-py3.9.egg-info moved to 
/usr/lib/python3.9/site-packages/setuptools_scm-5.0.2-py3.9.egg-info
>From 6106e636c748690b1e54561418a6ec958ba15e91 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:22:52 +
Subject: [PATCH] python3-setuptools-scm: upgrade 5.0.1 -> 5.0.2

---
 ...-setuptools-scm_5.0.1.bb => python3-setuptools-scm_5.0.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-setuptools-scm_5.0.1.bb => python3-setuptools-scm_5.0.2.bb} (90%)

diff --git a/meta/recipes-devtools/python/python3-setuptools-scm_5.0.1.bb b/meta/recipes-devtools/python/python3-setuptools-scm_5.0.2.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-setuptools-scm_5.0.1.bb
rename to meta/recipes-devtools/python/python3-setuptools-scm_5.0.2.bb
index ead80da7b4..dd74aef2b1 100644
--- a/meta/recipes-devtools/python/python3-setuptools-scm_5.0.1.bb
+++ b/meta/recipes-devtools/python/python3-setuptools-scm_5.0.2.bb
@@ -4,7 +4,7 @@ DESCRIPTION = "setuptools_scm handles managing your Python package versions in S
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://PKG-INFO;beginline=8;endline=8;md5=8227180126797a0148f94f483f3e1489"
 
-SRC_URI[sha256sum] = "c85b6b46d0edd40d2301038cdea96bb6adc14d62ef943e75afb08b3e7bcf142a"

[OE-core] [AUH] libedit: upgrading to 20210216-3.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libedit* to *20210216-3.1* 
has Succeeded.

Next steps:
- apply the patch: git am 
0001-libedit-upgrade-20191231-3.1-20210216-3.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
packages/core2-32-poky-linux/libedit: PV changed from "20191231-3.1" to 
"20210216-3.1"
packages/core2-32-poky-linux/libedit: SRC_URI changed from 
"http://www.thrysoee.dk/editline/libedit-20191231-3.1.tar.gz 
file://stdc-predef.patch" to 
"http://www.thrysoee.dk/editline/libedit-20210216-3.1.tar.gz 
file://stdc-predef.patch"
packages/core2-32-poky-linux/libedit: PKGV changed from 20191231-3.1 [default] 
to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-dbg: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-dbg: PKGSIZE changed from 517260 
to 517184 (-0%)
packages/core2-32-poky-linux/libedit/libedit-dbg: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-dbg: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit-dev: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-dev: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-dev: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit-doc: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-doc: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-doc: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit-locale: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-locale: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-locale: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit-src: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-src: PKGSIZE changed from 578860 
to 578903 (+0%)
packages/core2-32-poky-linux/libedit/libedit-src: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-src: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit-staticdev: PV changed from 
"20191231-3.1" to "20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit-staticdev: PKGV changed from 
20191231-3.1 [default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit-staticdev: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
packages/core2-32-poky-linux/libedit/libedit: PV changed from "20191231-3.1" to 
"20210216-3.1"
packages/core2-32-poky-linux/libedit/libedit: PKGV changed from 20191231-3.1 
[default] to 20210216-3.1 [default]
packages/core2-32-poky-linux/libedit/libedit: FILELIST: removed 
"/usr/lib/libedit.so.0.0.63", added "/usr/lib/libedit.so.0.0.64"
Changes to packages/core2-32-poky-linux/libedit (sysroot):
  /usr/lib/libedit.so.0 changed symlink target from libedit.so.0.0.63 to 
libedit.so.0.0.64
  /usr/lib/libedit.so changed symlink target from libedit.so.0.0.63 to 
libedit.so.0.0.64
  /usr/lib/libedit.so.0.0.63 moved to /usr/lib/libedit.so.0.0.64
>From 833069d4e53d8be678ff85a254169ad8992b1089 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:08:17 +
Subject: [PATCH] libedit: upgrade 20191231-3.1 -> 20210216-3.1

---
 .../{libedit_20191231-3.1.bb => libedit_20210216-3.1.bb}   | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-devtools/libedit/{libedit_20191231-3.1.bb => libedit_20210216-3.1.bb} (82%)

diff --git a/meta/recipes-devtools/libedit/libedit_20191231-3.1.bb b/meta/recipes-devtools/libedit/libedit_20210216-3.1.bb
similarity index 82%
rename from

[OE-core] [AUH] go: upgrading to 1.16.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.16.2* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-go-upgrade-1.16-1.16.2.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
>From db8974e5e88b7e8f491a1907d3360352434e84f8 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:02:35 +
Subject: [PATCH] go: upgrade 1.16 -> 1.16.2

---
 meta/recipes-devtools/go/{go-1.16.inc => go-1.16.2.inc}   | 4 ++--
 .../0001-allow-CC-and-CXX-to-have-multiple-words.patch| 0
 ...cmd-go-make-content-based-hash-generation-less-pedan.patch | 0
 ...-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch | 0
 .../0004-ld-add-soname-to-shareable-objects.patch | 0
 ...make.bash-override-CC-when-building-dist-and-go_boot.patch | 0
 .../0006-cmd-dist-separate-host-and-target-builds.patch   | 0
 .../0007-cmd-go-make-GOROOT-precious-by-default.patch | 0
 .../0008-use-GOBUILDMODE-to-set-buildmode.patch   | 0
 ...0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch | 0
 meta/recipes-devtools/go/{go_1.16.bb => go_1.16.2.bb} | 0
 11 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/go/{go-1.16.inc => go-1.16.2.inc} (88%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0004-ld-add-soname-to-shareable-objects.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0006-cmd-dist-separate-host-and-target-builds.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0007-cmd-go-make-GOROOT-precious-by-default.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0008-use-GOBUILDMODE-to-set-buildmode.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (100%)
 rename meta/recipes-devtools/go/{go_1.16.bb => go_1.16.2.bb} (100%)

diff --git a/meta/recipes-devtools/go/go-1.16.inc b/meta/recipes-devtools/go/go-1.16.2.inc
similarity index 88%
rename from meta/recipes-devtools/go/go-1.16.inc
rename to meta/recipes-devtools/go/go-1.16.2.inc
index 1ebbbef833..e65caf8197 100644
--- a/meta/recipes-devtools/go/go-1.16.inc
+++ b/meta/recipes-devtools/go/go-1.16.2.inc
@@ -1,7 +1,7 @@
 require go-common.inc
 
 GO_BASEVERSION = "1.16"
-PV = "1.16"
+PV = "1.16.2"
 FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
 
 LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
@@ -17,4 +17,4 @@ SRC_URI += "\
 file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
 file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
 "
-SRC_URI[main.sha256sum] = "7688063d55656105898f323d90a79a39c378d86fe89ae192eb3b7fc46347c95a"
+SRC_URI[main.sha256sum] = "37ca14287a23cb8ba2ac3f5c3dd8adbc1f7a54b9701a57824bf19a0b271f83ea"
diff --git a/meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch b/meta/recipes-devtools/go/go-1.16.2/0001-allow-CC-and-CXX-to-have-multiple-words.patch
similarity index 100%
rename from meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
rename to meta/recipes-devtools/go/go-1.16.2/0001-allow-CC-and-CXX-to-have-multiple-words.patch
diff --git a/meta/recipes-devtools/go/go-1.16/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch b/meta/recipes-devtools/go/go-1.16.2/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
similarity index 100%
rename from meta/recipes-devtools/go/go-1.16/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
rename to meta/recipes-devtools/go/go-1.16.2/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
diff --git

[OE-core] [AUH] libdnf: upgrading to 0.60.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdnf* to *0.60.0* has 
Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade libdnf -V 0.60.0 -S 
d6e0618f8658267df582327301104307b4427e59
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-b6bdefb78235dd27084fdcf016afd72971145f86"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:b6bdefb78235dd27084fdcf016afd72971145f86"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 20 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Extracting upgraded version source...
ERROR: Execution of 'git checkout d6e0618f8658267df582327301104307b4427e59' 
failed with exit code 128:
fatal: reference is not a tree: d6e0618f8658267df582327301104307b4427e59




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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149490): 
https://lists.openembedded.org/g/openembedded-core/message/149490
Mute This Topic: https://lists.openembedded.org/mt/81354103/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] git: upgrading to 2.30.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.30.2* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-git-upgrade-2.30.1-2.30.2.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
>From 6aa1773e4cb651c0632c02425f5bb2201d823dc0 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 05:55:35 +
Subject: [PATCH] git: upgrade 2.30.1 -> 2.30.2

---
 meta/recipes-devtools/git/{git_2.30.1.bb => git_2.30.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/git/{git_2.30.1.bb => git_2.30.2.bb} (75%)

diff --git a/meta/recipes-devtools/git/git_2.30.1.bb b/meta/recipes-devtools/git/git_2.30.2.bb
similarity index 75%
rename from meta/recipes-devtools/git/git_2.30.1.bb
rename to meta/recipes-devtools/git/git_2.30.2.bb
index bc1635ada9..319140353f 100644
--- a/meta/recipes-devtools/git/git_2.30.1.bb
+++ b/meta/recipes-devtools/git/git_2.30.2.bb
@@ -5,5 +5,5 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
  "
 EXTRA_OEMAKE += "NO_GETTEXT=1"
 
-SRC_URI[tarball.sha256sum] = "23a3e53f0d2dd3e62a8147b24a1a91d6ffe95b92123ef4dbae04e9a6205e71c0"
+SRC_URI[tarball.sha256sum] = "9ddea08fc7c38f1823a54a014ae2e9ecd45e1b4a06e919025f4c41f2c6a8061b"
 SRC_URI[manpages.sha256sum] = "db323e1b242e9d0337363b1e538c8b879e4c46eedbf94d3bee9e65dab6d49138"
-- 
2.17.1

Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 814 .bb files complete (813 cached, 1 parsed). 1438 targets, 31 
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-aec16a75ccc8d99b73d49db86eae6eb4e3cdd844"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:aec16a75ccc8d99b73d49db86eae6eb4e3cdd844"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 245 Local 236 Network 0 Missed 9 Current 448 (96% match, 
98% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 1585 of 2197 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/git/git_2.30.2.bb:do_fetch)
NOTE: recipe git-2.30.2-r0: task do_fetch: Started
WARNING: git-2.30.2-r0 do_fetch: Checksum mismatch for local file 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz
Cleaning and trying again.
WARNING: git-2.30.2-r0 do_fetch: Renaming 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz
 to 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz_bad-checksum_c62cb68b551214e61f0de87e7217938020bcc708011100612760812ea494b1d4
WARNING: git-2.30.2-r0 do_fetch: Checksum failure encountered with download of 
https://cdn.kernel.org/pub/software/scm/git/git-manpages-2.30.2.tar.gz;name=manpages
 - will attempt other sources if available
WARNING: git-2.30.2-r0 do_fetch: Checksum mismatch for local file 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz
Cleaning and trying again.
WARNING: git-2.30.2-r0 do_fetch: Renaming 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz
 to 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git-manpages-2.30.2.tar.gz_bad-checksum_c62cb68b551214e61f0de87e7217938020bcc708011100612760812ea494b1d4
ERROR: git-2.30.2-r0 do_fetch: Checksum failure fetching 
https://cdn.kernel.org/pub/software/scm/git/git-manpages-2.30.2.tar.gz;name=manpages
ERROR: git-2.30.2-r0 do_fetch: Fetcher failure for URL: 
'https://cdn.kernel.org/pub/software/scm/git/git-manpages-2.30.2.tar.gz;name=manpages'.
 Checksum mismatch!
File:

[OE-core] [AUH] gnu-efi: upgrading to 3.0.13 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-efi* to *3.0.13* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-gnu-efi-upgrade-3.0.12-3.0.13.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/gnu-efi/gnu-efi-dbg: PV changed from "3.0.12" to 
"3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-dbg: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-dev: PV changed from "3.0.12" to 
"3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-dev: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-dev: PKGSIZE changed from 358374 
to 365662 (+2%)
packages/core2-32-poky-linux/gnu-efi/gnu-efi-doc: PV changed from "3.0.12" to 
"3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-doc: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-locale: PV changed from "3.0.12" 
to "3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-locale: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-src: PV changed from "3.0.12" to 
"3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-src: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-src: PKGSIZE changed from 340060 
to 343685 (+1%)
packages/core2-32-poky-linux/gnu-efi/gnu-efi-staticdev: PV changed from 
"3.0.12" to "3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi-staticdev: PKGV changed from 
3.0.12 [default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi/gnu-efi-staticdev: PKGSIZE changed from 
341348 to 353568 (+4%)
packages/core2-32-poky-linux/gnu-efi/gnu-efi: PV changed from "3.0.12" to 
"3.0.13"
packages/core2-32-poky-linux/gnu-efi/gnu-efi: PKGV changed from 3.0.12 
[default] to 3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi: PV changed from "3.0.12" to "3.0.13"
packages/core2-32-poky-linux/gnu-efi: PKGV changed from 3.0.12 [default] to 
3.0.13 [default]
packages/core2-32-poky-linux/gnu-efi: SRC_URI changed from 
"https://downloads.sourceforge.net/gnu-efi/files/gnu-efi-3.0.12.tar.bz2 
file://parallel-make-archives.patch 
file://lib-Makefile-fix-parallel-issue.patch 
file://gnu-efi-3.0.9-fix-clang-build.patch" to 
"https://downloads.sourceforge.net/gnu-efi/files/gnu-efi-3.0.13.tar.bz2 
file://parallel-make-archives.patch 
file://lib-Makefile-fix-parallel-issue.patch 
file://gnu-efi-3.0.9-fix-clang-build.patch"
Changes to packages/core2-32-poky-linux/gnu-efi (sysroot):
  /usr/include/efi/eficonex.h was added
  /usr/include/efi/lib.h was added
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
ERROR: Nothing PROVIDES 'gnu-efi'
gnu-efi was skipped: incompatible with host mips-poky-linux (not in 
COMPATIBLE_HOST)
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1438 targets, 58 
skipped, 0 masked, 0 errors.

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Changes to packages/core2-32-poky-linux/gnu-efi (sysroot):
  /usr/include/efi/eficonex.h was added
  /usr/include/efi/lib.h was added
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
ERROR: Nothing PROVIDES 'gnu-efi'
gnu-efi was skipped: incompatible with host powerpc-poky-linux (not in 
COMPATIBLE_HOST)
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1438 targets, 67 
skipped, 0 masked, 0 errors.

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>From 2fed5c572451f55ef431ff386c6c164d848cef80 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 01:56:19 +
Subject: [PATCH] gnu-efi: upgrade 3.0.12 -> 3.0.13

---
 .../gnu-efi/{gnu-efi_3.0.12.bb => gnu-efi_3.0.13.bb}   | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-bsp/gnu-efi/{gnu-efi_3.0.12.bb => gnu-efi_3.0.13.bb} (95%)

diff --git a/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.12.bb b/meta/recipes-bsp/gnu-efi/gnu-efi_3.0.13.bb
similarity index 95%
rename from meta/recipes-bsp/gnu-efi/gnu-efi_3.0.12.bb
rename to meta/recipes-bsp/gnu-efi/gnu-efi_3.0.13.bb
index d27126603f..fa9886037c 100644
---

[OE-core] [AUH] python3-hypothesis: upgrading to 6.8.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to 
*6.8.1* has Succeeded.

Next steps:
- apply the patch: git am 0001-python3-hypothesis-upgrade-6.2.0-6.8.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
packages/core2-32-poky-linux/python3-hypothesis: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.2.0.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.8.1.tar.gz;
packages/core2-32-poky-linux/python3-hypothesis: PKGV changed from 6.2.0 
[default] to 6.8.1 [default]
packages/core2-32-poky-linux/python3-hypothesis: PV changed from "6.2.0" to 
"6.8.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: 
FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/hypothesis-6.2.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/hypothesis-6.8.1-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/filtering.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/utils.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/filtering.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/scrutineer.cpython-39.pyc
 
/usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/__pycache__/utils.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/internal/scrutineer.py"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PKGV 
changed from 6.2.0 [default] to 6.8.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PV 
changed from "6.2.0" to "6.8.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: 
FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/hypothesis-6.2.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/hypothesis-6.8.1-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/filtering.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/utils.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/filtering.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/scrutineer.cpython-39.pyc
 
/usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/__pycache__/utils.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/internal/scrutineer.py"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PKGV 
changed from 6.2.0 [default] to 6.8.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PV 
changed from "6.2.0" to "6.8.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: 
FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/hypothesis-6.2.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/hypothesis-6.8.1-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/filtering.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/utils.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/filtering.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/scrutineer.cpython-39.pyc
 
/usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/__pycache__/utils.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/internal/scrutineer.py"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PKGV 
changed from 6.2.0 [default] to 6.8.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PV 
changed from "6.2.0" to "6.8.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-locale: 
FILELIST: directory renamed 
/usr/lib/python3.9/site-packages/hypothesis-6.2.0-py3.9.egg-info -> 
/usr/lib/python3.9/site-packages/hypothesis-6.8.1-py3.9.egg-info, added 
"/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/filtering.cpython-39.pyc
 /usr/lib/python3.9/site-packages/hypothesis/strategies/_internal/utils.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/filtering.py 
/usr/lib/python3.9/site-packages/hypothesis/internal/__pycache__/scrutineer.cpython-39.pyc

[OE-core] [AUH] e2fsprogs: upgrading to 1.46.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *e2fsprogs* to *1.46.2* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-e2fsprogs-upgrade-1.46.1-1.46.2.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/e2fsprogs/e2fsprogs-badblocks: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-badblocks: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PV changed from "1.46.1" 
to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PKGV changed from 1.46.1 
[default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PKGSIZE changed from 
5263740 to 5274224 (+0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PV changed from "1.46.1" 
to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PKGV changed from 1.46.1 
[default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PKGSIZE changed from 
209944 to 209963 (+0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PV changed from "1.46.1" 
to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PKGV changed from 1.46.1 
[default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PKGSIZE changed from 
226131 to 226240 (+0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dumpe2fs: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dumpe2fs: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2fsck: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2fsck: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PKGSIZE changed from 
12689 to 12691 (+0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PKGSIZE changed 
from 138882 to 138601 (-0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PKGSIZE changed 
from 185395 to 185139 (-0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-da: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-da: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-da: PKGSIZE changed 
from 140084 to 139811 (-0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PKGSIZE changed 
from 175553 to 175279 (-0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PKGSIZE changed 
from 87964 to 87698 (-0%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PKGSIZE changed 
from 186138 to 190454 (+2%)
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-fi: PV changed from 
"1.46.1" to "1.46.2"
packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-fi: PKGV changed from 
1.46.1 [default] to 1.46.2 [default]

[OE-core] [AUH] gnu-config: upgrading to 277b4ed1776f721145b2649d888f1deb445fecc5 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to 
*277b4ed1776f721145b2649d888f1deb445fecc5* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade gnu-config -S 
277b4ed1776f721145b2649d888f1deb445fecc5
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-74730613fb8c1da40700414834f270c4c1e91db9"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:74730613fb8c1da40700414834f270c4c1e91db9"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 8 Local 0 Network 0 Missed 8 Current 12 (0% match, 60% 
complete)
NOTE: Executing Tasks
ERROR: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:devtool_post_unpack(d)
 0003:
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/meta/classes/devtool-source.bbclass',
 lineno: 150, function: devtool_post_unpack
 0146:"doesn't use any source or the correct source "
 0147:"directory could not be determined" % d.getVar('PN'))
 0148:
 0149:devbranch = d.getVar('DEVTOOL_DEVBRANCH')
 *** 0150:setup_git_repo(srcsubdir, d.getVar('PV'), devbranch, d=d)
 0151:
 0152:(stdout, _) = bb.process.run('git rev-parse HEAD', cwd=srcsubdir)
 0153:initial_rev = stdout.rstrip()
 0154:with open(os.path.join(tempdir, 'initial_rev'), 'w') as f:
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/__init__.py',
 lineno: 233, function: setup_git_repo
 0229:with open(excludefile, 'w') as f:
 0230:for line in excludes:
 0231:f.write(line)
 0232:
 *** 0233:bb.process.run('git checkout -b %s' % devbranch, cwd=repodir)
 0234:bb.process.run('git tag -f %s' % basetag, cwd=repodir)
 0235:
 0236:def recipe_to_append(recipefile, config, wildcard=False):
 0237:"""
File: 
'/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/process.py', 
lineno: 184, function: run
 0180:if not stderr is None:
 0181:stderr = stderr.decode("utf-8")
 0182:
 0183:if pipe.returncode != 0:
 *** 0184:raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
 0185:return stdout, stderr
Exception: bb.process.ExecutionError: Execution of 'git checkout -b 
devtool-orig' failed with exit code 128:
fatal: A branch named 'devtool-orig' already exists.


ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20210125+gitAUTOINC+6faca61810-r0/devtooltmp-93mjrj6o/temp/log.do_unpack.15210
NOTE: Tasks Summary: Attempted 55 tasks of which 47 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
ERROR: Extracting source for gnu-config failed



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149484): 
https://lists.openembedded.org/g/openembedded-core/message/149484
Mute This Topic: https://lists.openembedded.org/mt/81354097/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] go-runtime: upgrading to 1.16.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.16.2* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-go-runtime-upgrade-1.16-1.16.2.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
>From 54ee2ed0e09e29a5b7bcc79b86bceaa73b39abf9 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 06:00:11 +
Subject: [PATCH] go-runtime: upgrade 1.16 -> 1.16.2

---
 meta/recipes-devtools/go/{go-1.16.inc => go-1.16.2.inc}   | 4 ++--
 .../0001-allow-CC-and-CXX-to-have-multiple-words.patch| 0
 ...cmd-go-make-content-based-hash-generation-less-pedan.patch | 0
 ...-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch | 0
 .../0004-ld-add-soname-to-shareable-objects.patch | 0
 ...make.bash-override-CC-when-building-dist-and-go_boot.patch | 0
 .../0006-cmd-dist-separate-host-and-target-builds.patch   | 0
 .../0007-cmd-go-make-GOROOT-precious-by-default.patch | 0
 .../0008-use-GOBUILDMODE-to-set-buildmode.patch   | 0
 ...0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch | 0
 .../go/{go-runtime_1.16.bb => go-runtime_1.16.2.bb}   | 0
 11 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/go/{go-1.16.inc => go-1.16.2.inc} (88%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0001-allow-CC-and-CXX-to-have-multiple-words.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0003-allow-GOTOOLDIR-to-be-overridden-in-the-environment.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0004-ld-add-soname-to-shareable-objects.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0005-make.bash-override-CC-when-building-dist-and-go_boot.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0006-cmd-dist-separate-host-and-target-builds.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0007-cmd-go-make-GOROOT-precious-by-default.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0008-use-GOBUILDMODE-to-set-buildmode.patch (100%)
 rename meta/recipes-devtools/go/{go-1.16 => go-1.16.2}/0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch (100%)
 rename meta/recipes-devtools/go/{go-runtime_1.16.bb => go-runtime_1.16.2.bb} (100%)

diff --git a/meta/recipes-devtools/go/go-1.16.inc b/meta/recipes-devtools/go/go-1.16.2.inc
similarity index 88%
rename from meta/recipes-devtools/go/go-1.16.inc
rename to meta/recipes-devtools/go/go-1.16.2.inc
index 1ebbbef833..e65caf8197 100644
--- a/meta/recipes-devtools/go/go-1.16.inc
+++ b/meta/recipes-devtools/go/go-1.16.2.inc
@@ -1,7 +1,7 @@
 require go-common.inc
 
 GO_BASEVERSION = "1.16"
-PV = "1.16"
+PV = "1.16.2"
 FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
 
 LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
@@ -17,4 +17,4 @@ SRC_URI += "\
 file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
 file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
 "
-SRC_URI[main.sha256sum] = "7688063d55656105898f323d90a79a39c378d86fe89ae192eb3b7fc46347c95a"
+SRC_URI[main.sha256sum] = "37ca14287a23cb8ba2ac3f5c3dd8adbc1f7a54b9701a57824bf19a0b271f83ea"
diff --git a/meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch b/meta/recipes-devtools/go/go-1.16.2/0001-allow-CC-and-CXX-to-have-multiple-words.patch
similarity index 100%
rename from meta/recipes-devtools/go/go-1.16/0001-allow-CC-and-CXX-to-have-multiple-words.patch
rename to meta/recipes-devtools/go/go-1.16.2/0001-allow-CC-and-CXX-to-have-multiple-words.patch
diff --git a/meta/recipes-devtools/go/go-1.16/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch b/meta/recipes-devtools/go/go-1.16.2/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
similarity index 100%
rename from meta/recipes-devtools/go/go-1.16/0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
rename to

[OE-core] [AUH] openssh: upgrading to 8.5p1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssh* to *8.5p1* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-openssh-upgrade-8.4p1-8.5p1.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/openssh: PKGV changed from 8.4p1 [default] to 
8.5p1 [default]
packages/core2-32-poky-linux/openssh: PV changed from "8.4p1" to "8.5p1"
packages/core2-32-poky-linux/openssh: SRC_URI changed from 
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.4p1.tar.gz 
file://sshd_config file://ssh_config file://init file://sshd file://sshd.socket 
file://sshd@.service file://sshdgenkeys.service file://volatiles.99_sshd 
file://run-ptest 
file://fix-potential-signed-overflow-in-pointer-arithmatic.patch 
file://sshd_check_keys file://add-test-support-for-busybox.patch 
file://0f90440ca70abab947acbd77795e9f130967956c.patch" to 
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.5p1.tar.gz 
file://sshd_config file://ssh_config file://init file://sshd file://sshd.socket 
file://sshd@.service file://sshdgenkeys.service file://volatiles.99_sshd 
file://run-ptest 
file://fix-potential-signed-overflow-in-pointer-arithmatic.patch 
file://sshd_check_keys file://add-test-support-for-busybox.patch"
packages/core2-32-poky-linux/openssh/openssh-dbg: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-dbg: PKGSIZE changed from 11148804 
to 12308788 (+10%)
packages/core2-32-poky-linux/openssh/openssh-dbg: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-dev: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-dev: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-doc: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-doc: PKGSIZE changed from 303199 
to 309834 (+2%)
packages/core2-32-poky-linux/openssh/openssh-doc: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-keygen: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-keygen: PKGSIZE changed from 
542200 to 574968 (+6%)
packages/core2-32-poky-linux/openssh/openssh-keygen: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-locale: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-locale: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-misc: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-misc: PKGSIZE changed from 2608807 
to 2733416 (+5%)
packages/core2-32-poky-linux/openssh/openssh-misc: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-ptest: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-ptest: PKGSIZE changed from 817658 
to 1183745 (+45%)
packages/core2-32-poky-linux/openssh/openssh-ptest: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-scp: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-scp: PKGSIZE changed from 128496 
to 148976 (+16%)
packages/core2-32-poky-linux/openssh/openssh-scp: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-sftp-server: PKGV changed from 
8.4p1 [default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-sftp-server: PKGSIZE changed from 
144872 to 161256 (+11%)
packages/core2-32-poky-linux/openssh/openssh-sftp-server: PV changed from 
"8.4p1" to "8.5p1"
packages/core2-32-poky-linux/openssh/openssh-sftp: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-sftp: PKGSIZE changed from 185936 
to 218704 (+18%)
packages/core2-32-poky-linux/openssh/openssh-sftp: PV changed from "8.4p1" to 
"8.5p1"
packages/core2-32-poky-linux/openssh/openssh-src: PKGV changed from 8.4p1 
[default] to 8.5p1 [default]
packages/core2-32-poky-linux/openssh/openssh-src: PKGSIZE changed from 3136471 
to 3156096 (+1%)
packages/core2-32-poky-linux/openssh/openssh-src: PV changed from

[OE-core] [AUH] bison: upgrading to 3.7.6 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bison* to *3.7.6* has 
Succeeded.

Next steps:
- apply the patch: git am 0001-bison-upgrade-3.7.5-3.7.6.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/bison/bison-dbg: PKGV changed from 3.7.5 [default] 
to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-dbg: PV changed from "3.7.5" to "3.7.6"
packages/core2-32-poky-linux/bison/bison-dbg: PKGSIZE changed from 1895552 to 
1895704 (+0%)
packages/core2-32-poky-linux/bison/bison-dev: PKGV changed from 3.7.5 [default] 
to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-dev: PV changed from "3.7.5" to "3.7.6"
packages/core2-32-poky-linux/bison/bison-doc: PKGV changed from 3.7.5 [default] 
to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-doc: PV changed from "3.7.5" to "3.7.6"
packages/core2-32-poky-linux/bison/bison-doc: PKGSIZE changed from 1031392 to 
1035439 (+0%)
packages/core2-32-poky-linux/bison/bison-locale-af: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-af: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-af: PKGSIZE changed from 1371 
to 1412 (+3%)
packages/core2-32-poky-linux/bison/bison-locale-ast: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-ast: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-ast: PKGSIZE changed from 1352 
to 1393 (+3%)
packages/core2-32-poky-linux/bison/bison-locale-be: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-be: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-be: PKGSIZE changed from 1762 
to 1803 (+2%)
packages/core2-32-poky-linux/bison/bison-locale-bg: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-bg: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-bg: PKGSIZE changed from 42289 
to 42029 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-ca: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-ca: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-ca: PKGSIZE changed from 15795 
to 15572 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-cs: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-cs: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-cs: PKGSIZE changed from 2144 
to 2185 (+2%)
packages/core2-32-poky-linux/bison/bison-locale-da: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-da: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-da: PKGSIZE changed from 18077 
to 17909 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-de: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-de: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-de: PKGSIZE changed from 32938 
to 32734 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-el: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-el: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-el: PKGSIZE changed from 37304 
to 37062 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-eo: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-eo: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-eo: PKGSIZE changed from 31747 
to 31561 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-es: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]
packages/core2-32-poky-linux/bison/bison-locale-es: PV changed from "3.7.5" to 
"3.7.6"
packages/core2-32-poky-linux/bison/bison-locale-es: PKGSIZE changed from 16598 
to 16382 (-1%)
packages/core2-32-poky-linux/bison/bison-locale-et: PKGV changed from 3.7.5 
[default] to 3.7.6 [default]

[OE-core] [AUH] dnf: upgrading to 4.6.1 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dnf* to *4.6.1* has Succeeded.

Next steps:
- apply the patch: git am 0001-dnf-upgrade-4.6.0-4.6.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
packages/core2-32-poky-linux/dnf/dnf-bash-completion: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-bash-completion: PV changed from "4.6.0" 
to "4.6.1"
packages/core2-32-poky-linux/dnf/dnf-dbg: PKGV changed from 4.6.0 [default] to 
4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-dbg: PV changed from "4.6.0" to "4.6.1"
packages/core2-32-poky-linux/dnf/dnf-dev: PKGV changed from 4.6.0 [default] to 
4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-dev: PV changed from "4.6.0" to "4.6.1"
packages/core2-32-poky-linux/dnf/dnf-doc: PKGV changed from 4.6.0 [default] to 
4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-doc: PV changed from "4.6.0" to "4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-ar: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-ar: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-bg: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-bg: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-bn-in: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-bn-in: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-ca: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-ca: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-cs: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-cs: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-da: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-da: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-de: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-de: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-el: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-el: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-en-gb: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-en-gb: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-eo: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-eo: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-es: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-es: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-eu: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-eu: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-fa: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-fa: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-fi: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-fi: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-fil: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-fil: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-fr: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-fr: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-fur: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-fur: PV changed from "4.6.0" to 
"4.6.1"
packages/core2-32-poky-linux/dnf/dnf-locale-gd: PKGV changed from 4.6.0 
[default] to 4.6.1 [default]
packages/core2-32-poky-linux/dnf/dnf-locale-gd:

[OE-core] [AUH] autoconf-archive: upgrading to 2021.02.19 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *autoconf-archive* to 
*2021.02.19* has Succeeded.

Next steps:
- apply the patch: git am 
0001-autoconf-archive-upgrade-2019.01.06-2021.02.19.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/all-poky-linux/autoconf-archive/autoconf-archive-doc: PKGV changed 
from 2019.01.06 [default] to 2021.02.19 [default]
packages/all-poky-linux/autoconf-archive/autoconf-archive-doc: PV changed from 
"2019.01.06" to "2021.02.19"
packages/all-poky-linux/autoconf-archive/autoconf-archive-doc: PKGSIZE changed 
from 46036 to 46547 (+1%)
packages/all-poky-linux/autoconf-archive/autoconf-archive-src: PKGV changed 
from 2019.01.06 [default] to 2021.02.19 [default]
packages/all-poky-linux/autoconf-archive/autoconf-archive-src: PV changed from 
"2019.01.06" to "2021.02.19"
packages/all-poky-linux/autoconf-archive/autoconf-archive: PKGV changed from 
2019.01.06 [default] to 2021.02.19 [default]
packages/all-poky-linux/autoconf-archive/autoconf-archive: PV changed from 
"2019.01.06" to "2021.02.19"
packages/all-poky-linux/autoconf-archive/autoconf-archive: PKGSIZE changed from 
2068942 to 2092330 (+1%)
packages/all-poky-linux/autoconf-archive: PKGV changed from 2019.01.06 
[default] to 2021.02.19 [default]
packages/all-poky-linux/autoconf-archive: SRC_URI changed from 
"https://ftp.gnu.org/gnu/autoconf-archive/autoconf-archive-2019.01.06.tar.xz; 
to "https://ftp.gnu.org/gnu/autoconf-archive/autoconf-archive-2021.02.19.tar.xz;
packages/all-poky-linux/autoconf-archive: PV changed from "2019.01.06" to 
"2021.02.19"
Changes to packages/all-poky-linux/autoconf-archive (sysroot):
  /usr/share/aclocal/ax_boost_process.m4 was added
  /usr/share/aclocal/ax_check_pcre2.m4 was added
  /usr/share/aclocal/ax_int128.m4 was added
  /usr/share/aclocal/ax_prepend_flag.m4 was added
  /usr/share/aclocal/ax_prog_robot.m4 was added
Changes to packages/all-poky-linux/autoconf-archive (sysroot):
  /usr/share/aclocal/ax_boost_process.m4 was added
  /usr/share/aclocal/ax_check_pcre2.m4 was added
  /usr/share/aclocal/ax_int128.m4 was added
  /usr/share/aclocal/ax_prepend_flag.m4 was added
  /usr/share/aclocal/ax_prog_robot.m4 was added
>From b5731de25b8a1f26d7803d7a4912ba2b47a96e7c Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 04:07:02 +
Subject: [PATCH] autoconf-archive: upgrade 2019.01.06 -> 2021.02.19

---
 ...nf-archive_2019.01.06.bb => autoconf-archive_2021.02.19.bb} | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta/recipes-devtools/autoconf-archive/{autoconf-archive_2019.01.06.bb => autoconf-archive_2021.02.19.bb} (78%)

diff --git a/meta/recipes-devtools/autoconf-archive/autoconf-archive_2019.01.06.bb b/meta/recipes-devtools/autoconf-archive/autoconf-archive_2021.02.19.bb
similarity index 78%
rename from meta/recipes-devtools/autoconf-archive/autoconf-archive_2019.01.06.bb
rename to meta/recipes-devtools/autoconf-archive/autoconf-archive_2021.02.19.bb
index 13593d7bb3..54079b5f09 100644
--- a/meta/recipes-devtools/autoconf-archive/autoconf-archive_2019.01.06.bb
+++ b/meta/recipes-devtools/autoconf-archive/autoconf-archive_2021.02.19.bb
@@ -6,8 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=11cc2d3ee574f9d6b7ee797bdce4d423 \
 file://COPYING.EXCEPTION;md5=fdef168ebff3bc2f13664c365a5fb515"
 
 SRC_URI = "${GNU_MIRROR}/${BPN}/${BPN}-${PV}.tar.xz"
-SRC_URI[md5sum] = "d46413c8b00a125b1529bae385bbec55"
-SRC_URI[sha256sum] = "17195c833098da79de5778ee90948f4c5d90ed1a0cf8391b4ab348e2ec511e3f"
+SRC_URI[sha256sum] = "e8a6eb9d28ddcba8ffef3fa211653239e9bf239aba6a01a6b7cfc7ceaec69cbd"
 
 inherit autotools allarch texinfo
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149476): 
https://lists.openembedded.org/g/openembedded-core/message/149476
Mute This Topic: https://lists.openembedded.org/mt/81354089/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] cmake: upgrading to 3.19.6 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.19.6* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.19.5-3.19.6.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
>From 90fd872045be6d39d8a8372167df530e8f9e1da4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 04:47:03 +
Subject: [PATCH] cmake: upgrade 3.19.5 -> 3.19.6

---
 meta/recipes-devtools/cmake/cmake.inc |  2 +-
 ...stem-use-oe-environment-vars-to-load.patch |  2 +-
 .../cmake/cmake/OEToolchainConfig.cmake   | 25 ---
 .../cmake/cmake/environment.d-cmake.sh|  2 --
 .../{cmake_3.19.5.bb => cmake_3.19.6.bb}  | 11 
 5 files changed, 8 insertions(+), 34 deletions(-)
 delete mode 100644 meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
 delete mode 100644 meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
 rename meta/recipes-devtools/cmake/{cmake_3.19.5.bb => cmake_3.19.6.bb} (78%)

diff --git a/meta/recipes-devtools/cmake/cmake.inc b/meta/recipes-devtools/cmake/cmake.inc
index e0f59a6c67..b01e1b3b02 100644
--- a/meta/recipes-devtools/cmake/cmake.inc
+++ b/meta/recipes-devtools/cmake/cmake.inc
@@ -22,7 +22,7 @@ SRC_URI = "https://cmake.org/files/v${CMAKE_MAJOR_VERSION}/cmake-${PV}.tar.gz \
file://0004-Fail-silently-if-system-Qt-installation-is-broken.patch \
 "
 
-SRC_URI[sha256sum] = "c432296eb5dec6d71eae15d140f6297d63df44e9ffe3e453628d1dc8fc4201ce"
+SRC_URI[sha256sum] = "ec87ab67c45f47c4285f204280c5cde48e1c920cfcfed1555b27fb3b1a1d20ba"
 
 UPSTREAM_CHECK_REGEX = "cmake-(?P\d+(\.\d+)+)\.tar"
 
diff --git a/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch b/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
index 8181510324..73bdff366b 100644
--- a/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
+++ b/meta/recipes-devtools/cmake/cmake/0001-CMakeDetermineSystem-use-oe-environment-vars-to-load.patch
@@ -1,4 +1,4 @@
-From 66d5b27dc37ef6243f6549e16d0285ba6c064a6e Mon Sep 17 00:00:00 2001
+From f8937e4c7bc7f7ec591d0bce8354a2224db6403c Mon Sep 17 00:00:00 2001
 From: Cody P Schafer 
 Date: Thu, 27 Apr 2017 11:35:05 -0400
 Subject: [PATCH] CMakeDetermineSystem: use oe environment vars to load default
diff --git a/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake b/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
deleted file mode 100644
index 8f6f3a272d..00
--- a/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
+++ /dev/null
@@ -1,25 +0,0 @@
-set( CMAKE_SYSTEM_NAME Linux )
-set( CMAKE_C_FLAGS $ENV{CFLAGS} CACHE STRING "" FORCE )
-set( CMAKE_CXX_FLAGS $ENV{CXXFLAGS}  CACHE STRING "" FORCE )
-set( CMAKE_ASM_FLAGS ${CMAKE_C_FLAGS} CACHE STRING "" FORCE )
-set( CMAKE_LDFLAGS_FLAGS ${CMAKE_CXX_FLAGS} CACHE STRING "" FORCE )
-set( CMAKE_SYSROOT $ENV{OECORE_TARGET_SYSROOT} )
-
-set( CMAKE_FIND_ROOT_PATH $ENV{OECORE_TARGET_SYSROOT} )
-set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER )
-set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY )
-set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY )
-set( CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY )
-
-set(CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX "$ENV{OE_CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX}")
-
-# Set CMAKE_SYSTEM_PROCESSOR from the sysroot name (assuming processor-distro-os).
-if ($ENV{SDKTARGETSYSROOT} MATCHES "/sysroots/([a-zA-Z0-9_-]+)-.+-.+")
-  set(CMAKE_SYSTEM_PROCESSOR ${CMAKE_MATCH_1})
-endif()
-
-# Include the toolchain configuration subscripts
-file( GLOB toolchain_config_files "${CMAKE_CURRENT_LIST_FILE}.d/*.cmake" )
-foreach(config ${toolchain_config_files})
-include(${config})
-endforeach()
diff --git a/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh b/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
deleted file mode 100644
index 7bdb19fb6c..00
--- a/meta/recipes-devtools/cmake/cmake/environment.d-cmake.sh
+++ /dev/null
@@ -1,2 +0,0 @@
-export OE_CMAKE_TOOLCHAIN_FILE="$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake"
-export OE_CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX="`echo

[OE-core] [AUH] apt: upgrading to 2.2.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *apt* to *2.2.2* has Failed 
(devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe apt failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches 
to represent these
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-912eb2a4e82b8517638d3c3593bdff33a2034ea6"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:912eb2a4e82b8517638d3c3593bdff33a2034ea6"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 22 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun 
and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching http://ftp.debian.org/debian/pool/main/a/apt/apt_2.2.2.tar.xz...
Loading cache...done.
Loaded 1438 entries from dependency cache.
Parsing recipes...done.
Parsing of 815 .bb files complete (813 cached, 2 parsed). 1439 targets, 31 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-912eb2a4e82b8517638d3c3593bdff33a2034ea6"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:912eb2a4e82b8517638d3c3593bdff33a2034ea6"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Network 0 Missed 0 Current 18 (0% match, 100% 
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and 
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:   0% |   | ETA:  --:--:--
Adding changed files:  23% || ETA:  0:00:00
Adding changed files:  47% |#   | ETA:  0:00:00
Adding changed files:  71% |#   | ETA:  0:00:00
Adding changed files:  94% |##  | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00
WARNING: Command 'git rebase 878a1079446bc6efe4398368ebee0b16d62f0585' failed:
First, rewinding head to replay your work on top of it...
Applying: Disable documentation directory altogether
Using index info to reconstruct a base tree...
M   CMakeLists.txt
Falling back to patching base and 3-way merge...
Auto-merging CMakeLists.txt
Applying: Fix musl build
Applying: CMakeLists.txt: avoid changing install paths based on host distro
Applying: test/libapt: do not use gtest from the host
Using index info to reconstruct a base tree...
M   test/libapt/CMakeLists.txt
Falling back to patching base and 3-way merge...
Auto-merging test/libapt/CMakeLists.txt
CONFLICT (content): Merge conflict in test/libapt/CMakeLists.txt
error: Failed to merge in the changes.
Patch failed at 0004 test/libapt: do not use gtest from the host
Use 'git am --show-current-patch' to see the failed patch

Resolve all conflicts manually, mark them as resolved with
"git add/rm ", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase 
--abort".

You will need to resolve conflicts in order to complete the upgrade.
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/apt
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/apt/apt_2.2.2.bb




Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at

[OE-core] [AUH] automake: upgrading to 1.16.3 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *automake* to *1.16.3* has 
Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade automake -V 1.16.3
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1438 entries from dependency cache.
INFO: Extracting current version source...
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.49.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "3.2+snapshot-ffb197ef0e225571ec488baadc8603cd6a7a65f9"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:ffb197ef0e225571ec488baadc8603cd6a7a65f9"
workspace= "master:eec64066073428e38d5b0b6947ff302943188f65"

Initialising tasks...done.
Sstate summary: Wanted 5 Local 0 Network 0 Missed 5 Current 15 (0% match, 75% 
complete)
NOTE: Executing Tasks
ERROR: Command '['rm', '-rf', 
'/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-rl0bl79y/workdir/automake-1.16.2']'
 returned non-zero exit status 1.
ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-rl0bl79y/temp/log.do_unpack.48359
Log data follows:
| rm: cannot remove 
'/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-rl0bl79y/workdir/automake-1.16.2':
 Directory not empty
| ERROR: Command '['rm', '-rf', 
'/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/automake/1.16.2-r0/devtooltmp-rl0bl79y/workdir/automake-1.16.2']'
 returned non-zero exit status 1.
NOTE: Tasks Summary: Attempted 71 tasks of which 66 didn't need to be rerun and 
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
ERROR: Extracting source for automake failed



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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149477): 
https://lists.openembedded.org/g/openembedded-core/message/149477
Mute This Topic: https://lists.openembedded.org/mt/81354090/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [AUH] bind: upgrading to 9.16.12 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.16.12* has 
Failed(do_compile).

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-bind-upgrade-9.16.11-9.16.12.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
>From 22cfff5ab760c9bbd54f6c49584ff00322ea6228 Mon Sep 17 00:00:00 2001
From: Upgrade Helper 
Date: Mon, 15 Mar 2021 02:18:37 +
Subject: [PATCH] bind: upgrade 9.16.11 -> 9.16.12

---
 .../0001-avoid-start-failure-with-bind-user.patch   | 0
 .../0001-named-lwresd-V-and-start-log-hide-build-options.patch  | 0
 .../bind-ensure-searching-for-json-headers-searches-sysr.patch  | 0
 .../bind/{bind-9.16.11 => bind-9.16.12}/bind9   | 0
 .../bind/{bind-9.16.11 => bind-9.16.12}/conf.patch  | 0
 .../bind/{bind-9.16.11 => bind-9.16.12}/generate-rndc-key.sh| 0
 .../init.d-add-support-for-read-only-rootfs.patch   | 0
 .../make-etc-initd-bind-stop-work.patch | 0
 .../bind/{bind-9.16.11 => bind-9.16.12}/named.service   | 0
 .../bind/{bind_9.16.11.bb => bind_9.16.12.bb}   | 2 +-
 10 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/0001-avoid-start-failure-with-bind-user.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/bind9 (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/generate-rndc-key.sh (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/init.d-add-support-for-read-only-rootfs.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/make-etc-initd-bind-stop-work.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.16.11 => bind-9.16.12}/named.service (100%)
 rename meta/recipes-connectivity/bind/{bind_9.16.11.bb => bind_9.16.12.bb} (98%)

diff --git a/meta/recipes-connectivity/bind/bind-9.16.11/0001-avoid-start-failure-with-bind-user.patch b/meta/recipes-connectivity/bind/bind-9.16.12/0001-avoid-start-failure-with-bind-user.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.11/0001-avoid-start-failure-with-bind-user.patch
rename to meta/recipes-connectivity/bind/bind-9.16.12/0001-avoid-start-failure-with-bind-user.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.11/0001-named-lwresd-V-and-start-log-hide-build-options.patch b/meta/recipes-connectivity/bind/bind-9.16.12/0001-named-lwresd-V-and-start-log-hide-build-options.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.11/0001-named-lwresd-V-and-start-log-hide-build-options.patch
rename to meta/recipes-connectivity/bind/bind-9.16.12/0001-named-lwresd-V-and-start-log-hide-build-options.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.11/bind-ensure-searching-for-json-headers-searches-sysr.patch b/meta/recipes-connectivity/bind/bind-9.16.12/bind-ensure-searching-for-json-headers-searches-sysr.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.11/bind-ensure-searching-for-json-headers-searches-sysr.patch
rename to meta/recipes-connectivity/bind/bind-9.16.12/bind-ensure-searching-for-json-headers-searches-sysr.patch
diff --git a/meta/recipes-connectivity/bind/bind-9.16.11/bind9 b/meta/recipes-connectivity/bind/bind-9.16.12/bind9
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.11/bind9
rename to meta/recipes-connectivity/bind/bind-9.16.12/bind9
diff --git a/meta/recipes-connectivity/bind/bind-9.16.11/conf.patch b/meta/recipes-connectivity/bind/bind-9.16.12/conf.patch
similarity index 100%
rename from meta/recipes-connectivity/bind/bind-9.16.11/conf.patch
rename to meta/recipes-connectivity/bind/bind-9.16.12/conf.patch
diff --git

Re: [OE-core] Build the "boot" partition image (just like the rootfs)

2021-03-15 Thread Mike Looijmans


Hi Stefano,


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 15-03-2021 15:58, Stefano Babic wrote:

Hi Mike,

On 15.03.21 15:46, Mike Looijmans wrote:


On 15-03-2021 14:47, Stefano Babic wrote:

Hi Mike,

On 15.03.21 14:13, Mike Looijmans wrote:
For software updates, I want to have what would have gone into the 
boot partition of the WIC image as a separate file.


If I want to have the contents of the rootfs as an ext4 image, I 
can just specify IMAGE_TYPES="ext4" in my image recipe.

 > This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for 
example, the raspberrypi has the annoying property that devicetree 
and kernel reside here).


This is very annoying, but you could also get rid of it. You can 
install kernel and device tree in your rootfs (then they are located 
in /boot as usual), and you switch to U-Boot ( RPI_USE_U_BOOT = 
"1"). The proprietary bootloader will start U-Boot instead of 
kernel, and in u-boot you can load kernel and device tree from your 
rootfs.


That's what I did on other boards, but for the RPi that's not enough. 
There's also firmware there, which interacts with the kernel, and the 
firmware is altering the devicetree too. It's pretty likely that the 
firmware needs an update too when the kernel gets a big update.







If I create a WIC image, the boot partition is in there with the 
proper files (from IMAGE_BOOT_FILES) so I would really like to 
re-use that code. I could create the wic image and then cut out the 
part I want, but that doesn't seem particularly nice.


You can add vfat support for IMAGE_FSTYPES, and then you can build 
an image (you can just take the files you have in IMAGE_BOOT_FILES).


But that's *exactly* my problem: How do I get these IMAGE_BOOT_FILES 
into an image of sorts? Just setting IMAGE_FSTYPE="vfat" will put the 
rootfs contents in there, not the bootfiles I'm after.


rpi-bootfiles inherit nopackage, so you should write a recipe that 
instead of simply deploying the files as this recipe does, install 
them. You should then install it into /, as this is where they are put 
on the VFAT partition. If they are in the package, you can write an 
image recipe to install it via IMAGE_INSTALL, and via post process 
command you drop what is not necessary (/etc,...).


Anyway, as far as I know, an IMAGE_FSTYPES += "vfat" is not supported, 
you have also to add support for it.


rpi-bootfiles provides only part of the file set. The issue is that 
IMAGE_BOOT_FILES, which lists much more than what rpi-bootfiles 
provides, can be modified in the image recipe itself. It contains the 
kernel, devicetrees and configuration files as well.










What I want to do at update time is to write the new boot partition 
to another location on disk, and then adjust the partition table to 
make the first partition entry point to the new copy. That way, in 
case of unexpected failure (power loss for example), the device 
remains bootable.


This does not seem to be atomic. It remains the risk that partition 
table gets corrupted and then even the first bootloader cannot run. 
If you want to have a power-cut safe way to update is not enough.


It's not perfect but it's close enough. The partition table resides 
in a single sector, so chances of power-out at exactly this moment 
are small enough that I'm willing to take my chances here.


My experience is that there's more chance of the SD card completely 
dying because of power-out during some internal mumbojumbo than 
corrupting that partition table.


True, that is. So simply the hardware does not allow a safe update, 
point. Fully agree. Or use a very expensive industrial grade SD, but 
any board with eMMC is then cheaper.


I actually tried a few industrial grade SDs (usually SLC type). I had 
issues with those on other boards and the Pi is no exception. If I put 
one of those expensive SLC cards into the SD slot of the RPi4, there's 
about 30% chance that the board won't boot at all.





Against that SD failure there's nothing I can do...


Absolutely true.


Amen.

I'm going to let this thing rest for a while, maybe I'll come up with 
something completely different or maybe someone in this group has some 
brilliant idea...



--
Mike Looijmans


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149469): 
https://lists.openembedded.org/g/openembedded-core/message/149469
Mute This Topic: https://lists.openembedded.org/mt/81348440/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][PATCH] weston-init: Set $HOME variable for SysVinit manager. SysVinit sets by default the $HOME directory to "/" for the init scripts. It's picked then by the weston-launcher and make we

2021-03-15 Thread Adrian

This patch is wrongly formatted and should be ignored. I have already
sent a proper one.

Adrian

On 15.03.2021 15:01, Adrian Fiergolski wrote:
> Signed-off-by: Adrian Fiergolski 
> ---
>  meta/recipes-graphics/wayland/weston-init.bb   | 1 +
>  meta/recipes-graphics/wayland/weston-init/init | 1 +
>  2 files changed, 2 insertions(+)
>
> diff --git a/meta/recipes-graphics/wayland/weston-init.bb 
> b/meta/recipes-graphics/wayland/weston-init.bb
> index 65d7b81dc5..6b78e6722f 100644
> --- a/meta/recipes-graphics/wayland/weston-init.bb
> +++ b/meta/recipes-graphics/wayland/weston-init.bb
> @@ -30,6 +30,7 @@ DEFAULTBACKEND_x86-x32 = "fbdev"
>  do_install() {
>  if [ "${VIRTUAL-RUNTIME_init_manager}" != "systemd" ]; then
>   install -Dm755 ${WORKDIR}/init ${D}/${sysconfdir}/init.d/weston
> + sed -i 's#ROOTHOME#${ROOT_HOME}#' 
> ${D}/${sysconfdir}/init.d/weston
>  fi
>   install -D -p -m0644 ${WORKDIR}/weston.ini 
> ${D}${sysconfdir}/xdg/weston/weston.ini
>   install -Dm644 ${WORKDIR}/weston.env ${D}${sysconfdir}/default/weston
> diff --git a/meta/recipes-graphics/wayland/weston-init/init 
> b/meta/recipes-graphics/wayland/weston-init/init
> index d3e87c6cef..a849f29bcb 100644
> --- a/meta/recipes-graphics/wayland/weston-init/init
> +++ b/meta/recipes-graphics/wayland/weston-init/init
> @@ -30,6 +30,7 @@ done
>  case "$1" in
>start)
>  . /etc/profile
> + export HOME=ROOTHOME
>  
>  weston-start -- $OPTARGS
>;;

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149468): 
https://lists.openembedded.org/g/openembedded-core/message/149468
Mute This Topic: https://lists.openembedded.org/mt/81349618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] weston-init: Set $HOME variable for SysVinit manager.

2021-03-15 Thread Adrian

 SysVinit sets by default the $HOME directory to "/" for the init scripts.
 It's picked then by the weston-launcher and make weston-terminal to have
 wrongly set $HOME environment variable for the root user.

Signed-off-by: Adrian Fiergolski 
---
 Sorry, the previous patch far wrongly formatted.
 
 meta/recipes-graphics/wayland/weston-init.bb   | 1 +
 meta/recipes-graphics/wayland/weston-init/init | 1 +
 2 files changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/wayland/weston-init.bb 
b/meta/recipes-graphics/wayland/weston-init.bb
index 65d7b81dc5..6b78e6722f 100644
--- a/meta/recipes-graphics/wayland/weston-init.bb
+++ b/meta/recipes-graphics/wayland/weston-init.bb
@@ -30,6 +30,7 @@ DEFAULTBACKEND_x86-x32 = "fbdev"
 do_install() {
 if [ "${VIRTUAL-RUNTIME_init_manager}" != "systemd" ]; then
install -Dm755 ${WORKDIR}/init ${D}/${sysconfdir}/init.d/weston
+   sed -i 's#ROOTHOME#${ROOT_HOME}#' 
${D}/${sysconfdir}/init.d/weston
 fi
install -D -p -m0644 ${WORKDIR}/weston.ini 
${D}${sysconfdir}/xdg/weston/weston.ini
install -Dm644 ${WORKDIR}/weston.env ${D}${sysconfdir}/default/weston
diff --git a/meta/recipes-graphics/wayland/weston-init/init 
b/meta/recipes-graphics/wayland/weston-init/init
index d3e87c6cef..a849f29bcb 100644
--- a/meta/recipes-graphics/wayland/weston-init/init
+++ b/meta/recipes-graphics/wayland/weston-init/init
@@ -30,6 +30,7 @@ done
 case "$1" in
   start)
 . /etc/profile
+   export HOME=ROOTHOME
 
 weston-start -- $OPTARGS
   ;;
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149467): 
https://lists.openembedded.org/g/openembedded-core/message/149467
Mute This Topic: https://lists.openembedded.org/mt/81351162/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Build the "boot" partition image (just like the rootfs)

2021-03-15 Thread Stefano Babic


Hi Mike,

On 15.03.21 15:46, Mike Looijmans wrote:


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 15-03-2021 14:47, Stefano Babic wrote:

Hi Mike,

On 15.03.21 14:13, Mike Looijmans wrote:
For software updates, I want to have what would have gone into the 
boot partition of the WIC image as a separate file.


If I want to have the contents of the rootfs as an ext4 image, I can 
just specify IMAGE_TYPES="ext4" in my image recipe.

 > This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for example, 
the raspberrypi has the annoying property that devicetree and kernel 
reside here).


This is very annoying, but you could also get rid of it. You can 
install kernel and device tree in your rootfs (then they are located 
in /boot as usual), and you switch to U-Boot ( RPI_USE_U_BOOT = "1"). 
The proprietary bootloader will start U-Boot instead of kernel, and in 
u-boot you can load kernel and device tree from your rootfs.


That's what I did on other boards, but for the RPi that's not enough. 
There's also firmware there, which interacts with the kernel, and the 
firmware is altering the devicetree too. It's pretty likely that the 
firmware needs an update too when the kernel gets a big update.







If I create a WIC image, the boot partition is in there with the 
proper files (from IMAGE_BOOT_FILES) so I would really like to re-use 
that code. I could create the wic image and then cut out the part I 
want, but that doesn't seem particularly nice.


You can add vfat support for IMAGE_FSTYPES, and then you can build an 
image (you can just take the files you have in IMAGE_BOOT_FILES).


But that's *exactly* my problem: How do I get these IMAGE_BOOT_FILES 
into an image of sorts? Just setting IMAGE_FSTYPE="vfat" will put the 
rootfs contents in there, not the bootfiles I'm after.


rpi-bootfiles inherit nopackage, so you should write a recipe that 
instead of simply deploying the files as this recipe does, install them. 
You should then install it into /, as this is where they are put on the 
VFAT partition. If they are in the package, you can write an image 
recipe to install it via IMAGE_INSTALL, and via post process command you 
drop what is not necessary (/etc,...).


Anyway, as far as I know, an IMAGE_FSTYPES += "vfat" is not supported, 
you have also to add support for it.








What I want to do at update time is to write the new boot partition 
to another location on disk, and then adjust the partition table to 
make the first partition entry point to the new copy. That way, in 
case of unexpected failure (power loss for example), the device 
remains bootable.


This does not seem to be atomic. It remains the risk that partition 
table gets corrupted and then even the first bootloader cannot run. If 
you want to have a power-cut safe way to update is not enough.


It's not perfect but it's close enough. The partition table resides in a 
single sector, so chances of power-out at exactly this moment are small 
enough that I'm willing to take my chances here.


My experience is that there's more chance of the SD card completely 
dying because of power-out during some internal mumbojumbo than 
corrupting that partition table.


True, that is. So simply the hardware does not allow a safe update, 
point. Fully agree. Or use a very expensive industrial grade SD, but any 
board with eMMC is then cheaper.


Against that SD failure there's nothing 
I can do...


Absolutely true.

Best regards,
Stefano Babic


--
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149466): 
https://lists.openembedded.org/g/openembedded-core/message/149466
Mute This Topic: https://lists.openembedded.org/mt/81348440/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Build the "boot" partition image (just like the rootfs)

2021-03-15 Thread Mike Looijmans



Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 15-03-2021 14:47, Stefano Babic wrote:

Hi Mike,

On 15.03.21 14:13, Mike Looijmans wrote:
For software updates, I want to have what would have gone into the 
boot partition of the WIC image as a separate file.


If I want to have the contents of the rootfs as an ext4 image, I can 
just specify IMAGE_TYPES="ext4" in my image recipe.

 > This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for example, 
the raspberrypi has the annoying property that devicetree and kernel 
reside here).


This is very annoying, but you could also get rid of it. You can 
install kernel and device tree in your rootfs (then they are located 
in /boot as usual), and you switch to U-Boot ( RPI_USE_U_BOOT = "1"). 
The proprietary bootloader will start U-Boot instead of kernel, and in 
u-boot you can load kernel and device tree from your rootfs.


That's what I did on other boards, but for the RPi that's not enough. 
There's also firmware there, which interacts with the kernel, and the 
firmware is altering the devicetree too. It's pretty likely that the 
firmware needs an update too when the kernel gets a big update.







If I create a WIC image, the boot partition is in there with the 
proper files (from IMAGE_BOOT_FILES) so I would really like to re-use 
that code. I could create the wic image and then cut out the part I 
want, but that doesn't seem particularly nice.


You can add vfat support for IMAGE_FSTYPES, and then you can build an 
image (you can just take the files you have in IMAGE_BOOT_FILES).


But that's *exactly* my problem: How do I get these IMAGE_BOOT_FILES 
into an image of sorts? Just setting IMAGE_FSTYPE="vfat" will put the 
rootfs contents in there, not the bootfiles I'm after.






What I want to do at update time is to write the new boot partition 
to another location on disk, and then adjust the partition table to 
make the first partition entry point to the new copy. That way, in 
case of unexpected failure (power loss for example), the device 
remains bootable.


This does not seem to be atomic. It remains the risk that partition 
table gets corrupted and then even the first bootloader cannot run. If 
you want to have a power-cut safe way to update is not enough.


It's not perfect but it's close enough. The partition table resides in a 
single sector, so chances of power-out at exactly this moment are small 
enough that I'm willing to take my chances here.


My experience is that there's more chance of the SD card completely 
dying because of power-out during some internal mumbojumbo than 
corrupting that partition table. Against that SD failure there's nothing 
I can do...



--
Mike Looijmans


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149465): 
https://lists.openembedded.org/g/openembedded-core/message/149465
Mute This Topic: https://lists.openembedded.org/mt/81348440/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [dunfell][PATCH] cups: use /run instead /var/run in systemd's unit file

2021-03-15 Thread Steve Sakoman

On Sun, Mar 14, 2021 at 3:10 PM kai  wrote:
>
> On 3/10/21 11:09 AM, kai wrote:
>
> From: Chen Qi 
>
> /var/run has been deprecated by systemd, so use /run instead,
> as suggested by systemd.
>
> Ping.

This is in the group of patches sent for review on 3/13:

https://lists.openembedded.org/g/openembedded-core/message/149417

Steve


> [Yocto #14152]
>
> Signed-off-by: Chen Qi 
> Signed-off-by: Richard Purdie 
> (cherry picked from commit 6c3f56020da7a26c2daea73e39c2f324f1f597db)
> Signed-off-by: Kai Kang 
> ---
>  meta/recipes-extended/cups/cups.inc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-extended/cups/cups.inc 
> b/meta/recipes-extended/cups/cups.inc
> index 12780cf702..acad3c98c1 100644
> --- a/meta/recipes-extended/cups/cups.inc
> +++ b/meta/recipes-extended/cups/cups.inc
> @@ -54,6 +54,7 @@ EXTRA_OECONF = " \
> --enable-libusb \
> --with-system-groups=lpadmin \
> --with-cups-group=lp \
> +   --with-domainsocket=/run/cups/cups.sock \
> DSOFLAGS='${LDFLAGS}' \
> "
>
>
>
>
>
>
> --
> Kai Kang
> Wind River Linux
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149464): 
https://lists.openembedded.org/g/openembedded-core/message/149464
Mute This Topic: https://lists.openembedded.org/mt/81219332/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] weston-init: Set $HOME variable for SysVinit manager. SysVinit sets by default the $HOME directory to "/" for the init scripts. It's picked then by the weston-launcher and make weston

2021-03-15 Thread Adrian

Signed-off-by: Adrian Fiergolski 
---
 meta/recipes-graphics/wayland/weston-init.bb   | 1 +
 meta/recipes-graphics/wayland/weston-init/init | 1 +
 2 files changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/wayland/weston-init.bb 
b/meta/recipes-graphics/wayland/weston-init.bb
index 65d7b81dc5..6b78e6722f 100644
--- a/meta/recipes-graphics/wayland/weston-init.bb
+++ b/meta/recipes-graphics/wayland/weston-init.bb
@@ -30,6 +30,7 @@ DEFAULTBACKEND_x86-x32 = "fbdev"
 do_install() {
 if [ "${VIRTUAL-RUNTIME_init_manager}" != "systemd" ]; then
install -Dm755 ${WORKDIR}/init ${D}/${sysconfdir}/init.d/weston
+   sed -i 's#ROOTHOME#${ROOT_HOME}#' 
${D}/${sysconfdir}/init.d/weston
 fi
install -D -p -m0644 ${WORKDIR}/weston.ini 
${D}${sysconfdir}/xdg/weston/weston.ini
install -Dm644 ${WORKDIR}/weston.env ${D}${sysconfdir}/default/weston
diff --git a/meta/recipes-graphics/wayland/weston-init/init 
b/meta/recipes-graphics/wayland/weston-init/init
index d3e87c6cef..a849f29bcb 100644
--- a/meta/recipes-graphics/wayland/weston-init/init
+++ b/meta/recipes-graphics/wayland/weston-init/init
@@ -30,6 +30,7 @@ done
 case "$1" in
   start)
 . /etc/profile
+   export HOME=ROOTHOME
 
 weston-start -- $OPTARGS
   ;;
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149463): 
https://lists.openembedded.org/g/openembedded-core/message/149463
Mute This Topic: https://lists.openembedded.org/mt/81349618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

On Mon, 2021-03-15 at 14:55 +0100, Martin Jansa wrote:
> On Mon, Mar 15, 2021 at 12:21:37PM +, Richard Purdie wrote:
> > On Mon, 2021-03-15 at 11:50 +, Luca Boccassi wrote:
> > > On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> > > > On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > > > > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > > > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > > > > From: Luca Boccassi 
> > > > > > > 
> > > > > > > Recently util-linux gained an (optional) build dependency on 
> > > > > > > libcryptsetup.
> > > > > > > But libcryptsetup build-depends on util-linux for blkid 
> > > > > > > (optional, can be disabled)
> > > > > > > and uuid (mandatory).
> > > > > > > Split out util-linux-uuid in a different recipe to break the 
> > > > > > > cycle.
> > > > > > > 
> > > > > > > https://github.com/karelzak/util-linux/pull/898
> > > > > > > 
> > > > > > > Signed-off-by: Luca Boccassi 
> > > > > > 
> > > > > > Unfortunately I noticed we had a performance regression in 
> > > > > > buildtimes in 
> > > > > > recent changes. The closest I have this narrowed down to so far:
> > > > > > 
> > > > > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > > > > 
> > > > > > suggests it may be this change. I have more tests queued to confirm
> > > > > > that definitively, if so we'll have to figure out why as this 
> > > > > > shouldn't
> > > > > > really happen, its an 8% regression :(.
> > > > > 
> > > > > Very strange that a single recipe could do that - is there something
> > > > > wrong in the new .bb that I missed and could cause this?
> > > > 
> > > > I'm wondering if it is because we're building util-linux twice now and
> > > > there is some key choke point in the dependency chain. I have no 
> > > > evidence
> > > > for that yet, it is just speculation though.
> > > 
> > > With the autoconf options I've set, on my laptop it takes 32s to do
> > > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > > 
> > > Only 3 libraries are built with this combination: libcommon.a,
> > > libtcolors.a, and libuuid.a/so. No executables or anything else is
> > > built. It doesn't look like libtcolors is actually needed, I'll see if
> > > I can prepare a patch to skip it, but I don't think it will buy more
> > > than 1s, it's just two object files.
> > > 
> > > The good news is that meson support is about to land upstream, which
> > > should be significantly faster than autoconf + make:
> > > 
> > > https://github.com/karelzak/util-linux/commits/topic/meson
> > 
> > Meson definitely improves the speed! I was wondering if it was from
> > configure for example.
> > 
> > I now have more performance test results in (takes time to interleave 
> > them with testing of master):
> > 
> > https://autobuilder.yocto.io/pub/non-release/20210315-1/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210315005048_6bb1621815.html
> > 
> > and I think this means it isn't from the util-linux change but one of 
> > another three. I'm not entirely convinced those changes could do this
> > but it is what the data says. 
> > 
> > I've queued more bisection to narrow it down from there...
> 
> BTW: this split also needs manual cleanup in the TMPDIR, right?

It shouldn't. The system should spot that util-linux has changed and uninstall
it from the sysroots as it goes. There is something not working right there :(

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149462): 
https://lists.openembedded.org/g/openembedded-core/message/149462
Mute This Topic: https://lists.openembedded.org/mt/81254724/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

2021-03-15 Thread Martin Jansa

On Mon, Mar 15, 2021 at 12:21:37PM +, Richard Purdie wrote:
> On Mon, 2021-03-15 at 11:50 +, Luca Boccassi wrote:
> > On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> > > On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > > > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > > > From: Luca Boccassi 
> > > > > > 
> > > > > > Recently util-linux gained an (optional) build dependency on 
> > > > > > libcryptsetup.
> > > > > > But libcryptsetup build-depends on util-linux for blkid (optional, 
> > > > > > can be disabled)
> > > > > > and uuid (mandatory).
> > > > > > Split out util-linux-uuid in a different recipe to break the cycle.
> > > > > > 
> > > > > > https://github.com/karelzak/util-linux/pull/898
> > > > > > 
> > > > > > Signed-off-by: Luca Boccassi 
> > > > > 
> > > > > Unfortunately I noticed we had a performance regression in buildtimes 
> > > > > in 
> > > > > recent changes. The closest I have this narrowed down to so far:
> > > > > 
> > > > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > > > 
> > > > > suggests it may be this change. I have more tests queued to confirm
> > > > > that definitively, if so we'll have to figure out why as this 
> > > > > shouldn't
> > > > > really happen, its an 8% regression :(.
> > > > 
> > > > Very strange that a single recipe could do that - is there something
> > > > wrong in the new .bb that I missed and could cause this?
> > > 
> > > I'm wondering if it is because we're building util-linux twice now and
> > > there is some key choke point in the dependency chain. I have no evidence
> > > for that yet, it is just speculation though.
> > 
> > With the autoconf options I've set, on my laptop it takes 32s to do
> > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > 
> > Only 3 libraries are built with this combination: libcommon.a,
> > libtcolors.a, and libuuid.a/so. No executables or anything else is
> > built. It doesn't look like libtcolors is actually needed, I'll see if
> > I can prepare a patch to skip it, but I don't think it will buy more
> > than 1s, it's just two object files.
> > 
> > The good news is that meson support is about to land upstream, which
> > should be significantly faster than autoconf + make:
> > 
> > https://github.com/karelzak/util-linux/commits/topic/meson
> 
> Meson definitely improves the speed! I was wondering if it was from
> configure for example.
> 
> I now have more performance test results in (takes time to interleave 
> them with testing of master):
> 
> https://autobuilder.yocto.io/pub/non-release/20210315-1/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210315005048_6bb1621815.html
> 
> and I think this means it isn't from the util-linux change but one of 
> another three. I'm not entirely convinced those changes could do this
> but it is what the data says. 
> 
> I've queued more bisection to narrow it down from there...

BTW: this split also needs manual cleanup in the TMPDIR, right?

Incremental build fails with:
ERROR: util-linux-uuid-2.36.2-r0 do_packagedata: The recipe util-linux-uuid is 
trying to install files into a shared area when those files already exist. 
Those files and their manifest location are:
  /OE/build/oe-core/tmp-glibc/pkgdata/qemux86-64/shlibs2/util-linux-libuuid.list
(matched in manifest-qemux86_64-util-linux.packagedata)
  
/OE/build/oe-core/tmp-glibc/pkgdata/qemux86-64/runtime/util-linux-libuuid.packaged
(matched in manifest-qemux86_64-util-linux.packagedata)
  /OE/build/oe-core/tmp-glibc/pkgdata/qemux86-64/runtime/util-linux-libuuid
(matched in manifest-qemux86_64-util-linux.packagedata)
Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if 
not now, possibly in the future (we've seen builds fail several months later). 
If the system knew how to recover from this automatically it would, however 
there are several different scenarios which can result in this and we don't 
know which one this is. It may be you have switched providers of something like 
virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you

Re: [OE-core] Build the "boot" partition image (just like the rootfs)

2021-03-15 Thread Stefano Babic


Hi Mike,

On 15.03.21 14:13, Mike Looijmans wrote:
For software updates, I want to have what would have gone into the boot 
partition of the WIC image as a separate file.


If I want to have the contents of the rootfs as an ext4 image, I can 
just specify IMAGE_TYPES="ext4" in my image recipe.

 > This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for example, 
the raspberrypi has the annoying property that devicetree and kernel 
reside here).


This is very annoying, but you could also get rid of it. You can install 
kernel and device tree in your rootfs (then they are located in /boot as 
usual), and you switch to U-Boot ( RPI_USE_U_BOOT = "1"). The 
proprietary bootloader will start U-Boot instead of kernel, and in 
u-boot you can load kernel and device tree from your rootfs.




If I create a WIC image, the boot partition is in there with the proper 
files (from IMAGE_BOOT_FILES) so I would really like to re-use that 
code. I could create the wic image and then cut out the part I want, but 
that doesn't seem particularly nice.


You can add vfat support for IMAGE_FSTYPES, and then you can build an 
image (you can just take the files you have in IMAGE_BOOT_FILES).




What I want to do at update time is to write the new boot partition to 
another location on disk, and then adjust the partition table to make 
the first partition entry point to the new copy. That way, in case of 
unexpected failure (power loss for example), the device remains bootable.


This does not seem to be atomic. It remains the risk that partition 
table gets corrupted and then even the first bootloader cannot run. If 
you want to have a power-cut safe way to update is not enough.


Best regards,
Stefano Babic

--
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149460): 
https://lists.openembedded.org/g/openembedded-core/message/149460
Mute This Topic: https://lists.openembedded.org/mt/81348440/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [gatesgarth][PATCH] glib-2.0: Fix CVE-2021-27219

2021-03-15 Thread Anatol Belski

The upstream patches are only in glib >= 2.66.6 and >= 2.67.3 and won't
be backported. This patch is developed based on the upstream patch set
and consulting teh backports recently made by Ubuntu for the 2.64.6
series.

Signed-off-by: Anatol Belski 
---
 .../glib-2.0/glib-2.0/CVE-2021-27219.patch| 1444 +
 meta/recipes-core/glib-2.0/glib-2.0_2.64.5.bb |1 +
 2 files changed, 1445 insertions(+)
 create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219.patch

diff --git a/meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219.patch 
b/meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219.patch
new file mode 100644
index 00..a4ec01134a
--- /dev/null
+++ b/meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219.patch
@@ -0,0 +1,1444 @@
+commit b70039028b4a39ea071f6ed368a58ad5b5b90ba3
+Author: Anatol Belski 
+Date:   Sun Mar 14 17:51:53 2021 +
+
+backport: 2.64.5_CVE-2021-27219
+
+CVE: CVE-2021-27219
+Upstream-Status: Backport
+[https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1926]
+
+Signed-off-by: Anatol Belski 
+
+diff --git a/docs/reference/glib/meson.build b/docs/reference/glib/meson.build
+index 62d95f78d..7eebb04ac 100644
+--- a/docs/reference/glib/meson.build
 b/docs/reference/glib/meson.build
+@@ -22,6 +22,7 @@ if get_option('gtk_doc')
+ 'gprintfint.h',
+ 'gmirroringtable.h',
+ 'gscripttable.h',
++'gstrfuncsprivate.h',
+ 'glib-mirroring-tab',
+ 'gnulib',
+ 'pcre',
+diff --git a/gio/gdatainputstream.c b/gio/gdatainputstream.c
+index 2e7750cb5..2cdcbda19 100644
+--- a/gio/gdatainputstream.c
 b/gio/gdatainputstream.c
+@@ -27,6 +27,7 @@
+ #include "gioenumtypes.h"
+ #include "gioerror.h"
+ #include "glibintl.h"
++#include "gstrfuncsprivate.h"
+ 
+ #include 
+ 
+@@ -856,7 +857,7 @@ static gssize
+ scan_for_chars (GDataInputStream *stream,
+   gsize*checked_out,
+   const char   *stop_chars,
+-gssizestop_chars_len)
++gsize stop_chars_len)
+ {
+   GBufferedInputStream *bstream;
+   const char *buffer;
+@@ -952,7 +953,7 @@ typedef struct
+   gsize checked;
+ 
+   gchar *stop_chars;
+-  gssize stop_chars_len;
++  gsize stop_chars_len;
+   gsize length;
+ } GDataInputStreamReadData;
+ 
+@@ -1078,12 +1079,17 @@ g_data_input_stream_read_async (GDataInputStream
*stream,
+ {
+   GDataInputStreamReadData *data;
+   GTask *task;
++  gsize stop_chars_len_unsigned;
+ 
+   data = g_slice_new0 (GDataInputStreamReadData);
+-  if (stop_chars_len == -1)
+-stop_chars_len = strlen (stop_chars);
+-  data->stop_chars = g_memdup (stop_chars, stop_chars_len);
+-  data->stop_chars_len = stop_chars_len;
++
++  if (stop_chars_len < 0)
++stop_chars_len_unsigned = strlen (stop_chars);
++  else
++stop_chars_len_unsigned = (gsize) stop_chars_len;
++
++  data->stop_chars = g_memdup2 (stop_chars, stop_chars_len_unsigned);
++  data->stop_chars_len = stop_chars_len_unsigned;
+   data->last_saw_cr = FALSE;
+ 
+   task = g_task_new (stream, cancellable, callback, user_data);
+@@ -1338,17 +1344,20 @@ g_data_input_stream_read_upto (GDataInputStream  
*stream,
+   gssize found_pos;
+   gssize res;
+   char *data_until;
++  gsize stop_chars_len_unsigned;
+ 
+   g_return_val_if_fail (G_IS_DATA_INPUT_STREAM (stream), NULL);
+ 
+   if (stop_chars_len < 0)
+-stop_chars_len = strlen (stop_chars);
++stop_chars_len_unsigned = strlen (stop_chars);
++  else
++stop_chars_len_unsigned = (gsize) stop_chars_len;
+ 
+   bstream = G_BUFFERED_INPUT_STREAM (stream);
+ 
+   checked = 0;
+ 
+-  while ((found_pos = scan_for_chars (stream, , stop_chars, 
stop_chars_len)) == -1)
++  while ((found_pos = scan_for_chars (stream, , stop_chars, 
stop_chars_len_unsigned)) == -1)
+ {
+   if (g_buffered_input_stream_get_available (bstream) ==
+   g_buffered_input_stream_get_buffer_size (bstream))
+diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c
+index 1a4dae3bd..9de661bde 100644
+--- a/gio/gdbusconnection.c
 b/gio/gdbusconnection.c
+@@ -110,6 +110,7 @@
+ #include "gasyncinitable.h"
+ #include "giostream.h"
+ #include "gasyncresult.h"
++#include "gstrfuncsprivate.h"
+ #include "gtask.h"
+ #include "gmarshal-internal.h"
+ 
+@@ -4007,7 +4008,7 @@ _g_dbus_interface_vtable_copy (const 
GDBusInterfaceVTable *vtable)
+   /* Don't waste memory by copying padding - remember to update this
+* when changing struct _GDBusInterfaceVTable in gdbusconnection.h
+*/
+-  return g_memdup ((gconstpointer) vtable, 3 * sizeof (gpointer));
++  return g_memdup2 ((gconstpointer) vtable, 3 * sizeof (gpointer));
+ }
+ 
+ static void
+@@ -4024,7 +4025,7 @@ _g_dbus_subtree_vtable_copy (const GDBusSubtreeVTable 
*vtable)
+   /* Don't waste memory by copying padding - remember to update this
+* when changing struct _GDBusSubtreeVTable in gdbusconnection.h
+*/
+-  return g_memdup ((gconstpointer) vtable, 3 * sizeof (gpointer));
++  return g_memdup2

[OE-core] Build the "boot" partition image (just like the rootfs)

2021-03-15 Thread Mike Looijmans

For software updates, I want to have what would have gone into the boot 
partition of the WIC image as a separate file.


If I want to have the contents of the rootfs as an ext4 image, I can 
just specify IMAGE_TYPES="ext4" in my image recipe.


This image I can feed to SWUdate and write to the rootfs storage.

But I also want to be able to update the boot partition (for example, 
the raspberrypi has the annoying property that devicetree and kernel 
reside here).


If I create a WIC image, the boot partition is in there with the proper 
files (from IMAGE_BOOT_FILES) so I would really like to re-use that 
code. I could create the wic image and then cut out the part I want, but 
that doesn't seem particularly nice.


What I want to do at update time is to write the new boot partition to 
another location on disk, and then adjust the partition table to make 
the first partition entry point to the new copy. That way, in case of 
unexpected failure (power loss for example), the device remains bootable.



--
Mike Looijmans


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149458): 
https://lists.openembedded.org/g/openembedded-core/message/149458
Mute This Topic: https://lists.openembedded.org/mt/81348440/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

2021-03-15 Thread Luca Bocassi

On Mon, 2021-03-15 at 12:21 +, Richard Purdie wrote:
> On Mon, 2021-03-15 at 11:50 +, Luca Boccassi wrote:
> > On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> > > On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > > > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > > > From: Luca Boccassi 
> > > > > > 
> > > > > > Recently util-linux gained an (optional) build dependency on 
> > > > > > libcryptsetup.
> > > > > > But libcryptsetup build-depends on util-linux for blkid (optional, 
> > > > > > can be disabled)
> > > > > > and uuid (mandatory).
> > > > > > Split out util-linux-uuid in a different recipe to break the cycle.
> > > > > > 
> > > > > > https://github.com/karelzak/util-linux/pull/898
> > > > > > 
> > > > > > Signed-off-by: Luca Boccassi 
> > > > > 
> > > > > Unfortunately I noticed we had a performance regression in buildtimes 
> > > > > in 
> > > > > recent changes. The closest I have this narrowed down to so far:
> > > > > 
> > > > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > > > 
> > > > > suggests it may be this change. I have more tests queued to confirm
> > > > > that definitively, if so we'll have to figure out why as this 
> > > > > shouldn't
> > > > > really happen, its an 8% regression :(.
> > > > 
> > > > Very strange that a single recipe could do that - is there something
> > > > wrong in the new .bb that I missed and could cause this?
> > > 
> > > I'm wondering if it is because we're building util-linux twice now and
> > > there is some key choke point in the dependency chain. I have no evidence
> > > for that yet, it is just speculation though.
> > 
> > With the autoconf options I've set, on my laptop it takes 32s to do
> > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > 
> > Only 3 libraries are built with this combination: libcommon.a,
> > libtcolors.a, and libuuid.a/so. No executables or anything else is
> > built. It doesn't look like libtcolors is actually needed, I'll see if
> > I can prepare a patch to skip it, but I don't think it will buy more
> > than 1s, it's just two object files.
> > 
> > The good news is that meson support is about to land upstream, which
> > should be significantly faster than autoconf + make:
> > 
> > https://github.com/karelzak/util-linux/commits/topic/meson
> 
> Meson definitely improves the speed! I was wondering if it was from
> configure for example.
> 
> I now have more performance test results in (takes time to interleave 
> them with testing of master):
> 
> https://autobuilder.yocto.io/pub/non-release/20210315-1/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210315005048_6bb1621815.html
> 
> and I think this means it isn't from the util-linux change but one of 
> another three. I'm not entirely convinced those changes could do this
> but it is what the data says. 
> 
> I've queued more bisection to narrow it down from there...
> 
> Cheers,
> 
> Richard

Ok, that's good news then (at least for me!) - in the meanwhile I had a
look at automake anyway, and found out the compile time can be halved
since libcommon and libtcolors are not needed by libuuid:

https://github.com/karelzak/util-linux/pull/1262

Not sure if worth backporting, as it's just a dozen object files, the
big time chunk is from autoconf anyway.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149457): 
https://lists.openembedded.org/g/openembedded-core/message/149457
Mute This Topic: https://lists.openembedded.org/mt/81254724/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] meta-selftest: Add HOMEPAGE / DESCRIPTION

2021-03-15 Thread Dorinda

From: Dorinda Bassey 

Added HOMEPAGE and DESCRIPTION for recipes with missing
descriptions or homepage.

Signed-off-by: Dorinda Bassey 
---
 meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb  | 1 +
 .../recipes-test/git-submodule-test/git-submodule-test.bb| 1 +
 2 files changed, 2 insertions(+)

diff --git a/meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb 
b/meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb
index 9f905a5198..dcf6c8ba63 100644
--- a/meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb
+++ b/meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb
@@ -4,6 +4,7 @@
 
 SUMMARY = "GNU Aspell spell-checker"
 SECTION = "console/utils"
+HOMEPAGE = "https://ftp.gnu.org/gnu/aspell/;
 
 LICENSE = "LGPLv2 | LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
diff --git 
a/meta-selftest/recipes-test/git-submodule-test/git-submodule-test.bb 
b/meta-selftest/recipes-test/git-submodule-test/git-submodule-test.bb
index 08089b4186..9429564df4 100644
--- a/meta-selftest/recipes-test/git-submodule-test/git-submodule-test.bb
+++ b/meta-selftest/recipes-test/git-submodule-test/git-submodule-test.bb
@@ -1,4 +1,5 @@
 SUMMARY = "Test recipe for fetching git submodules"
+HOMEPAGE = "http://git.yoctoproject.org/cgit/cgit.cgi/git-submodule-test/;
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
 
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149456): 
https://lists.openembedded.org/g/openembedded-core/message/149456
Mute This Topic: https://lists.openembedded.org/mt/81347808/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [RFC][PATCH] sstatesig.py: show an error instead of warning when sstate manifest isn't found

2021-03-15 Thread Martin Jansa

On Tue, Feb 23, 2021 at 02:35:53PM +0100, Martin Jansa via 
lists.openembedded.org wrote:
> * not sure if there are some valid use-cases for missing manifest, but
>   recently I'm seeing increasing number of build failures where something
>   from native recipe is missing (seen it with pseudo, autoconf, nodejs
>   recently) and the only indication that something is wrong (before showing
>   sometimes misleading error like:
>   recipe-sysroot-native/usr/bin/node: No such file or directory
>   is this warning:
>   NOTE: Running task 7844 of 12431 
> (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_prepare_recipe_sysroot)
>   NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Started
>   WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest 
> /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot
>  not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
>   NOTE: Running task 7845 of 12431 
> (/meta-oe/meta-oe/recipes-devtools/nodejs/nodejs_12.20.2.bb:do_unpack)
>   NOTE: recipe nodejs-12.20.2-r0: task do_unpack: Started
>   WARNING: nodejs-12.20.2-r0 do_prepare_recipe_sysroot: Manifest 
> /BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-nodejs-native.populate_sysroot
>  not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
>   NOTE: recipe nodejs-12.20.2-r0: task do_prepare_recipe_sysroot: Succeeded
> 
>   if I rebuild that native dependency, then it gets fixed and I don't
>   see these failures in clean builds (as without sstate and with empty
>   TMPDIR), only in incremental builds
> 
> * but if there isn't valid reason for missing manifest file, then I think
>   it would be better to error early (or even bb.fatal())

FYI:

With bb.fatal() I'm using for my builds I got few more failures now
(which might have been silently ignored like nodejs-native in example
before), this time it was
image.do_prepare_recipe_sysroot:
  ERROR: Manifest 
TOPDIR/BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-bmap-tools-native.populate_sysroot
 not found in x86_64 x86_64_ubuntu-18.04 (variant '')?

linux-yocto.do_validate_branches
  ERROR: Manifest 
TOPDIR/BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-kern-tools-native.populate_sysroot
 not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
u-boot.do_prepare_recipe_sysroot
  ERROR: Manifest 
TOPDIR/BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-kern-tools-native.populate_sysroot
 not found in x86_64 x86_64_ubuntu-18.04 (variant '')?
busybox.do_prepare_recipe_sysroot
  NOTE: Direct dependencies are 
['TOPDIR/oe-core/meta/recipes-devtools/gcc/gcc-cross_10.2.bb:do_populate_sysroot',

'TOPDIR/oe-core/meta/recipes-devtools/gcc/gcc-runtime_10.2.bb:do_populate_sysroot',

'TOPDIR/oe-core/meta/recipes-devtools/opkg-utils/opkg-utils_0.4.3.bb:do_populate_sysroot',

'TOPDIR/oe-core/meta/recipes-core/systemd/systemd-systemctl-native.bb:do_populate_sysroot',

'TOPDIR/oe-core/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_populate_sysroot',
 'TOPDIR/oe-core/meta/recipes-core/glibc/glibc_2.33.bb:do_populate_sysroot', 
'virtual:native:TOPDIR/oe-core/meta/recipes-devtools/icecc-create-env/icecc-create-env_0.1.bb:do_populate_sysroot',

'virtual:native:TOPDIR/oe-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',

'TOPDIR/oe-core/meta/recipes-core/libxcrypt/libxcrypt_4.4.18.bb:do_populate_sysroot']
  ERROR: Manifest 
TOPDIR/BUILD/sstate-control/manifest-x86_64_ubuntu-18.04-kern-tools-native.populate_sysroot
 not found in x86_64 x86_64_ubuntu-18.04 (variant '')?

gstreamer1.0-plugins-base.do_prepare_recipe_sysroot
  ERROR: gstreamer1.0-plugins-base-1.18.3-r0 do_prepare_recipe_sysroot: 
Manifest 
TOPDIR/BUILD/sstate-control/manifest-x86_64_x86_64-nativesdk-iso-codes.populate_sysroot

And the issue with kern-tools-native was reproduced in 3 different workspaces 
on different builders
which don't share the same SSTATE_MIRROR.

I'll try to debug what happened in these cases, but it was again on jenkins 
where the workspace
was already overwritten by some other builds and the evidence might be lost 
already and last time
I've tried to reproduce this locally it never failed.

I'm pretty sure that previous successful build which left the TMPDIR as well as 
SSTATE_DIR populated was
based on oe-core b27bff26a9 (+ some local modifications) and the current 
failing once is
69f8f3e213 (+ similar local modifications), and the git log shows that 
bmap-tools, kern-tools
and iso-codes were updated in this:

$ git log --oneline b27bff26a9..69f8f3e213 | tee
69f8f3e213 bmap-tools: upgrade 3.5 -> 3.6
09cfa5ce1e spirv-tools: Replace strncpy with memcpy
f939624981 local.conf.sample.extended: sample value for SDK_PS1
81ed52f245 toolchain-scripts.bbclass: customize prompt string for SDKs
1d19b16846 sanity.bbclass: Add az fetcher to accepted URI protocols for mirrors 
sanity
7639ffed1a iso-codes: upgrade 4.5.0 -> 4.6.0
ad4e023bb3 help2man: upgrade 1.48.1 -> 1.48.2
a7d7c1412b sysklogd: upgrade 2.2.1 -> 2.2.2

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

On Mon, 2021-03-15 at 11:50 +, Luca Boccassi wrote:
> On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> > On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > > From: Luca Boccassi 
> > > > > 
> > > > > Recently util-linux gained an (optional) build dependency on 
> > > > > libcryptsetup.
> > > > > But libcryptsetup build-depends on util-linux for blkid (optional, 
> > > > > can be disabled)
> > > > > and uuid (mandatory).
> > > > > Split out util-linux-uuid in a different recipe to break the cycle.
> > > > > 
> > > > > https://github.com/karelzak/util-linux/pull/898
> > > > > 
> > > > > Signed-off-by: Luca Boccassi 
> > > > 
> > > > Unfortunately I noticed we had a performance regression in buildtimes 
> > > > in 
> > > > recent changes. The closest I have this narrowed down to so far:
> > > > 
> > > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > > 
> > > > suggests it may be this change. I have more tests queued to confirm
> > > > that definitively, if so we'll have to figure out why as this shouldn't
> > > > really happen, its an 8% regression :(.
> > > 
> > > Very strange that a single recipe could do that - is there something
> > > wrong in the new .bb that I missed and could cause this?
> > 
> > I'm wondering if it is because we're building util-linux twice now and
> > there is some key choke point in the dependency chain. I have no evidence
> > for that yet, it is just speculation though.
> 
> With the autoconf options I've set, on my laptop it takes 32s to do
> configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> 
> Only 3 libraries are built with this combination: libcommon.a,
> libtcolors.a, and libuuid.a/so. No executables or anything else is
> built. It doesn't look like libtcolors is actually needed, I'll see if
> I can prepare a patch to skip it, but I don't think it will buy more
> than 1s, it's just two object files.
> 
> The good news is that meson support is about to land upstream, which
> should be significantly faster than autoconf + make:
> 
> https://github.com/karelzak/util-linux/commits/topic/meson

Meson definitely improves the speed! I was wondering if it was from
configure for example.

I now have more performance test results in (takes time to interleave 
them with testing of master):

https://autobuilder.yocto.io/pub/non-release/20210315-1/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210315005048_6bb1621815.html

and I think this means it isn't from the util-linux change but one of 
another three. I'm not entirely convinced those changes could do this
but it is what the data says. 

I've queued more bisection to narrow it down from there...

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149454): 
https://lists.openembedded.org/g/openembedded-core/message/149454
Mute This Topic: https://lists.openembedded.org/mt/81254724/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping

2021-03-15 Thread Luca Bocassi

On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > From: Luca Boccassi 
> > > > 
> > > > Recently util-linux gained an (optional) build dependency on 
> > > > libcryptsetup.
> > > > But libcryptsetup build-depends on util-linux for blkid (optional, can 
> > > > be disabled)
> > > > and uuid (mandatory).
> > > > Split out util-linux-uuid in a different recipe to break the cycle.
> > > > 
> > > > https://github.com/karelzak/util-linux/pull/898
> > > > 
> > > > Signed-off-by: Luca Boccassi 
> > > 
> > > Unfortunately I noticed we had a performance regression in buildtimes in 
> > > recent changes. The closest I have this narrowed down to so far:
> > > 
> > > https://autobuilder.yocto.io/pub/non-release/20210314-14/testresults/buildperf-ubuntu1604/perf-ubuntu1604_master_20210314181831_d42487bf52.html
> > > 
> > > suggests it may be this change. I have more tests queued to confirm
> > > that definitively, if so we'll have to figure out why as this shouldn't
> > > really happen, its an 8% regression :(.
> > 
> > Very strange that a single recipe could do that - is there something
> > wrong in the new .bb that I missed and could cause this?
> 
> I'm wondering if it is because we're building util-linux twice now and
> there is some key choke point in the dependency chain. I have no evidence
> for that yet, it is just speculation though.

With the autoconf options I've set, on my laptop it takes 32s to do
configure + make -j2. Most of that is autoconf - make -j2 takes 8s.

Only 3 libraries are built with this combination: libcommon.a,
libtcolors.a, and libuuid.a/so. No executables or anything else is
built. It doesn't look like libtcolors is actually needed, I'll see if
I can prepare a patch to skip it, but I don't think it will buy more
than 1s, it's just two object files.

The good news is that meson support is about to land upstream, which
should be significantly faster than autoconf + make:

https://github.com/karelzak/util-linux/commits/topic/meson

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149453): 
https://lists.openembedded.org/g/openembedded-core/message/149453
Mute This Topic: https://lists.openembedded.org/mt/81254724/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a warning when login with root is disabled

2021-03-15 Thread Peter Kjellerstedt

> -Original Message-
> From: Robert Yang 
> Sent: den 15 mars 2021 03:32
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> warning when login with root is disabled
> 
> On 3/12/21 10:13 PM, Peter Kjellerstedt wrote:
> >> -Original Message-
> >> From: Robert Yang 
> >> Sent: den 9 mars 2021 09:32
> >> To: Peter Kjellerstedt ; openembedded-
> >> c...@lists.openembedded.org
> >> Subject: Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> >> warning when login with root is disabled
> >>
> >> Hi Peter,
> >>
> >> On 3/5/21 6:18 PM, Peter Kjellerstedt wrote:
>  -Original Message-
>  From: openembedded-core@lists.openembedded.org   c...@lists.openembedded.org> On Behalf Of Robert Yang
>  Sent: den 5 mars 2021 09:49
>  To: openembedded-core@lists.openembedded.org
>  Subject: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> >> warning when login with root is disabled
> 
>  Fixed:
>  EXTRA_IMAGE_FEATURES_remove = "debug-tweaks"
>  $ bitbake core-image-minimal
> 
>  Then we can't login to the system with root without any messages. Add
>  a warning makes it easy to debug.
> 
>  Signed-off-by: Robert Yang 
>  ---
> meta/classes/rootfs-postcommands.bbclass | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
> 
>  diff --git a/meta/classes/rootfs-postcommands.bbclass
> >> b/meta/classes/rootfs-postcommands.bbclass
>  index 1f27a3d07a..e4fe416ac9 100644
>  --- a/meta/classes/rootfs-postcommands.bbclass
>  +++ b/meta/classes/rootfs-postcommands.bbclass
>  @@ -147,7 +147,11 @@ read_only_rootfs_hook () {
> zap_empty_root_password () {
>   if [ -e ${IMAGE_ROOTFS}/etc/shadow ]; then
>   sed -i 's%^root::%root:*:%' >> 
>  ${IMAGE_ROOTFS}/etc/shadow
>  -fi
>  +grep -q '^root:*:' ${IMAGE_ROOTFS}/etc/shadow
> >>>
> >>> That will match any /etc/shadow file with "root:" in it. Change it to:
> >>>
> >>>   grep -q '^root:\*:' ${IMAGE_ROOTFS}/etc/shadow
> >>
> >> Thanks, I will update it.
> >>
> >>>
> >>> And make this optional. We intentionally do not have a root password
> >>> set in our
> >>
> >> I don't quite understand about "optional", when the command is:
> >>
> >> grep -q '^root:\*:' ${IMAGE_ROOTFS}/etc/shadow
> >>
> >> Then empty root password in shadow is:
> >> root::
> >>
> >> so empty root password won't be matched?
> >
> > Sorry, I was unclear. We do not have an empty password, we have
> > "root:*:..." in /etc/shadow, and we obviously do not want this warning.
> 
> Thanks, makes sense, then let's drop this patch, this patch is for
> debugging only, it doesn't matter to drop it.
> 
> I wonder how to login when the line is "root:*:..." in /etc/shadow?

In our case, you have to set a password the first time you access the product's 
web page.

> // Robert
> 
> >
> >> // Robert
> >
> > //Peter
> >
> >>> products when they are delivered due to the state law (SB-327) that
> >>> went into effect on January 1, 2020 in California, which prohibits 
> >>> default passwords to be used in IoT products.
> >>>
>  +if [ $? -eq 0 ]; then
>  +bbwarn "Login with root user is disabled since 
>  zap_empty_root_password is enabled"
>  +fi
>  +fi
>   if [ -e ${IMAGE_ROOTFS}/etc/passwd ]; then
>   sed -i 's%^root::%root:*:%' >> 
>  ${IMAGE_ROOTFS}/etc/passwd
>   fi
>  --
>  2.17.1
> >>>
> >>> //Peter

//Peter

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#149452): 
https://lists.openembedded.org/g/openembedded-core/message/149452
Mute This Topic: https://lists.openembedded.org/mt/81098576/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v11] util-linux: split uuid in separate recipe to allow bootstrapping