date:20220715

On Fri, 15 Jul 2022 at 22:42, Richard Purdie
 wrote:
> Michael basically said that we were unlikely ever to get vgem working
> with Alma. It was almalinux-9 that I was adding but I think we wait and
> evaluate the situation with 10 and then someone can send a patch if we
> can add it.

Michael, can you share the findings please? Is 10 and beyond unlikely
to fix this for some reason?
(from what I remember the problem is lack of vgem module in any of the
rhel/alma distro packages, which strangely is not a problem with
fedora)

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168138): 
https://lists.openembedded.org/g/openembedded-core/message/168138
Mute This Topic: https://lists.openembedded.org/mt/92403794/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] selftest/runtime_test/virgl: Disable for all almalinux

On Fri, 2022-07-15 at 18:13 +0200, Alexander Kanavin wrote:
> On Fri, 15 Jul 2022 at 17:59, Richard Purdie
>  wrote:
> > -if distro and distro in ['debian-9', 'debian-10', 'centos-7', 
> > 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 
> > 'almalinux-8.6']:
> > +if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 
> > 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or 
> > distro.startswith('almalinux')):
> 
> I guess almalinux-9 has also shown the same problem as 8? Should this
> be 'or distro.startswith('almalinux-8') or
> distro.startswith('almalinux-9') rather? It will be a while before 10
> is available , and that should be evaluated on its own.

Michael basically said that we were unlikely ever to get vgem working
with Alma. It was almalinux-9 that I was adding but I think we wait and
evaluate the situation with 10 and then someone can send a patch if we
can add it.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168137): 
https://lists.openembedded.org/g/openembedded-core/message/168137
Mute This Topic: https://lists.openembedded.org/mt/92403794/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] conf/local.conf.sample: mention site.conf.sample as well

Signed-off-by: Alexander Kanavin 
---
 meta/conf/local.conf.sample | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
index 589ee32665..f6be0a59d1 100644
--- a/meta/conf/local.conf.sample
+++ b/meta/conf/local.conf.sample
@@ -5,7 +5,8 @@
 # be set in this file. More adventurous users can look at
 # local.conf.sample.extended which contains other examples of configuration 
which
 # can be placed in this file but new users likely won't need any of them
-# initially.
+# initially. There's also site.conf.sample which contains examples of site 
specific
+# information such as proxy server addresses.
 #
 # Lines starting with the '#' character are commented out and in some cases the
 # default values are provided as comments to show people example syntax. 
Enabling
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168136): 
https://lists.openembedded.org/g/openembedded-core/message/168136
Mute This Topic: https://lists.openembedded.org/mt/92406680/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] package.bbclass: Fix kernel source handling when not using externalsrc

2022-07-15 Thread Alejandro Hernandez Samaniego

Previous commit c725bdb29b266 broke kernel source handling, this was due
to the code expecting the sources to be in a different directory, this did
not happen when using externalsrc since sources were found in the expected
directories.

Pass work-shared to the check to allow sources to be found in the proper
directory, allowing these to be packaged in the next step.

To test this we grabbed a commit where we knew the buildpaths
QA test should flag a file inside the kernel sources, with the previous
commit the QA warning wasnt flagged since no sources where there, with
this fix the buildpaths QA warning gets flagged properly.

Signed-off-by: Alejandro Enedino Hernandez Samaniego 
---
 meta/classes/package.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 4850134022..541bb9df93 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -561,7 +561,7 @@ def copydebugsources(debugsrcdir, sources, d):
 
 # If S isnt based on WORKDIR we can infer our sources are located 
elsewhere,
 # e.g. using externalsrc; use S as base for our dirs
-if workdir in sdir:
+if workdir in sdir or 'work-shared' in sdir:
 basedir = workbasedir
 parentdir = workparentdir
 else:
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168135): 
https://lists.openembedded.org/g/openembedded-core/message/168135
Mute This Topic: https://lists.openembedded.org/mt/92406339/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] pulseaudio: add m4-native to DEPENDS

2022-07-15 Thread Khem Raj




On 7/15/22 1:10 PM, Richard Purdie wrote:

On Fri, 2022-07-15 at 13:05 -0400, Khem Raj wrote:


On 7/15/22 7:05 AM, Ross Burton wrote:

Normally m4-native ends up in the sysroot via the toolchain, but if a
non-standard toolchain is used them m4-native may not be installed.

However Pulseaudio explicitly checks for m4 in the meson.build, so add
it to DEPENDS.


I think default toolchain dependencies should be emulated by external
toolchains too. Or perhaps m4-native should be dropped from the internal
toolchain too.


See the section in OE-Core's layer.conf:

"""
# Avoid adding bison-native to the sysroot without a specific
# dependency in the recipe. This means indirect dependencies
# (e.g. X -> Y -> binutils-cross -> bison-native) no longer meet the
# dependency incidentally. This improves determinism and avoids build
# failures when people switch to external toolchains.
# libarchive only needs e2fsprogs headers at buildtime
SSTATE_EXCLUDEDEPS_SYSROOT += "\
 .*->autoconf-native \
 .*->automake-native \
 .*->bison-native \
"""

If we add m4-native to that list, it would do that. Just need someone
to work through all the failures it might generate.


interesting. m4 is mostly used by autotools based packages barring few 
exception like pulseaudio, Maybe moving m4 dependency to autotools class 
might be able to address most of fallouts.




Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168134): 
https://lists.openembedded.org/g/openembedded-core/message/168134
Mute This Topic: https://lists.openembedded.org/mt/92398180/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] pulseaudio: add m4-native to DEPENDS

On Fri, 2022-07-15 at 13:05 -0400, Khem Raj wrote:
> 
> On 7/15/22 7:05 AM, Ross Burton wrote:
> > Normally m4-native ends up in the sysroot via the toolchain, but if a
> > non-standard toolchain is used them m4-native may not be installed.
> > 
> > However Pulseaudio explicitly checks for m4 in the meson.build, so add
> > it to DEPENDS.
> 
> I think default toolchain dependencies should be emulated by external 
> toolchains too. Or perhaps m4-native should be dropped from the internal 
> toolchain too.

See the section in OE-Core's layer.conf:

"""
# Avoid adding bison-native to the sysroot without a specific
# dependency in the recipe. This means indirect dependencies
# (e.g. X -> Y -> binutils-cross -> bison-native) no longer meet the
# dependency incidentally. This improves determinism and avoids build
# failures when people switch to external toolchains.
# libarchive only needs e2fsprogs headers at buildtime
SSTATE_EXCLUDEDEPS_SYSROOT += "\
.*->autoconf-native \
.*->automake-native \
.*->bison-native \
"""

If we add m4-native to that list, it would do that. Just need someone
to work through all the failures it might generate.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168133): 
https://lists.openembedded.org/g/openembedded-core/message/168133
Mute This Topic: https://lists.openembedded.org/mt/92398180/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] pulseaudio: add m4-native to DEPENDS

2022-07-15 Thread Khem Raj




On 7/15/22 7:05 AM, Ross Burton wrote:

Normally m4-native ends up in the sysroot via the toolchain, but if a
non-standard toolchain is used them m4-native may not be installed.

However Pulseaudio explicitly checks for m4 in the meson.build, so add
it to DEPENDS.


I think default toolchain dependencies should be emulated by external 
toolchains too. Or perhaps m4-native should be dropped from the internal 
toolchain too.




Signed-off-by: Ross Burton 
---
  meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc 
b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
index 602d7263ce8..6055a9ebadb 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
@@ -61,7 +61,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=0e5cd938de1a7a53ea5adac38cc10c39 \
  "
  
  # libtool is needed for libltdl, used in module loading.

-DEPENDS = "libatomic-ops libsndfile1 libtool"
+DEPENDS = "m4-native libatomic-ops libsndfile1 libtool"
  # optional
  DEPENDS += "udev alsa-lib glib-2.0"
  DEPENDS += "speexdsp libxml-parser-perl-native libcap"






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168132): 
https://lists.openembedded.org/g/openembedded-core/message/168132
Mute This Topic: https://lists.openembedded.org/mt/92398180/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] curl: Fix determinism issues in ptest package

NROFF can take different values depending on the filesystem layout of the
host system and this leaks onto the target ptest package through the
Makefiles. Since ptest doesn't use them, delete them to resovle that issue.

Also ensure the task can rerun even if it already deleted configurehelp.pm

Signed-off-by: Richard Purdie 
---
 meta/recipes-support/curl/curl_7.84.0.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/curl/curl_7.84.0.bb 
b/meta/recipes-support/curl/curl_7.84.0.bb
index 28b09ef0173..75417cd1bc5 100644
--- a/meta/recipes-support/curl/curl_7.84.0.bb
+++ b/meta/recipes-support/curl/curl_7.84.0.bb
@@ -93,9 +93,10 @@ do_compile_ptest() {
 
 do_install_ptest() {
cat  ${WORKDIR}/disable-tests >> ${S}/tests/data/DISABLED
-   rm  ${B}/tests/configurehelp.pm
+   rm -f ${B}/tests/configurehelp.pm
cp -rf ${B}/tests ${D}${PTEST_PATH}
cp -rf ${S}/tests ${D}${PTEST_PATH}
+   find ${D}${PTEST_PATH}/ -type f -name Makefile.am -o -name Makefile.in 
-o -name Makefile -delete
install -d ${D}${PTEST_PATH}/src
ln -sf ${bindir}/curl   ${D}${PTEST_PATH}/src/curl
cp -rf ${D}${bindir}/curl-config ${D}${PTEST_PATH}
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168131): 
https://lists.openembedded.org/g/openembedded-core/message/168131
Mute This Topic: https://lists.openembedded.org/mt/92405342/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] gcc-runtime: Fix build when using gold

2022-07-15 Thread Khem Raj




On 7/14/22 5:15 AM, Richard Purdie wrote:

If gold is enabled as the default linker, it errors trying to link
to our dummy library empty file and this turns off things which should
be present in libstdc++.

For example, _GLIBCXX_HAVE_S_ISREG isn't defined and HAVE_S_ISREG in
libstdc++-v3/config.h isn't set properly.

Instead of just creating an empty file, create an empty elf binary
instead which addresses the issue.

Signed-off-by: Richard Purdie 
---
  meta/recipes-devtools/gcc/gcc-runtime.inc | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc 
b/meta/recipes-devtools/gcc/gcc-runtime.inc
index c39a0caf8a7..7e920df2d34 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -68,7 +68,8 @@ do_configure () {
# libstdc++ isn't built yet so CXX would error not able to find it 
which breaks stdc++'s configure
# tests. Create a dummy empty lib for the purposes of configure.
mkdir -p ${WORKDIR}/dummylib
-   touch ${WORKDIR}/dummylib/libstdc++.so
+   touch ${WORKDIR}/dummylib/dummylib.c
+   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o 
${WORKDIR}/dummylib/libstdc++.so


you can improve it a little by using a one liner

${CC} -x c /dev/null -shared -o ${WORKDIR}/dummylib/libstdc++.so


for d in libgcc ${RUNTIMETARGET}; do
echo "Configuring $d"
rm -rf ${B}/${TARGET_SYS}/$d/






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168130): 
https://lists.openembedded.org/g/openembedded-core/message/168130
Mute This Topic: https://lists.openembedded.org/mt/92375338/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] python3-docutils: upgrade 0.18.1 -> 0.19

On Fri, 15 Jul 2022 at 18:41, Richard Purdie
 wrote:
> > License-Update:
> >  year updated to 2022
> >  url of some reposity and license changed
> >  exceptions of BSD 2-Clause License changed
>
> This last bit sounds a little worrying. Is the code still under BSD-2-
> Clause? How did the exceptions change? Were new ones added or removed?
> Does it change the license?

In cases like this it usually helps to include a link to the commit on
the web (e.g. github) where the changes are. If there are several
commits between the two releases, then include all of them, there's
usually a way to browse history per-file.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168129): 
https://lists.openembedded.org/g/openembedded-core/message/168129
Mute This Topic: https://lists.openembedded.org/mt/92328558/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] python3-docutils: upgrade 0.18.1 -> 0.19

On Tue, 2022-07-12 at 15:44 +0800, wangmy wrote:
> License-Update:
>  year updated to 2022
>  url of some reposity and license changed
>  exceptions of BSD 2-Clause License changed

This last bit sounds a little worrying. Is the code still under BSD-2-
Clause? How did the exceptions change? Were new ones added or removed?
Does it change the license?

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168128): 
https://lists.openembedded.org/g/openembedded-core/message/168128
Mute This Topic: https://lists.openembedded.org/mt/92328558/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] local.conf.sample: Mention other MACHINE options may exist

Mention other MACHINE options exist and where to look for them. Based
on an idea from Robert P. J. Day but adjusted not to use urls but to
refer to the local metadata.

Signed-off-by: Richard Purdie 
---
 meta/conf/local.conf.sample | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
index c05691de581..589ee32665b 100644
--- a/meta/conf/local.conf.sample
+++ b/meta/conf/local.conf.sample
@@ -29,6 +29,10 @@
 # This sets the default machine to be qemux86-64 if no other machine is 
selected:
 MACHINE ??= "qemux86-64"
 
+# These are some of the more commonly used values. Looking at the files in the
+# meta/conf/machine directory, or the conf/machine directory of any additional 
layers
+# you add in will show all the available machines.
+
 #
 # Where to place downloads
 #
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168127): 
https://lists.openembedded.org/g/openembedded-core/message/168127
Mute This Topic: https://lists.openembedded.org/mt/92404707/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/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

On Fri, 15 Jul 2022 at 18:24, Richard Purdie
 wrote:
> In that sense, it was something a user would provide, not something
> that would be provisioned by automated scripting. If there are settings
> to be provisioned by a layer, we have local.conf for that? Why do we
> need another file too?

Right, I'm ok with organizational proxies and servers going into
local.conf. Then site.conf.sample and local.conf.extended.sample
should be promoted in the banner when setting up from the meta-poky
template.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168126): 
https://lists.openembedded.org/g/openembedded-core/message/168126
Mute This Topic: https://lists.openembedded.org/mt/92212803/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/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

On Fri, 2022-07-15 at 18:15 +0200, Alexander Kanavin wrote:
> On Fri, 15 Jul 2022 at 16:42, Richard Purdie
>  wrote:
> > We'd always intended that site.conf was more something the user would
> > setup once for their environment and not need to change. It was
> > therefore deliberately left out of the auto-setup piece.
> 
> I don't think I understand this point in particular. If site.conf is
> copied once into a newly created, empty build directory, why is that
> problematic?

Originally, we actually wanted this to be something like from the
user's homedir, i.e. things they really would setup just once.

Doing that has downsides in that if not careful, things can "leak" into
a build unexpectedly too so we never did end up enabling it from $HOME.
I do still think of it that way though.

In that sense, it was something a user would provide, not something
that would be provisioned by automated scripting. If there are settings
to be provisioned by a layer, we have local.conf for that? Why do we
need another file too?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168125): 
https://lists.openembedded.org/g/openembedded-core/message/168125
Mute This Topic: https://lists.openembedded.org/mt/92212803/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/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

On Fri, 15 Jul 2022 at 16:42, Richard Purdie
 wrote:
> We'd always intended that site.conf was more something the user would
> setup once for their environment and not need to change. It was
> therefore deliberately left out of the auto-setup piece.

I don't think I understand this point in particular. If site.conf is
copied once into a newly created, empty build directory, why is that
problematic?

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168124): 
https://lists.openembedded.org/g/openembedded-core/message/168124
Mute This Topic: https://lists.openembedded.org/mt/92212803/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] selftest/runtime_test/virgl: Disable for all almalinux

2022-07-15 Thread Ranjitsinh Rathod via lists.openembedded.org

On Fri, 15 Jul 2022 at 17:59, Richard Purdie
 wrote:
> -if distro and distro in ['debian-9', 'debian-10', 'centos-7', 
> 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 'almalinux-8.6']:
> +if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 
> 'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or 
> distro.startswith('almalinux')):

I guess almalinux-9 has also shown the same problem as 8? Should this
be 'or distro.startswith('almalinux-8') or
distro.startswith('almalinux-9') rather? It will be a while before 10
is available , and that should be evaluated on its own.

Alex

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

[OE-Core][dunfell][PATCH] cve-extra-exclusions.inc: Use CVE_CHECK_WHITELIST

Use CVE_CHECK_WHITELIST as CVE_CHECK_IGNORE is not valid on dunfell
branch

Signed-off-by: Ranjitsinh Rathod 
Signed-off-by: Ranjitsinh Rathod 
---
 meta/conf/distro/include/cve-extra-exclusions.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/conf/distro/include/cve-extra-exclusions.inc 
b/meta/conf/distro/include/cve-extra-exclusions.inc
index 70442df991..f3490db9dd 100644
--- a/meta/conf/distro/include/cve-extra-exclusions.inc
+++ b/meta/conf/distro/include/cve-extra-exclusions.inc
@@ -57,19 +57,19 @@ CVE-2016-0689 CVE-2016-0692 CVE-2016-0694 CVE-2016-3418 
CVE-2020-2981"
 # There was a proposed patch 
https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06098.html
 # qemu maintainers say the patch is incorrect and should not be applied
 # Ignore from OE's perspectivee as the issue is of low impact, at worst 
sitting in an infinite loop rather than exploitable
-CVE_CHECK_IGNORE += "CVE-2021-20255"
+CVE_CHECK_WHITELIST += "CVE-2021-20255"

 # qemu:qemu-native:qemu-system-native 
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-12067
 # There was a proposed patch but rejected by upstream qemu. It is unclear if 
the issue can
 # still be reproduced or where exactly any bug is.
 # Ignore from OE's perspective as we'll pick up any fix when upstream accepts 
one.
-CVE_CHECK_IGNORE += "CVE-2019-12067"
+CVE_CHECK_WHITELIST += "CVE-2019-12067"

 # nasm:nasm-native 
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-18974
 # It is a fuzzing related buffer overflow. It is of low impact since most 
devices
 # wouldn't expose an assembler. The upstream is inactive and there is little 
to be
 # done about the bug, ignore from an OE perspective.
-CVE_CHECK_IGNORE += "CVE-2020-18974"
+CVE_CHECK_WHITELIST += "CVE-2020-18974"



--
2.17.1

This message contains information that may be privileged or confidential and is 
the property of the KPIT Technologies Ltd. It is intended only for the person 
to whom it is addressed. If you are not the intended recipient, you are not 
authorized to read, print, retain copy, disseminate, distribute, or use this 
message or any part thereof. If you receive this message in error, please 
notify the sender immediately and delete all copies of this message. KPIT 
Technologies Ltd. does not accept any liability for virus infected mails.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168122): 
https://lists.openembedded.org/g/openembedded-core/message/168122
Mute This Topic: https://lists.openembedded.org/mt/92403999/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/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

On Fri, 15 Jul 2022 at 16:42, Richard Purdie
 wrote:
> We'd always intended that site.conf was more something the user would
> setup once for their environment and not need to change. It was
> therefore deliberately left out of the auto-setup piece.
> I hadn't remembered we have an sample version of it. I think a sample
> is fine as an example of how a site might setup a shared downloads
> directory or common proxy information but I don't think the layer
> should be installing it, particularly if it can trample an existing
> file which I think the patch could as it stands.

Ah I see where the problem is: the sample file is installed subject to
existence of local.conf in the destination build directory, which is
ok most of the time, but not all of the time. It should check for
existence of site.conf.

The idea is to serve two use cases:
- when setting up a build from the poky template, there's a sample
file installed. Same as local.conf.sample, we give users something to
play with via commented out examples. They'll never find it in
meta-poky/conf, even you had no idea it's there :)
- when setting up a build from an organizational template, the right
servers get configured without any extra steps. Ross pointed out that
can be achieved with 'meta-product/conf/site.conf', but that can't be
edited when needed, and can't be used to configure different settings
for different builds (e.g. where the caches are - such things can be
under access control restrictions).

I think this is worth reworking and making the commit message clearer.
Or we should come up with a different way to provide 'official' way to
set up site.conf, because otherwise it's back to 'write a custom
script'.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168121): 
https://lists.openembedded.org/g/openembedded-core/message/168121
Mute This Topic: https://lists.openembedded.org/mt/92212803/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] selftest/runtime_test/virgl: Disable for all almalinux

We can't support vgem on RHEL derived distros so disable this test for
all almalinux hosts rather than specific versions.

Signed-off-by: Richard Purdie 
---
 meta/lib/oeqa/selftest/cases/runtime_test.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py 
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index 8eacde40adb..857737f730c 100644
--- a/meta/lib/oeqa/selftest/cases/runtime_test.py
+++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
@@ -252,7 +252,7 @@ class TestImage(OESelftestTestCase):
 import subprocess, os
 
 distro = oe.lsb.distro_identifier()
-if distro and distro in ['debian-9', 'debian-10', 'centos-7', 
'centos-8', 'ubuntu-16.04', 'ubuntu-18.04', 'almalinux-8.5', 'almalinux-8.6']:
+if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 
'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or distro.startswith('almalinux')):
 self.skipTest('virgl headless cannot be tested with %s' %(distro))
 
 render_hint = """If /dev/dri/renderD* is absent due to lack of 
suitable GPU, 'modprobe vgem' will create one suitable for mesa llvmpipe 
software renderer."""
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168120): 
https://lists.openembedded.org/g/openembedded-core/message/168120
Mute This Topic: https://lists.openembedded.org/mt/92403794/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] rt-tests: upgrading to 2.4 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe rt-tests failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-671df67863826d9e91415bf85671df1512d30457"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:671df67863826d9e91415bf85671df1512d30457"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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 current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto ca4a6293da23ad0fd708ea1fecb2d465a9ea6093
WARNING: Command 'git rebase ca4a6293da23ad0fd708ea1fecb2d465a9ea6093' failed:
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile

You will need to resolve conflicts in order to complete the upgrade.
INFO: Using source tree as build directory since that would be the default for 
this recipe
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/rt-tests
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/rt-tests/rt-tests_git.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 (#168108): 
https://lists.openembedded.org/g/openembedded-core/message/168108
Mute This Topic: https://lists.openembedded.org/mt/92403756/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] linux-firmware: upgrading to 20220708 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  upgrade linux-firmware -V 20220708
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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:  77% |### | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://cdn.kernel.org/pub/linux/kernel/firmware/linux-firmware-20220708.tar.xz...
INFO: Rebasing devtool onto 7c9ff48e3f884622c139dd841136a8430d0963e1
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/upgrade.py",
 line 568, in upgrade
new_licenses = _extract_licenses(srctree_s, (rd.getVar('LIC_FILES_CHKSUM') 
or ""))
  File 
"/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/upgrade.py",
 line 469, in _extract_licenses
with open(os.path.join(srcpath, path), 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/linux-firmware/LICENCE.i2400m'


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.

[OE-core] [AUH] Upgrade status: 2022-07-15

Recipe upgrade statistics:

* Failed (devtool error): 16
efibootmgr, 18, Ross Burton 
systemd, 251.3, Chen Qi 
rpm, 4.17.1, Unassigned 
gcr, 3.90.0, Alexander Kanavin 
libva-initial, 2.15.0, Anuj Mittal 
libva-utils, 2.15.0, Anuj Mittal 
xev, 1.2.5, Unassigned 
xmodmap, 1.0.11, Unassigned 
xf86-input-keyboard, 2.0.0, Unassigned 
xf86-input-synaptics, 1.9.2, Unassigned 
xf86-video-cirrus, 1.6.0, Unassigned 
encodings, 1.0.6, Unassigned 
font-util, 1.3.3, Unassigned 
linux-firmware, 20220708, Otavio Salvador 

rt-tests, 2.4, Alexander Kanavin 
libgit2, 1.5.0, Unassigned 
* Failed(do_compile): 5
u-boot-tools, 2022.07, Marek Vasut 
u-boot, 2022.07, Marek Vasut 
go-runtime, 1.18.4, Khem Raj 
go, 1.18.4, Khem Raj 
llvm, 14.0.6, Khem Raj 
* Succeeded: 35
libuv, 1.44.2, Armin Kuster 
systemd-boot, 251.3, Chen Qi 
git, 2.37.1, Robert Yang 
log4cplus, 2.0.8, Unassigned 
meson, 0.63.0, Alexander Kanavin 
mmc-utils, 0.1-new-commits-available, Anuj Mittal 

python3-docutils, 0.19, Oleksandr Kravchuk 

python3-dtschema, 2022.7, Bruce Ashfield 
python3-hypothesis, 6.50.1, Tim Orling 
python3-jsonschema, 4.7.2, Bruce Ashfield 
python3-setuptools-rust, 1.4.1, Tim Orling 
python3-setuptools-scm, 7.0.5, Tim Orling 
python3-setuptools, 63.2.0, Oleksandr Kravchuk 

python3-zipp, 3.8.1, Tim Orling 
vala, 0.56.2, Alexander Kanavin 
hdparm, 9.64, Denys Dmytriyenko 
libidn2, 2.3.3, Ross Burton 
epiphany, 42.3, Alexander Kanavin 
libhandy, 1.6.3, Alexander Kanavin 
libnotify, 0.8.0, Anuj Mittal 
libdrm, 2.4.112, Otavio Salvador 
libva, 2.15.0, Anuj Mittal 
pango, 1.50.8, Ross Burton 
piglit, 1.0-new-commits-available, Ross Burton 
wayland-protocols, 1.26, Denys Dmytriyenko 
xserver-xorg, 21.1.4, Unassigned 
xwayland, 22.1.3, Unassigned 
alsa-lib, 1.2.7.2, Michael Opdenacker 
alsa-ucm-conf, 1.2.7.2, Michael Opdenacker 

mpg123, 1.30.1, Alexander Kanavin 
hwlatdetect, 2.4, Alexander Kanavin 
webkitgtk, 2.36.4, Alexander Kanavin 
diffoscope, 218, Joshua Watt 
libnl, 3.7.0, Alexander Kanavin 
sqlite3, 3.39.1, Anuj Mittal 
* Failed(other errors): 1
vulkan-samples, git-new-commits-available, Ross Burton 


TOTAL: attempted=57 succeeded=35(61.40%) failed=22(38.60%)

Recipe upgrade statistics per Maintainer:

Marek Vasut 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168118): 
https://lists.openembedded.org/g/openembedded-core/message/168118
Mute This Topic: https://lists.openembedded.org/mt/92403766/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] hwlatdetect: upgrading to 2.4 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-hwlatdetect-upgrade-2.3-2.4.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-dbg: PV changed from "2.3" 
to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-dbg: PKGV changed from 2.3 
[default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-dev: PV changed from "2.3" 
to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-dev: PKGV changed from 2.3 
[default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-doc: PV changed from "2.3" 
to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-doc: PKGV changed from 2.3 
[default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-locale: PV changed from 
"2.3" to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-locale: PKGV changed from 
2.3 [default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-src: PV changed from "2.3" 
to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-src: PKGV changed from 2.3 
[default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-staticdev: PV changed from 
"2.3" to "2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect-staticdev: PKGV changed 
from 2.3 [default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect: PV changed from "2.3" to 
"2.4"
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect: PKGSIZE changed from 
16555 to 17231 (+4%)
packages/core2-32-poky-linux/hwlatdetect/hwlatdetect: PKGV changed from 2.3 
[default] to 2.4 [default]
packages/core2-32-poky-linux/hwlatdetect: PKGV changed from 2.3 [default] to 
2.4 [default]
packages/core2-32-poky-linux/hwlatdetect: PV changed from "2.3" to "2.4"


0001-hwlatdetect-upgrade-2.3-2.4.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168109): 
https://lists.openembedded.org/g/openembedded-core/message/168109
Mute This Topic: https://lists.openembedded.org/mt/92403757/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] alsa-ucm-conf: upgrading to 1.2.7.2 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-ucm-conf* to *1.2.7.2* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-alsa-ucm-conf-upgrade-1.2.7.1-1.2.7.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/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf-src: PV changed from 
"1.2.7.1" to "1.2.7.2"
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf-src: PKGV changed from 
1.2.7.1 [default] to 1.2.7.2 [default]
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PKGSIZE changed from 
250268 to 254123 (+2%)
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PV changed from "1.2.7.1" 
to "1.2.7.2"
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: PKGV changed from 1.2.7.1 
[default] to 1.2.7.2 [default]
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: FILELIST: removed 
"/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf", added 
"/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0009.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0003.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0009.conf 
/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1-Mixer.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0003.conf"
packages/all-poky-linux/alsa-ucm-conf: PV changed from "1.2.7.1" to "1.2.7.2"
packages/all-poky-linux/alsa-ucm-conf: SRC_URI changed from 
"https://www.alsa-project.org/files/pub/lib/alsa-ucm-conf-1.2.7.1.tar.bz2; to 
"https://www.alsa-project.org/files/pub/lib/alsa-ucm-conf-1.2.7.2.tar.bz2;
packages/all-poky-linux/alsa-ucm-conf: PKGV changed from 1.2.7.1 [default] to 
1.2.7.2 [default]
Changes to packages/all-poky-linux/alsa-ucm-conf (sysroot):
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0003.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0009.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0003.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0009.conf was added
  /usr/share/alsa/ucm2/USB-Audio/NativeInstruments was added
  /usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1.conf was 
added
  
/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1-Mixer.conf 
was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf was removed
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf was removed
packages/all-poky-linux/alsa-ucm-conf/alsa-ucm-conf: FILELIST: removed 
"/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf", added 
"/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0003.conf 
/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1-Mixer.conf 
/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0009.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0009.conf 
/usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0003.conf"
Changes to packages/all-poky-linux/alsa-ucm-conf (sysroot):
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0003.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0009.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0003.conf was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi-0009.conf was added
  /usr/share/alsa/ucm2/USB-Audio/NativeInstruments was added
  /usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1.conf was 
added
  
/usr/share/alsa/ucm2/USB-Audio/NativeInstruments/Traktor-Kontrol-Z1-Mixer.conf 
was added
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4.conf was removed
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-HiFi.conf was removed


0001-alsa-ucm-conf-upgrade-1.2.7.1-1.2.7.2.patch
Description: Binary data

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

[OE-core] [AUH] xf86-input-keyboard: upgrading to 2.0.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xf86-input-keyboard* to 
*2.0.0* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade xf86-input-keyboard -V 2.0.0
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/driver/xf86-input-keyboard-2.0.0.tar.bz2,
 attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/driver/xf86-input-keyboard-2.0.0.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a_5ub/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a_5ub/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a_5ub/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a_5ub/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a_5ub/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-4p1a
 
_5ub/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/xf86-input-keyboard-2.0.0.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads

[OE-core] [AUH] xwayland: upgrading to 22.1.3 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-xwayland-upgrade-22.1.2-22.1.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/xwayland: PKGV changed from 22.1.2 [default] to 
22.1.3 [default]
packages/core2-32-poky-linux/xwayland: PV changed from "22.1.2" to "22.1.3"
packages/core2-32-poky-linux/xwayland: SRC_URI changed from 
"https://www.x.org/archive/individual/xserver/xwayland-22.1.2.tar.xz; to 
"https://www.x.org/archive/individual/xserver/xwayland-22.1.3.tar.xz;
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PV changed from "22.1.2" to 
"22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland-dbg: PKGSIZE changed from 
10262652 to 10267572 (+0%)
packages/core2-32-poky-linux/xwayland/xwayland-dev: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-dev: PV changed from "22.1.2" to 
"22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland-doc: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-doc: PV changed from "22.1.2" to 
"22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland-locale: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-locale: PV changed from "22.1.2" 
to "22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland-src: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-src: PV changed from "22.1.2" to 
"22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland-src: PKGSIZE changed from 
8590421 to 8593951 (+0%)
packages/core2-32-poky-linux/xwayland/xwayland-staticdev: PKGV changed from 
22.1.2 [default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland-staticdev: PV changed from 
"22.1.2" to "22.1.3"
packages/core2-32-poky-linux/xwayland/xwayland: PKGV changed from 22.1.2 
[default] to 22.1.3 [default]
packages/core2-32-poky-linux/xwayland/xwayland: PV changed from "22.1.2" to 
"22.1.3"


0001-xwayland-upgrade-22.1.2-22.1.3.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168106): 
https://lists.openembedded.org/g/openembedded-core/message/168106
Mute This Topic: https://lists.openembedded.org/mt/92403754/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-samples: upgrading to 5d9a1e5e66d9597a9f2b7bbc64f254436298e75b FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to 
*5d9a1e5e66d9597a9f2b7bbc64f254436298e75b* has Failed(other errors).

Detailed error information:

'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 889 .bb files complete (0 cached, 889 parsed). 1660 targets, 36 
skipped, 0 masked, 0 errors.
Removing 65 recipes from the core2-32 sysroot...done.
Removing 76 recipes from the qemux86 sysroot...done.

Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.

/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: Nothing PROVIDES 'vulkan-samples'
vulkan-samples was skipped: incompatible with host i686-poky-linux (not in 
COMPATIBLE_HOST)


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 (#168105): 
https://lists.openembedded.org/g/openembedded-core/message/168105
Mute This Topic: https://lists.openembedded.org/mt/92403753/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] libnl: upgrading to 3.7.0 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-libnl-upgrade-3.6.0-3.7.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/libnl: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl: PKGV changed from 3.6.0 [default] to 3.7.0 
[default]
packages/core2-32-poky-linux/libnl: SRC_URI changed from 
"https://github.com/thom311/libnl/releases/download/libnl3_6_0/libnl-3.6.0.tar.gz
 file://enable-serial-tests.patch file://run-ptest 
file://fa7f97f8982544c4fcb403893bae6701230d5165.patch" to 
"https://github.com/thom311/libnl/releases/download/libnl3_7_0/libnl-3.7.0.tar.gz
 file://enable-serial-tests.patch file://run-ptest"
packages/core2-32-poky-linux/libnl/libnl-cli: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl/libnl-cli: PKGV changed from 3.6.0 [default] 
to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-dbg: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl/libnl-dbg: PKGV changed from 3.6.0 [default] 
to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-dbg: PKGSIZE changed from 4096748 to 
4215168 (+3%)
packages/core2-32-poky-linux/libnl/libnl-dev: FILELIST: added 
"/usr/include/libnl3/netlink/route/act/nat.h"
packages/core2-32-poky-linux/libnl/libnl-dev: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl/libnl-dev: PKGV changed from 3.6.0 [default] 
to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-dev: PKGSIZE changed from 284493 to 
286366 (+1%)
packages/core2-32-poky-linux/libnl/libnl-doc: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl/libnl-doc: PKGV changed from 3.6.0 [default] 
to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-genl: PV changed from "3.6.0" to 
"3.7.0"
packages/core2-32-poky-linux/libnl/libnl-genl: PKGV changed from 3.6.0 
[default] to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-idiag: PV changed from "3.6.0" to 
"3.7.0"
packages/core2-32-poky-linux/libnl/libnl-idiag: PKGV changed from 3.6.0 
[default] to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-locale: PV changed from "3.6.0" to 
"3.7.0"
packages/core2-32-poky-linux/libnl/libnl-locale: PKGV changed from 3.6.0 
[default] to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-nf: PV changed from "3.6.0" to "3.7.0"
packages/core2-32-poky-linux/libnl/libnl-nf: PKGV changed from 3.6.0 [default] 
to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-ptest: PV changed from "3.6.0" to 
"3.7.0"
packages/core2-32-poky-linux/libnl/libnl-ptest: PKGV changed from 3.6.0 
[default] to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-ptest: PKGSIZE changed from 450127 to 
539151 (+20%)
packages/core2-32-poky-linux/libnl/libnl-route: PV changed from "3.6.0" to 
"3.7.0"
packages/core2-32-poky-linux/libnl/libnl-route: PKGV changed from 3.6.0 
[default] to 3.7.0 [default]
packages/core2-32-poky-linux/libnl/libnl-route: PKGSIZE changed from 640513 to 
648801 (+1%)
packages/core2-32-poky-linux/libnl/libnl-src: FILELIST: directory renamed 
/usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/lib/route -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/lib/route, directory renamed 
/usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/include/netlink -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/include/netlink, directory renamed 
/usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/include/netlink-private/route -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/include/netlink-private/route, 
directory renamed 
/usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/include/netlink/idiag -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/include/netlink/idiag, directory 
renamed 
/usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/include/linux-private/linux/tc_ematch
 -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/include/linux-private/linux/tc_ematch,
 directory renamed /usr/src/debug/libnl/1_3.6.0-r0/libnl-3.6.0/src/lib -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/src/lib, directory renamed 
/usr/src/debug/l
 ibnl/1_3.6.0-r0/libnl-3.6.0/lib/route/cls -> 
/usr/src/debug/libnl/1_3.7.0-r0/libnl-3.7.0/lib/route/cls, directory renamed

[OE-core] [AUH] libva-initial: upgrading to 2.15.0 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  finish -f libva-initial 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (889 cached, 1 parsed). 1663 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.

INFO: No patches or local source files needed updating
INFO: Cleaning sysroot for recipe libva-initial...
ERROR: Command 'bitbake -c clean libva-initial' failed, output:
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1663 entries from dependency cache.
Parsing recipes...
Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.

If you wish, you may specify -n/--no-clean to skip running this command when 
resetting


Next steps:
- apply the patch: git am 0001-libva-initial-upgrade-2.14.0-2.15.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


0001-libva-initial-upgrade-2.14.0-2.15.0.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168099): 
https://lists.openembedded.org/g/openembedded-core/message/168099
Mute This Topic: https://lists.openembedded.org/mt/92403747/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] xf86-video-cirrus: upgrading to 1.6.0 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xf86-video-cirrus* to *1.6.0* 
has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade xf86-video-cirrus -V 1.6.0
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/driver/xf86-video-cirrus-1.6.0.tar.bz2, 
attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/driver/xf86-video-cirrus-1.6.0.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq_53x/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq_53x/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq_53x/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq_53x/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq_53x/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fbxq
 
_53x/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/xf86-video-cirrus-1.6.0.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads

[OE-core] [AUH] wayland-protocols: upgrading to 1.26 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wayland-protocols* to *1.26* 
has Succeeded.

Next steps:
- apply the patch: git am 0001-wayland-protocols-upgrade-1.25-1.26.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/wayland-protocols: PV changed from "1.25" to "1.26"
packages/all-poky-linux/wayland-protocols: PKGV changed from 1.25 [default] to 
1.26 [default]
packages/all-poky-linux/wayland-protocols: SRC_URI changed from 
"https://wayland.freedesktop.org/releases/wayland-protocols-1.25.tar.xz; to 
"https://wayland.freedesktop.org/releases/wayland-protocols-1.26.tar.xz;
Changes to packages/all-poky-linux/wayland-protocols (sysroot):
  /usr/share/wayland-protocols/staging/single-pixel-buffer was added
  
/usr/share/wayland-protocols/staging/single-pixel-buffer/single-pixel-buffer-v1.xml
 was added
packages/all-poky-linux/wayland-protocols/wayland-protocols-src: PV changed 
from "1.25" to "1.26"
packages/all-poky-linux/wayland-protocols/wayland-protocols-src: PKGV changed 
from 1.25 [default] to 1.26 [default]
packages/all-poky-linux/wayland-protocols/wayland-protocols: PKGSIZE changed 
from 472395 to 477229 (+1%)
packages/all-poky-linux/wayland-protocols/wayland-protocols: PV changed from 
"1.25" to "1.26"
packages/all-poky-linux/wayland-protocols/wayland-protocols: PKGV changed from 
1.25 [default] to 1.26 [default]
packages/all-poky-linux/wayland-protocols/wayland-protocols: FILELIST: added 
"/usr/share/wayland-protocols/staging/single-pixel-buffer/single-pixel-buffer-v1.xml"


0001-wayland-protocols-upgrade-1.25-1.26.patch
Description: Binary data
Changes to packages/all-poky-linux/wayland-protocols (sysroot):
  /usr/share/wayland-protocols/staging/single-pixel-buffer was added
  
/usr/share/wayland-protocols/staging/single-pixel-buffer/single-pixel-buffer-v1.xml
 was added
packages/all-poky-linux/wayland-protocols/wayland-protocols: FILELIST: added 
"/usr/share/wayland-protocols/staging/single-pixel-buffer/single-pixel-buffer-v1.xml"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168107): 
https://lists.openembedded.org/g/openembedded-core/message/168107
Mute This Topic: https://lists.openembedded.org/mt/92403755/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] piglit: upgrading to c107462e4e429fa1cf6daac39168674c1c0c9fd4 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to 
*c107462e4e429fa1cf6daac39168674c1c0c9fd4* 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: PKGV changed from 
1.0+gitrAUTOINC+479b0002d0 [default] to 1.0+gitrAUTOINC+c107462e4e [default]
packages/core2-32-poky-linux/piglit: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-bash-completion: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-dbg: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-dev: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-doc: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-locale: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-src: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-staticdev: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit: PV changed from 
"1.0+gitrAUTOINC+479b0002d0" to "1.0+gitrAUTOINC+c107462e4e"
packages/core2-32-poky-linux/piglit/piglit: FILELIST: added 
"/usr/lib/piglit/bin/arm_shader_framebuffer_fetch_depth_stencil 
/usr/lib/piglit/bin/arm_shader_framebuffer_fetch_depth_stencil_gles3"
packages/core2-32-poky-linux/piglit/piglit: PKGSIZE changed from 2042567695 to 
2042597292 (+0%)


0001-piglit-upgrade-to-latest-revision.patch
Description: Binary data
packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e
packages/core2-32-poky-linux/piglit/piglit: FILELIST: added 
"/usr/lib/piglit/bin/arm_shader_framebuffer_fetch_depth_stencil 
/usr/lib/piglit/bin/arm_shader_framebuffer_fetch_depth_stencil_gles3"
packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 
1.0+gitr0+479b0002d0 to 1.0+gitr0+c107462e4e

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

[OE-core] [AUH] libgit2: upgrading to 1.5.0 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe libgit2 failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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 current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto fbea439d4b6fc91c6b619d01b85ab3b7746e4c19
WARNING: Command 'git rebase fbea439d4b6fc91c6b619d01b85ab3b7746e4c19' failed:
Auto-merging include/git2/version.h
CONFLICT (content): Merge conflict in include/git2/version.h

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/libgit2
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libgit2/libgit2_1.5.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 (#168102): 
https://lists.openembedded.org/g/openembedded-core/message/168102
Mute This Topic: https://lists.openembedded.org/mt/92403750/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] encodings: upgrading to 1.0.6 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  upgrade encodings -V 1.0.6
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/font/encodings-1.0.6.tar.bz2, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/font/encodings-1.0.6.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las2n8q/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las2n8q/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las2n8q/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las2n8q/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las2n8q/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-3las
 
2n8q/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/encodings-1.0.6.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads

[OE-core] [AUH] libva: upgrading to 2.15.0 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-libva-upgrade-2.14.0-2.15.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/libva: PV changed from "2.14.0" to "2.15.0"
packages/core2-32-poky-linux/libva: SRC_URI changed from 
"https://github.com/intel/libva/releases/download/2.14.0/libva-2.14.0.tar.bz2; 
to 
"https://github.com/intel/libva/releases/download/2.15.0/libva-2.15.0.tar.bz2;
packages/core2-32-poky-linux/libva: PKGV changed from 2.14.0 [default] to 
2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-dbg: FILELIST: removed 
"/usr/lib/.debug/libva-wayland.so.2.1400.0 
/usr/lib/.debug/libva-x11.so.2.1400.0 /usr/lib/.debug/libva.so.2.1400.0 
/usr/lib/.debug/libva-drm.so.2.1400.0 /usr/lib/.debug/libva-glx.so.2.1400.0", 
added "/usr/lib/.debug/libva-drm.so.2.1500.0 
/usr/lib/.debug/libva-glx.so.2.1500.0 /usr/lib/.debug/libva-wayland.so.2.1500.0 
/usr/lib/.debug/libva.so.2.1500.0 /usr/lib/.debug/libva-x11.so.2.1500.0"
packages/core2-32-poky-linux/libva/libva-dbg: PV changed from "2.14.0" to 
"2.15.0"
packages/core2-32-poky-linux/libva/libva-dbg: PKGSIZE changed from 736268 to 
721592 (-2%)
packages/core2-32-poky-linux/libva/libva-dbg: PKGV changed from 2.14.0 
[default] to 2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-dev: PV changed from "2.14.0" to 
"2.15.0"
packages/core2-32-poky-linux/libva/libva-dev: PKGSIZE changed from 646641 to 
648841 (+0%)
packages/core2-32-poky-linux/libva/libva-dev: PKGV changed from 2.14.0 
[default] to 2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-doc: PV changed from "2.14.0" to 
"2.15.0"
packages/core2-32-poky-linux/libva/libva-doc: PKGV changed from 2.14.0 
[default] to 2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-glx: FILELIST: removed 
"/usr/lib/libva-glx.so.2.1400.0", added "/usr/lib/libva-glx.so.2.1500.0"
packages/core2-32-poky-linux/libva/libva-glx: PV changed from "2.14.0" to 
"2.15.0"
packages/core2-32-poky-linux/libva/libva-glx: PKGV changed from 2.14.0 
[default] to 2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-locale: PV changed from "2.14.0" to 
"2.15.0"
packages/core2-32-poky-linux/libva/libva-locale: PKGV changed from 2.14.0 
[default] to 2.15.0 [default]
packages/core2-32-poky-linux/libva/libva-src: FILELIST: directory renamed 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/wayland -> 
/usr/src/debug/libva/2.15.0-r0/libva-2.15.0/va/wayland, directory renamed 
/usr/src/debug/libva/2.14.0-r0/build/va -> 
/usr/src/debug/libva/2.15.0-r0/build/va, directory renamed 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/x11 -> 
/usr/src/debug/libva/2.15.0-r0/libva-2.15.0/va/x11, directory renamed 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/drm -> 
/usr/src/debug/libva/2.15.0-r0/libva-2.15.0/va/drm, directory renamed 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/glx -> 
/usr/src/debug/libva/2.15.0-r0/libva-2.15.0/va/glx, removed 
"/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_enc_vp8.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_dec_jpeg.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_compat.c 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_dec_vp9.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_prot.h 
/usr/src/debug/libva/2.14.0-r0
 /libva-2.14.0/va/va_enc_h264.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_backend_prot.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_fool.c 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_drmcommon.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va.c 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_vpp.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_enc_mpeg2.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_enc_vp9.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_enc_hevc.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_dec_vp8.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_backend.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_str.c 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_trace.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_str.h 
/usr/src/debug/libva/2.14.0-r0/libva-2.14.0/va/va_dec_hevc.h

[OE-core] [AUH] xmodmap: upgrading to 1.0.11 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  upgrade xmodmap -V 1.0.11
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/app/xmodmap-1.0.11.tar.bz2, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/app/xmodmap-1.0.11.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltptbw3/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltptbw3/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltptbw3/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltptbw3/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltptbw3/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-wltp
 
tbw3/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/xmodmap-1.0.11.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads 
'https://www.x.org/releases//individual/app/xmodmap-1.0.11.tar.bz2'

[OE-core] [AUH] font-util: upgrading to 1.3.3 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  upgrade font-util -V 1.3.3
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/font/font-util-1.3.3.tar.bz2, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/font/font-util-1.3.3.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4xzvp/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4xzvp/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4xzvp/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4xzvp/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4xzvp/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-fxj4
 
xzvp/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/font-util-1.3.3.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads

[OE-core] [AUH] python3-jsonschema: upgrading to 4.7.2 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-python3-jsonschema-upgrade-4.7.1-4.7.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-jsonschema: PV changed from "4.7.1" to 
"4.7.2"
packages/core2-32-poky-linux/python3-jsonschema: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/j/jsonschema/jsonschema-4.7.1.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/j/jsonschema/jsonschema-4.7.2.tar.gz;
packages/core2-32-poky-linux/python3-jsonschema: PKGV changed from 4.7.1 
[default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-dbg: PV 
changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-dbg: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-dev: PV 
changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-dev: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-doc: PV 
changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-doc: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-locale: PV 
changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-locale: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-src: PV 
changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-src: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-staticdev: 
PV changed from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema-staticdev: 
PKGV changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema: PV changed 
from "4.7.1" to "4.7.2"
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema: PKGV 
changed from 4.7.1 [default] to 4.7.2 [default]
packages/core2-32-poky-linux/python3-jsonschema/python3-jsonschema: PKGSIZE 
changed from 690656 to 692410 (+0%)
Changes to packages/core2-32-poky-linux/python3-jsonschema (sysroot):
  /usr/lib/python3.10/site-packages/jsonschema-4.7.1.dist-info moved to 
/usr/lib/python3.10/site-packages/jsonschema-4.7.2.dist-info


0001-python3-jsonschema-upgrade-4.7.1-4.7.2.patch
Description: Binary data
Changes to packages/core2-32-poky-linux/python3-jsonschema (sysroot):
  /usr/lib/python3.10/site-packages/jsonschema-4.7.1.dist-info moved to 
/usr/lib/python3.10/site-packages/jsonschema-4.7.2.dist-info

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168086): 
https://lists.openembedded.org/g/openembedded-core/message/168086
Mute This Topic: https://lists.openembedded.org/mt/92403734/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] hdparm: upgrading to 9.64 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-hdparm-upgrade-9.63-9.64.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/hdparm/hdparm-dbg: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-dbg: PKGSIZE changed from 300816 to 
300828 (+0%)
packages/core2-32-poky-linux/hdparm/hdparm-dbg: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm/hdparm-dev: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-dev: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm/hdparm-doc: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-doc: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm/hdparm-locale: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-locale: PV changed from "9.63" to 
"9.64"
packages/core2-32-poky-linux/hdparm/hdparm-src: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-src: PKGSIZE changed from 229462 to 
229528 (+0%)
packages/core2-32-poky-linux/hdparm/hdparm-src: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm/hdparm-staticdev: PKGV changed from 9.63 
[default] to 9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm-staticdev: PV changed from "9.63" to 
"9.64"
packages/core2-32-poky-linux/hdparm/hdparm: PKGV changed from 9.63 [default] to 
9.64 [default]
packages/core2-32-poky-linux/hdparm/hdparm: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm: PKGV changed from 9.63 [default] to 9.64 
[default]
packages/core2-32-poky-linux/hdparm: SRC_URI changed from 
"https://downloads.sourceforge.net/hdparm/hdparm-9.63.tar.gz 
file://wiper.sh-fix-stat-path.patch" to 
"https://downloads.sourceforge.net/hdparm/hdparm-9.64.tar.gz 
file://wiper.sh-fix-stat-path.patch"
packages/core2-32-poky-linux/hdparm: PV changed from "9.63" to "9.64"
packages/core2-32-poky-linux/hdparm/wiper: PKGV changed from 9.63 [default] to 
9.64 [default]
packages/core2-32-poky-linux/hdparm/wiper: PV changed from "9.63" to "9.64"


0001-hdparm-upgrade-9.63-9.64.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168085): 
https://lists.openembedded.org/g/openembedded-core/message/168085
Mute This Topic: https://lists.openembedded.org/mt/92403733/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] xf86-input-synaptics: upgrading to 1.9.2 FAILED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xf86-input-synaptics* to 
*1.9.2* has Failed (devtool error).

Detailed error information:

The following devtool command failed:  upgrade xf86-input-synaptics -V 1.9.2
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/driver/xf86-input-synaptics-1.9.2.tar.bz2,
 attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://www.x.org/releases//individual/driver/xf86-input-synaptics-1.9.2.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu9bih/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu9bih/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu9bih/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu9bih/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu9bih/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-reyu
 
9bih/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/xf86-input-synaptics-1.9.2.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads

[OE-core] [AUH] rpm: upgrading to 4.17.1 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe rpm failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-5c567186d9017b2f6e3ed3d30b257ee8ff25239f"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:5c567186d9017b2f6e3ed3d30b257ee8ff25239f"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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: 1 seconds
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 5bef402da334595ed9302b8bca1acdf5e88bfe11
WARNING: Command 'git rebase 5bef402da334595ed9302b8bca1acdf5e88bfe11' failed:
Auto-merging rpmio/rpmpgp.c
CONFLICT (content): Merge conflict in rpmio/rpmpgp.c

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/rpm
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/rpm/rpm_4.17.1.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 (#168087): 
https://lists.openembedded.org/g/openembedded-core/message/168087
Mute This Topic: https://lists.openembedded.org/mt/92403735/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] xev: upgrading to 1.2.5 FAILED

Hello,

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

Detailed error information:

The following devtool command failed:  upgrade xev -V 1.2.5
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-28dbfa376d767146e4b8c7a4e30297d612879ade"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:28dbfa376d767146e4b8c7a4e30297d612879ade"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% 
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL 
https://www.x.org/releases//individual/app/xev-1.2.5.tar.bz2, attempting 
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching https://www.x.org/releases//individual/app/xev-1.2.5.tar.bz2...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export 
ftp_proxy="http://proxy.yocto.io:5187/;; export 
FTP_PROXY="http://proxy.yocto.io:5187/;; export 
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zriyee/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zriyee/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zriyee/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zriyee/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zriyee/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-q8zr
 
iyee/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
 export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O 
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/xev-1.2.5.tar.bz2.tmp
 -P /home/pokybuild/yocto-worker/auh/build/build/build/downloads 
'https://www.x.org/releases//individual/app/xev-1.2.5.tar.bz2' --progress=dot 
-v failed with

[OE-core] [AUH] python3-zipp: upgrading to 3.8.1 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-python3-zipp-upgrade-3.8.0-3.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-zipp: PV changed from "3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp: PKGV changed from 3.8.0 [default] to 
3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/z/zipp/zipp-3.8.0.tar.gz; to 
"https://files.pythonhosted.org/packages/source/z/zipp/zipp-3.8.1.tar.gz;
packages/core2-32-poky-linux/python3-zipp/python3-zipp-dbg: PV changed from 
"3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-dbg: PKGV changed from 
3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp-dev: PV changed from 
"3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-dev: PKGV changed from 
3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp-doc: PV changed from 
"3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-doc: PKGV changed from 
3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp-locale: PV changed from 
"3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-locale: PKGV changed 
from 3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp-src: PV changed from 
"3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-src: PKGV changed from 
3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp-staticdev: PV changed 
from "3.8.0" to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp-staticdev: PKGV changed 
from 3.8.0 [default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp: PV changed from "3.8.0" 
to "3.8.1"
packages/core2-32-poky-linux/python3-zipp/python3-zipp: PKGV changed from 3.8.0 
[default] to 3.8.1 [default]
packages/core2-32-poky-linux/python3-zipp/python3-zipp: PKGSIZE changed from 
22168 to 22959 (+4%)
Changes to packages/core2-32-poky-linux/python3-zipp (sysroot):
  /usr/lib/python3.10/site-packages/zipp-3.8.0.dist-info moved to 
/usr/lib/python3.10/site-packages/zipp-3.8.1.dist-info


0001-python3-zipp-upgrade-3.8.0-3.8.1.patch
Description: Binary data
Changes to packages/core2-32-poky-linux/python3-zipp (sysroot):
  /usr/lib/python3.10/site-packages/zipp-3.8.0.dist-info moved to 
/usr/lib/python3.10/site-packages/zipp-3.8.1.dist-info

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168081): 
https://lists.openembedded.org/g/openembedded-core/message/168081
Mute This Topic: https://lists.openembedded.org/mt/92403729/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] gcr: upgrading to 3.90.0 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe gcr failed.
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-75a9b44b3562373bb266d0dc23c7fe035d2304bb"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:75a9b44b3562373bb266d0dc23c7fe035d2304bb"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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: 3 seconds
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 890 .bb files complete (888 cached, 2 parsed). 1661 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "qemux86-64"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-75a9b44b3562373bb266d0dc23c7fe035d2304bb"
TUNE_FEATURES= "m64 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:75a9b44b3562373bb266d0dc23c7fe035d2304bb"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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:  21% |### | ETA:  0:00:00
Adding changed files:  42% |### | ETA:  0:00:00
Adding changed files:  64% |### | ETA:  0:00:00
Adding changed files:  85% |##  | ETA:  0:00:00
Adding changed files: 100% || Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching 
https://download.gnome.org/sources//gcr/3.90/gcr-3.90.0.tar.xz;name=archive...
INFO: Rebasing devtool onto c47fc1424ff84bf17044c3b47bc5ab113942f57d
WARNING: Command 'git rebase c47fc1424ff84bf17044c3b47bc5ab113942f57d' failed:
CONFLICT (modify/delete): ui/meson.build deleted in HEAD and modified in 
c475aa6 (meson: Fix unknown kw argument in gnome.generate_gir). Version c475aa6 
(meson: Fix unknown kw argument in gnome.generate_gir) of ui/meson.build left 
in tree.
Auto-merging gcr/meson.build
CONFLICT (content): Merge conflict in gcr/meson.build
Auto-merging gck/meson.build
CONFLICT (content): Merge conflict in gck/meson.build

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/gcr
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/gcr/gcr_3.90.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

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

Hello,

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

Next steps:
- apply the patch: git am 
0001-python3-setuptools-rust-upgrade-1.3.0-1.4.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-setuptools-rust: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/s/setuptools-rust/setuptools-rust-1.3.0.tar.gz
 
https://files.pythonhosted.org/packages/67/08/e1aa2c582c62ac76e4d60f8e454bd3bba933781a06a88b4e38797445822a/setuptools-rust-1.3.0.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/s/setuptools-rust/setuptools-rust-1.4.1.tar.gz
 
https://files.pythonhosted.org/packages/67/08/e1aa2c582c62ac76e4d60f8e454bd3bba933781a06a88b4e38797445822a/setuptools-rust-1.4.1.tar.gz;
packages/core2-32-poky-linux/python3-setuptools-rust: PKGV changed from 1.3.0 
[default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust: PV changed from "1.3.0" 
to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-dbg:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-dbg:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-dev:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-dev:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-doc:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-doc:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-locale:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-locale:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-src:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-src:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-staticdev:
 PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust-staticdev:
 PV changed from "1.3.0" to "1.4.1"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust: 
PKGSIZE changed from 103786 to 118700 (+14%)
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust: 
PKGV changed from 1.3.0 [default] to 1.4.1 [default]
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust: 
FILELIST: directory renamed 
/usr/lib/python3.10/site-packages/setuptools_rust-1.3.0.dist-info -> 
/usr/lib/python3.10/site-packages/setuptools_rust-1.4.1.dist-info, removed 
"/usr/lib/python3.10/site-packages/setuptools_rust/utils.py 
/usr/lib/python3.10/site-packages/setuptools_rust/__pycache__/utils.cpython-310.pyc",
 added 
"/usr/lib/python3.10/site-packages/setuptools_rust/__pycache__/_utils.cpython-310.pyc
 
/usr/lib/python3.10/site-packages/setuptools_rust/__pycache__/rustc_info.cpython-310.pyc
 /usr/lib/python3.10/site-packages/setuptools_rust/_utils.py 
/usr/lib/python3.10/site-packages/setuptools_rust/rustc_info.py"
packages/core2-32-poky-linux/python3-setuptools-rust/python3-setuptools-rust: 
PV changed from "1.3.0" to "1.4.1"
Changes to packages/core2-32-poky-linux/python3-setuptools-rust (sysroot):
  /usr/lib/python3.10/site-packages/setuptools_rust-1.3.0.dist-info moved to 
/usr/lib/python3.10/site-packages/setuptools_rust-1.4.1.dist-info
  
/usr/lib/python3.10/site-packages/setuptools_rust/__pycache__/rustc_info.cpython-310.pyc
 was added
  
/usr/lib/python3.10/site-packages/setuptools_rust/__pycache__/_utils.cpython-310.pyc
 was added
  /usr/lib/python3.10/site-packages/setuptools_rust/rustc_info.py was added
  /usr/lib/python3.10/site-packages/setuptools_rust/_utils.py was added

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

Hello,

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

Next steps:
- apply the patch: git am 
0001-python3-setuptools-scm-upgrade-7.0.3-7.0.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


0001-python3-setuptools-scm-upgrade-7.0.3-7.0.5.patch
Description: Binary data
packages/core2-32-poky-linux/python3-setuptools-scm: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/s/setuptools_scm/setuptools_scm-7.0.3.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/s/setuptools_scm/setuptools_scm-7.0.5.tar.gz;
packages/core2-32-poky-linux/python3-setuptools-scm: PKGV changed from 7.0.3 
[default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm: PV changed from "7.0.3" to 
"7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dbg: 
PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dbg: 
PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dev: 
PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-dev: 
PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-doc: 
PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-doc: 
PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-locale:
 PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-locale:
 PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-src: 
PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-src: 
PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-staticdev:
 PV changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm-staticdev:
 PKGV changed from 7.0.3 [default] to 7.0.5 [default]
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: 
PKGSIZE changed from 193065 to 193775 (+0%)
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: PV 
changed from "7.0.3" to "7.0.5"
packages/core2-32-poky-linux/python3-setuptools-scm/python3-setuptools-scm: 
PKGV changed from 7.0.3 [default] to 7.0.5 [default]
Changes to packages/core2-32-poky-linux/python3-setuptools-scm (sysroot):
  /usr/lib/python3.10/site-packages/setuptools_scm-7.0.3.dist-info moved to 
/usr/lib/python3.10/site-packages/setuptools_scm-7.0.5.dist-info
Changes to packages/core2-32-poky-linux/python3-setuptools-scm (sysroot):
  /usr/lib/python3.10/site-packages/setuptools_scm-7.0.3.dist-info moved to 
/usr/lib/python3.10/site-packages/setuptools_scm-7.0.5.dist-info

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168080): 
https://lists.openembedded.org/g/openembedded-core/message/168080
Mute This Topic: https://lists.openembedded.org/mt/92403728/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] libva-utils: upgrading to 2.15.0 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe libva-utils failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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 current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto be203c8b85b07e1f7a3faedd13057b0a8cabd3c3
WARNING: Command 'git rebase be203c8b85b07e1f7a3faedd13057b0a8cabd3c3' failed:
Auto-merging meson.build
CONFLICT (content): Merge conflict in meson.build
Auto-merging configure.ac
CONFLICT (content): Merge conflict in configure.ac

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/libva-utils
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libva-utils/libva-utils_2.15.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 (#168084): 
https://lists.openembedded.org/g/openembedded-core/message/168084
Mute This Topic: https://lists.openembedded.org/mt/92403732/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] vala: upgrading to 0.56.2 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-vala-upgrade-0.56.1-0.56.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/vala: PKGV changed from 0.56.1 [default] to 0.56.2 
[default]
packages/core2-32-poky-linux/vala: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala: SRC_URI changed from 
"http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.1.tar.xz; to 
"http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.2.tar.xz;
Changes to packages/core2-32-poky-linux/vala (sysroot):
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.deps was added
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-1.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.vapi was added
  /usr/share/vala-0.56/vapi/wayland-client.vapi was added
packages/core2-32-poky-linux/vala/vala-dbg: PKGV changed from 0.56.1 [default] 
to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-dbg: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala/vala-dbg: PKGSIZE changed from 15442244 to 
15447840 (+0%)
packages/core2-32-poky-linux/vala/vala-dev: PKGV changed from 0.56.1 [default] 
to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-dev: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala/vala-doc: PKGV changed from 0.56.1 [default] 
to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-doc: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala/vala-doc: PKGSIZE changed from 10307 to 10304 
(-0%)
packages/core2-32-poky-linux/vala/vala-locale: PKGV changed from 0.56.1 
[default] to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-locale: PV changed from "0.56.1" to 
"0.56.2"
packages/core2-32-poky-linux/vala/vala-src: PKGV changed from 0.56.1 [default] 
to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-src: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala/vala-src: PKGSIZE changed from 15478348 to 
15485258 (+0%)
packages/core2-32-poky-linux/vala/vala-staticdev: PKGV changed from 0.56.1 
[default] to 0.56.2 [default]
packages/core2-32-poky-linux/vala/vala-staticdev: PV changed from "0.56.1" to 
"0.56.2"
packages/core2-32-poky-linux/vala/vala: PKGV changed from 0.56.1 [default] to 
0.56.2 [default]
packages/core2-32-poky-linux/vala/vala: PV changed from "0.56.1" to "0.56.2"
packages/core2-32-poky-linux/vala/vala: PKGSIZE changed from 13028128 to 
13073034 (+0%)
packages/core2-32-poky-linux/vala/vala: FILELIST: added 
"/usr/share/vala-0.56/vapi/rest-1.0.vapi 
/usr/share/vala-0.56/vapi/wayland-client.vapi 
/usr/share/vala-0.56/vapi/geocode-glib-2.0.deps 
/usr/share/vala-0.56/vapi/rest-1.0.deps 
/usr/share/vala-0.56/vapi/rest-extras-1.0.vapi 
/usr/share/vala-0.56/vapi/rest-extras-1.0.deps 
/usr/share/vala-0.56/vapi/geocode-glib-2.0.vapi"
Changes to packages/x86_64-linux/vala-native (sysroot):
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.deps was added
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-1.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.vapi was added
  /usr/share/vala-0.56/vapi/wayland-client.vapi was added


0001-vala-upgrade-0.56.1-0.56.2.patch
Description: Binary data
Changes to packages/core2-32-poky-linux/vala (sysroot):
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.deps was added
  /usr/share/vala-0.56/vapi/geocode-glib-2.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-1.0.vapi was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.deps was added
  /usr/share/vala-0.56/vapi/rest-extras-1.0.vapi was added
  /usr/share/vala-0.56/vapi/wayland-client.vapi was added
packages/core2-32-poky-linux/vala/vala: FILELIST: added 
"/usr/share/vala-0.56/vapi/wayland-client.vapi 
/usr/share/vala-0.56/vapi/rest-extras-1.0.vapi 
/usr/share/vala-0.56/vapi/geocode-glib-2.0.vapi

[OE-core] [AUH] python3-dtschema: upgrading to 2022.7 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-python3-dtschema-upgrade-2022.5-2022.7.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-dtschema: PKGV changed from 2022.5 
[default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema: PV changed from "2022.5" to 
"2022.7"
packages/core2-32-poky-linux/python3-dtschema: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/d/dtschema/dtschema-2022.5.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/d/dtschema/dtschema-2022.7.tar.gz;
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dbg: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dbg: PV changed 
from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dev: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-dev: PV changed 
from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-doc: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-doc: PV changed 
from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-locale: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-locale: PV 
changed from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-src: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-src: PV changed 
from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-staticdev: PKGV 
changed from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema-staticdev: PV 
changed from "2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PKGV changed 
from 2022.5 [default] to 2022.7 [default]
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PV changed from 
"2022.5" to "2022.7"
packages/core2-32-poky-linux/python3-dtschema/python3-dtschema: PKGSIZE changed 
from 218918 to 226184 (+3%)
Changes to packages/core2-32-poky-linux/python3-dtschema (sysroot):
  /usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info moved to 
/usr/lib/python3.10/site-packages/dtschema-2022.7.dist-info
Changes to packages/core2-32-poky-linux/python3-dtschema (sysroot):
  /usr/lib/python3.10/site-packages/dtschema-2022.5.dist-info moved to 
/usr/lib/python3.10/site-packages/dtschema-2022.7.dist-info


0001-python3-dtschema-upgrade-2022.5-2022.7.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168079): 
https://lists.openembedded.org/g/openembedded-core/message/168079
Mute This Topic: https://lists.openembedded.org/mt/92403727/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-hypothesis: upgrading to 6.50.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.50.1* has Succeeded.

Next steps:
- apply the patch: git am 
0001-python3-hypothesis-upgrade-6.48.2-6.50.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.48.2.tar.gz
 file://run-ptest file://test_binary_search.py file://test_rle.py" to 
"https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.50.1.tar.gz
 file://run-ptest file://test_binary_search.py file://test_rle.py"
packages/core2-32-poky-linux/python3-hypothesis: PKGV changed from 6.48.2 
[default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis: PV changed from "6.48.2" to 
"6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-locale: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-locale: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-src: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-src: PV 
changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-staticdev: 
PKGV changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-staticdev: 
PV changed from "6.48.2" to "6.50.1"
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PKGV 
changed from 6.48.2 [default] to 6.50.1 [default]
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PKGSIZE 
changed from 2072669 to 2079543 (+0%)
packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PV changed 
from "6.48.2" to "6.50.1"
Changes to packages/core2-32-poky-linux/python3-hypothesis (sysroot):
  /usr/lib/python3.10/site-packages/hypothesis-6.48.2.dist-info moved to 
/usr/lib/python3.10/site-packages/hypothesis-6.50.1.dist-info
Changes to packages/core2-32-poky-linux/python3-hypothesis (sysroot):
  /usr/lib/python3.10/site-packages/hypothesis-6.48.2.dist-info moved to 
/usr/lib/python3.10/site-packages/hypothesis-6.50.1.dist-info


0001-python3-hypothesis-upgrade-6.48.2-6.50.1.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168074): 
https://lists.openembedded.org/g/openembedded-core/message/168074
Mute This Topic: https://lists.openembedded.org/mt/92403721/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: upgrading to 63.2.0 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 
0001-python3-setuptools-upgrade-62.6.0-63.2.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/python3-setuptools: PKGV changed from 62.6.0 
[default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools: PV changed from "62.6.0" to 
"63.2.0"
packages/core2-32-poky-linux/python3-setuptools: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-62.6.0.tar.gz
 file://0001-change-shebang-to-python3.patch 
file://0001-_distutils-sysconfig.py-make-it-possible-to-substite.patch" to 
"https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-63.2.0.tar.gz
 file://0001-change-shebang-to-python3.patch 
file://0001-_distutils-sysconfig.py-make-it-possible-to-substite.patch"
packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PV 
changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: 
PKGV changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: 
PV changed from "62.6.0" to "63.2.0"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGV 
changed from 62.6.0 [default] to 63.2.0 [default]
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: FILELIST: 
directory renamed /usr/lib/python3.10/site-packages/setuptools-62.6.0.dist-info 
-> /usr/lib/python3.10/site-packages/setuptools-63.2.0.dist-info, removed 
"/usr/lib/python3.10/site-packages/setuptools/_vendor/nspektr/__init__.py 
/usr/lib/python3.10/site-packages/setuptools/_vendor/nspektr/__pycache__/__init__.cpython-310.pyc
 
/usr/lib/python3.10/site-packages/setuptools/_vendor/nspektr/__pycache__/_compat.cpython-310.pyc
 /usr/lib/python3.10/site-packages/setuptools/_vendor/nspektr/_compat.py", 
added 
"/usr/lib/python3.10/site-packages/setuptools/_distutils/command/_framework_compat.py
 
/usr/lib/python3.10/site-packages/setuptools/_distutils/command/__pycache__/_framework_compat.cpython-310.pyc"
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGSIZE 
changed from 4866050 to 4858785 (-0%)
packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PV changed 
from "62.6.0" to "63.2.0"
Changes to packages/core2-32-poky-linux/python3-setuptools (sysroot):
  /usr/lib/python3.10/site-packages/setuptools-62.6.0.dist-info moved to 
/usr/lib/python3.10/site-packages/setuptools-63.2.0.dist-info
  
/usr/lib/python3.10/site-packages/setuptools/_distutils/command/_framework_compat.py
 was added
  
/usr/lib/python3.10/site-packages/setuptools/_distutils/command/__pycache__/_framework_compat.cpython-310.pyc
 was added
  /usr/lib/python3.10/site-packages/setuptools/_vendor/nspektr was removed

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

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-go-upgrade-1.18.3-1.18.4.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...
Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: ParseError at 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/go/go-runtime_1.18.3.bb:1:
 Could not include required file go-1.18.3.inc
ERROR: Parsing halted due to errors, see error messages above


0001-go-upgrade-1.18.3-1.18.4.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168075): 
https://lists.openembedded.org/g/openembedded-core/message/168075
Mute This Topic: https://lists.openembedded.org/mt/92403722/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-docutils: upgrading to 0.19 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-python3-docutils-upgrade-0.18.1-0.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/core2-32-poky-linux/python3-docutils: PV changed from "0.18.1" to 
"0.19"
packages/core2-32-poky-linux/python3-docutils: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/d/docutils/docutils-0.18.1.tar.gz;
 to 
"https://files.pythonhosted.org/packages/source/d/docutils/docutils-0.19.tar.gz;
packages/core2-32-poky-linux/python3-docutils: PKGV changed from 0.18.1 
[default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-dbg: PV changed 
from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-dbg: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-dev: PV changed 
from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-dev: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-doc: PV changed 
from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-doc: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-locale: PV 
changed from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-locale: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-src: PV changed 
from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-src: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils-staticdev: PV 
changed from "0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils-staticdev: PKGV 
changed from 0.18.1 [default] to 0.19 [default]
packages/core2-32-poky-linux/python3-docutils/python3-docutils: PV changed from 
"0.18.1" to "0.19"
packages/core2-32-poky-linux/python3-docutils/python3-docutils: FILELIST: 
removed "/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/METADATA 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/RECORD 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/dependency_links.html
 /usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/top_level.txt 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/COPYING.txt 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/SOURCES.html 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/top_level.html 
/usr/lib/python3.10/site-packages/docutils-0.18.1.dist-info/WHEEL", added 
"/usr/bin/docutils 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/WHEEL 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/top_level.html 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/dependency_links.html 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/top_level.txt 
/usr/lib/python3.10/s
 ite-packages/docutils/parsers/__pycache__/commonmark_wrapper.cpython-310.pyc 
/usr/lib/python3.10/site-packages/docutils/__pycache__/__main__.cpython-310.pyc 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/SOURCES.html 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/RECORD 
/usr/lib/python3.10/site-packages/docutils/parsers/commonmark_wrapper.py 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/COPYING.txt 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/METADATA 
/usr/lib/python3.10/site-packages/docutils-0.19.dist-info/entry_points.txt 
/usr/lib/python3.10/site-packages/docutils/__main__.py"
packages/core2-32-poky-linux/python3-docutils/python3-docutils: PKGSIZE changed 
from 3218679 to 3222813 (+0%)
packages/core2-32-poky-linux/python3-docutils/python3-docutils: PKGV changed 
from 0.18.1 [default] to 0.19 [default]
Changes to packages/core2-32-poky-linux/python3-docutils (sysroot):
  /usr/lib/python3.10/site-packages/docutils-0.19.dist-info was added
  /usr/lib/python3.10/site-packages/docutils-0.19.dist-info/COPYING.txt was 
added

[OE-core] [AUH] meson: upgrading to 0.63.0 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-meson-upgrade-0.62.2-0.63.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/meson: SRC_URI changed from 
"https://github.com/mesonbuild/meson/releases/download/0.62.2/meson-0.62.2.tar.gz
 file://meson-setup.py file://meson-wrapper 
file://0001-python-module-do-not-manipulate-the-environment-when.patch 
file://disable-rpath-handling.patch 
file://0001-Make-CPU-family-warnings-fatal.patch 
file://0002-Support-building-allarch-recipes-again.patch 
file://0001-is_debianlike-always-return-False.patch 
file://0001-Check-for-clang-before-guessing-gcc-or-lcc.patch" to 
"https://github.com/mesonbuild/meson/releases/download/0.63.0/meson-0.63.0.tar.gz
 file://meson-setup.py file://meson-wrapper 
file://0001-python-module-do-not-manipulate-the-environment-when.patch 
file://disable-rpath-handling.patch 
file://0001-Make-CPU-family-warnings-fatal.patch 
file://0002-Support-building-allarch-recipes-again.patch 
file://0001-is_debianlike-always-return-False.patch 
file://0001-Check-for-clang-before-guessing-gcc-or-lcc.patch"
packages/core2-32-poky-linux/meson: PKGV changed from 0.62.2 [default] to 
0.63.0 [default]
packages/core2-32-poky-linux/meson: PV changed from "0.62.2" to "0.63.0"
packages/core2-32-poky-linux/meson/meson-dbg: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-dbg: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson-dev: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-dev: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson-doc: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-doc: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson-doc: PKGSIZE changed from 5340 to 5341 
(+0%)
packages/core2-32-poky-linux/meson/meson-locale: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-locale: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson-src: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-src: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson-staticdev: PKGV changed from 0.62.2 
[default] to 0.63.0 [default]
packages/core2-32-poky-linux/meson/meson-staticdev: PV changed from "0.62.2" to 
"0.63.0"
packages/core2-32-poky-linux/meson/meson: PKGV changed from 0.62.2 [default] to 
0.63.0 [default]
packages/core2-32-poky-linux/meson/meson: PV changed from "0.62.2" to "0.63.0"
packages/core2-32-poky-linux/meson/meson: PKGSIZE changed from 5571742 to 
5656824 (+2%)
Changes to packages/core2-32-poky-linux/meson (sysroot):
  /usr/lib/python3.10/site-packages/meson-0.62.2.dist-info moved to 
/usr/lib/python3.10/site-packages/meson-0.63.0.dist-info


0001-meson-upgrade-0.62.2-0.63.0.patch
Description: Binary data
Changes to packages/core2-32-poky-linux/meson (sysroot):
  /usr/lib/python3.10/site-packages/meson-0.62.2.dist-info moved to 
/usr/lib/python3.10/site-packages/meson-0.63.0.dist-info

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168077): 
https://lists.openembedded.org/g/openembedded-core/message/168077
Mute This Topic: https://lists.openembedded.org/mt/92403724/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.37.1 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-git-upgrade-2.37.0-2.37.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/git/git-bash-completion: PV changed from "2.37.0" 
to "2.37.1"
packages/core2-32-poky-linux/git/git-bash-completion: PKGV changed from 2.37.0 
[default] to 2.37.1 [default]
packages/core2-32-poky-linux/git/git-dbg: PKGSIZE changed from 69612908 to 
69638992 (+0%)
packages/core2-32-poky-linux/git/git-dbg: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git-dbg: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/git-dev: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git-dev: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/git-doc: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git-doc: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/git-locale: PV changed from "2.37.0" to 
"2.37.1"
packages/core2-32-poky-linux/git/git-locale: PKGV changed from 2.37.0 [default] 
to 2.37.1 [default]
packages/core2-32-poky-linux/git/git-perltools: PV changed from "2.37.0" to 
"2.37.1"
packages/core2-32-poky-linux/git/git-perltools: PKGV changed from 2.37.0 
[default] to 2.37.1 [default]
packages/core2-32-poky-linux/git/git-src: PKGSIZE changed from 8729715 to 
8731618 (+0%)
packages/core2-32-poky-linux/git/git-src: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git-src: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/git-staticdev: PV changed from "2.37.0" to 
"2.37.1"
packages/core2-32-poky-linux/git/git-staticdev: PKGV changed from 2.37.0 
[default] to 2.37.1 [default]
packages/core2-32-poky-linux/git/git-tk: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git-tk: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/git: PKGSIZE changed from 24195466 to 24203658 
(+0%)
packages/core2-32-poky-linux/git/git: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/git: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git/gitweb: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git/gitweb: PKGV changed from 2.37.0 [default] to 
2.37.1 [default]
packages/core2-32-poky-linux/git: SRC_URI changed from 
"https://cdn.kernel.org/pub/software/scm/git/git-2.37.0.tar.gz;name=tarball 
file://fixsort.patch 
file://0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch" to 
"https://cdn.kernel.org/pub/software/scm/git/git-2.37.1.tar.gz;name=tarball 
file://fixsort.patch 
file://0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch"
packages/core2-32-poky-linux/git: PV changed from "2.37.0" to "2.37.1"
packages/core2-32-poky-linux/git: PKGV changed from 2.37.0 [default] to 2.37.1 
[default]


0001-git-upgrade-2.37.0-2.37.1.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168073): 
https://lists.openembedded.org/g/openembedded-core/message/168073
Mute This Topic: https://lists.openembedded.org/mt/92403720/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.18.4 FAILED

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-go-runtime-upgrade-1.18.3-1.18.4.patch
- check the changes to upstream patches and summarize them in the commit 
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update 
failures.
Any problem please file a bug at 
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper


0001-go-runtime-upgrade-1.18.3-1.18.4.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...
Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: ParseError at 
/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/go/go-native_1.18.3.bb:4:
 Could not include required file go-1.18.3.inc
ERROR: Parsing halted due to errors, see error messages above

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168071): 
https://lists.openembedded.org/g/openembedded-core/message/168071
Mute This Topic: https://lists.openembedded.org/mt/92403718/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] mmc-utils: upgrading to d7b343fd262880994f041ce2335442e7bd1071f5 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mmc-utils* to 
*d7b343fd262880994f041ce2335442e7bd1071f5* has Succeeded.

Next steps:
- apply the patch: git am 0001-mmc-utils-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


0001-mmc-utils-upgrade-to-latest-revision.patch
Description: Binary data
packages/core2-32-poky-linux/mmc-utils: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils: PKGV changed from 
0.1+gitAUTOINC+b7e4d5a6ae [default] to 0.1+gitAUTOINC+d7b343fd26 [default]
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGSIZE changed from 
229644 to 229396 (-0%)
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGSIZE changed from 
210092 to 210197 (+0%)
packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils: PV changed from 
"0.1+gitAUTOINC+b7e4d5a6ae" to "0.1+gitAUTOINC+d7b343fd26"
packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26
packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 
0.1+git0+b7e4d5a6ae to 0.1+git0+d7b343fd26

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168072): 
https://lists.openembedded.org/g/openembedded-core/message/168072
Mute This Topic: https://lists.openembedded.org/mt/92403719/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] log4cplus: upgrading to 2.0.8 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-log4cplus-upgrade-2.0.7-2.0.8.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/log4cplus: PKGV changed from 2.0.7 [default] to 
2.0.8 [default]
packages/core2-32-poky-linux/log4cplus: PV changed from "2.0.7" to "2.0.8"
packages/core2-32-poky-linux/log4cplus: SRC_URI changed from 
"https://downloads.sourceforge.net/project/log4cplus/log4cplus-stable/2.0.7/log4cplus-2.0.7.tar.gz;
 to 
"https://downloads.sourceforge.net/project/log4cplus/log4cplus-stable/2.0.8/log4cplus-2.0.8.tar.gz;
packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: FILELIST: removed 
"/usr/lib/.debug/liblog4cplus-2.0.so.3.4.6 
/usr/lib/.debug/liblog4cplusU-2.0.so.3.4.6", added 
"/usr/lib/.debug/liblog4cplus-2.0.so.3.4.7 
/usr/lib/.debug/liblog4cplusU-2.0.so.3.4.7"
packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PKGV changed from 2.0.7 
[default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PKGSIZE changed from 
15050528 to 15067208 (+0%)
packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PV changed from "2.0.7" 
to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus-dev: PKGV changed from 2.0.7 
[default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-dev: PV changed from "2.0.7" 
to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus-doc: PKGV changed from 2.0.7 
[default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-doc: PV changed from "2.0.7" 
to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus-locale: PKGV changed from 
2.0.7 [default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-locale: PV changed from 
"2.0.7" to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus-src: PKGV changed from 2.0.7 
[default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-src: PKGSIZE changed from 
709086 to 709906 (+0%)
packages/core2-32-poky-linux/log4cplus/log4cplus-src: PV changed from "2.0.7" 
to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus-staticdev: PKGV changed from 
2.0.7 [default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus-staticdev: PV changed from 
"2.0.7" to "2.0.8"
packages/core2-32-poky-linux/log4cplus/log4cplus: FILELIST: removed 
"/usr/lib/liblog4cplusU-2.0.so.3.4.6 /usr/lib/liblog4cplus-2.0.so.3.4.6", added 
"/usr/lib/liblog4cplus-2.0.so.3.4.7 /usr/lib/liblog4cplusU-2.0.so.3.4.7"
packages/core2-32-poky-linux/log4cplus/log4cplus: PKGV changed from 2.0.7 
[default] to 2.0.8 [default]
packages/core2-32-poky-linux/log4cplus/log4cplus: PV changed from "2.0.7" to 
"2.0.8"
Changes to packages/core2-32-poky-linux/log4cplus (sysroot):
  /usr/lib/liblog4cplus-2.0.so.3 changed symlink target from 
liblog4cplus-2.0.so.3.4.6 to liblog4cplus-2.0.so.3.4.7
  /usr/lib/liblog4cplus.so changed symlink target from 
liblog4cplus-2.0.so.3.4.6 to liblog4cplus-2.0.so.3.4.7
  /usr/lib/liblog4cplusU-2.0.so.3 changed symlink target from 
liblog4cplusU-2.0.so.3.4.6 to liblog4cplusU-2.0.so.3.4.7
  /usr/lib/liblog4cplusU.so changed symlink target from 
liblog4cplusU-2.0.so.3.4.6 to liblog4cplusU-2.0.so.3.4.7
  /usr/lib/liblog4cplus-2.0.so.3.4.6 moved to /usr/lib/liblog4cplus-2.0.so.3.4.7
  /usr/lib/liblog4cplusU-2.0.so.3.4.6 moved to 
/usr/lib/liblog4cplusU-2.0.so.3.4.7
packages/core2-32-poky-linux/log4cplus/log4cplus: FILELIST: removed 
"/usr/lib/liblog4cplus-2.0.so.3.4.6 /usr/lib/liblog4cplusU-2.0.so.3.4.6", added 
"/usr/lib/liblog4cplus-2.0.so.3.4.7 /usr/lib/liblog4cplusU-2.0.so.3.4.7"
Changes to packages/core2-32-poky-linux/log4cplus (sysroot):
  /usr/lib/liblog4cplus-2.0.so.3 changed symlink target from 
liblog4cplus-2.0.so.3.4.6 to liblog4cplus-2.0.so.3.4.7
  /usr/lib/liblog4cplus.so changed symlink target from 
liblog4cplus-2.0.so.3.4.6 to liblog4cplus-2.0.so.3.4.7
  /usr/lib/liblog4cplusU-2.0.so.3 changed symlink target from 
liblog4cplusU-2.0.so.3.4.6 to liblog4cplusU-2.0.so.3.4.7
  /usr/lib/liblog4cplusU.so changed symlink target from 
liblog4cplusU-2.0.so.3.4.6 to liblog4cplusU-2.0.so.3.4.7
  /usr/lib/liblog4cplus-2.0.so.3.4.6 moved to /usr/lib/liblog4cplus-2.0.so.3.4.7

[OE-core] [AUH] llvm: upgrading to 14.0.6 FAILED

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-llvm-upgrade-14.0.4-14.0.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


0001-llvm-upgrade-14.0.4-14.0.6.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Removing 1 recipes from the core2-32 sysroot...done.
Removing 1 recipes from the qemux86 sysroot...done.

Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: Nothing PROVIDES 'llvm'

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168068): 
https://lists.openembedded.org/g/openembedded-core/message/168068
Mute This Topic: https://lists.openembedded.org/mt/92403714/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] u-boot-tools: upgrading to 2022.07 FAILED

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-u-boot-tools-upgrade-2022.04-2022.07.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


0001-u-boot-tools-upgrade-2022.04-2022.07.patch
Description: Binary data
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.
Parsing recipes...done.
Parsing of 889 .bb files complete (887 cached, 2 parsed). 1660 targets, 36 
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   = "2.0.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "i686-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "4.1+snapshot-f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"
TUNE_FEATURES= "m32 core2"
TARGET_FPU   = ""
meta 
meta-poky
meta-yocto-bsp   = 
"tmp-auh-upgrades:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"
workspace= "master:f1d7e0f1d466a8cac540acbd7b166aa2d784ed00"

Initialising tasks...done.
Sstate summary: Wanted 21 Local 14 Mirrors 0 Missed 7 Current 246 (66% match, 
97% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 905 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_fetch)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_fetch: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_fetch: Succeeded
NOTE: Running task 1026 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_unpack)
NOTE: Running task 1027 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_prepare_recipe_sysroot)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_unpack: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_prepare_recipe_sysroot: 
Succeeded
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_unpack: Succeeded
NOTE: Running task 1028 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_patch)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_patch: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_patch: Succeeded
NOTE: Running task 1029 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_deploy_source_date_epoch)
NOTE: Running task 1030 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_populate_lic)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_deploy_source_date_epoch: 
Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_populate_lic: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_populate_lic: Succeeded
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_deploy_source_date_epoch: 
Succeeded
NOTE: Running task 1031 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_configure)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_configure: Started
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_configure: Succeeded
NOTE: Running task 1032 of 1039 
(/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-bsp/u-boot/u-boot-tools_2022.07.bb:do_compile)
NOTE: recipe u-boot-tools-1_2022.07-r0: task do_compile: Started
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 56 CROSS_COMPILE=i686-poky-linux- CC=i686-poky-linux-gcc  -m32 
-march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack-protector-strong  -O2 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security

[OE-core] [AUH] libuv: upgrading to 1.44.2 SUCCEEDED

Hello,

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

Next steps:
- apply the patch: git am 0001-libuv-upgrade-1.44.1-1.44.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/libuv: PKGV changed from 1.44.1 [default] to 
1.44.2 [default]
packages/core2-32-poky-linux/libuv: PV changed from "1.44.1" to "1.44.2"
packages/core2-32-poky-linux/libuv/libuv-dbg: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-dbg: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv-dbg: PKGSIZE changed from 581804 to 
582252 (+0%)
packages/core2-32-poky-linux/libuv/libuv-dev: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-dev: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv-doc: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-doc: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv-locale: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-locale: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv-src: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-src: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv-src: FILELIST: directory renamed 
/usr/src/debug/libuv/1.44.1-r0/git/include/uv -> 
/usr/src/debug/libuv/1.44.2-r0/git/include/uv, directory renamed 
/usr/src/debug/libuv/1.44.1-r0/git/src/unix -> 
/usr/src/debug/libuv/1.44.2-r0/git/src/unix, directory renamed 
/usr/src/debug/libuv/1.44.1-r0/git/include -> 
/usr/src/debug/libuv/1.44.2-r0/git/include, removed 
"/usr/src/debug/libuv/1.44.1-r0/git/src/strscpy.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/heap-inl.h 
/usr/src/debug/libuv/1.44.1-r0/git/src/version.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/timer.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/inet.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/threadpool.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/random.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/idna.h 
/usr/src/debug/libuv/1.44.1-r0/git/src/fs-poll.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/strscpy.h 
/usr/src/debug/libuv/1.44.1-r0/git/src/uv-common.h 
/usr/src/debug/libuv/1.44.1-r0/git/src/queue.h /usr/src/debug/lib
 uv/1.44.1-r0/git/src/uv-data-getter-setters.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/idna.c 
/usr/src/debug/libuv/1.44.1-r0/git/src/uv-common.c", added 
"/usr/src/debug/libuv/1.44.2-r0/git/src/inet.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/strscpy.h 
/usr/src/debug/libuv/1.44.2-r0/git/src/threadpool.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/uv-common.h 
/usr/src/debug/libuv/1.44.2-r0/git/src/queue.h 
/usr/src/debug/libuv/1.44.2-r0/git/src/random.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/fs-poll.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/strscpy.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/uv-common.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/uv-data-getter-setters.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/timer.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/heap-inl.h 
/usr/src/debug/libuv/1.44.2-r0/git/src/idna.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/version.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/strtok.h 
/usr/src/debug/libuv/1.44.2-r0/git/src/strtok.c 
/usr/src/debug/libuv/1.44.2-r0/git/src/idna.h"
packages/core2-32-poky-linux/libuv/libuv-src: PKGSIZE changed from 580688 to 
585513 (+1%)
packages/core2-32-poky-linux/libuv/libuv-staticdev: PKGV changed from 1.44.1 
[default] to 1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv-staticdev: PV changed from "1.44.1" to 
"1.44.2"
packages/core2-32-poky-linux/libuv/libuv: PKGV changed from 1.44.1 [default] to 
1.44.2 [default]
packages/core2-32-poky-linux/libuv/libuv: PV changed from "1.44.1" to "1.44.2"


0001-libuv-upgrade-1.44.1-1.44.2.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168067): 
https://lists.openembedded.org/g/openembedded-core/message/168067
Mute This Topic: https://lists.openembedded.org/mt/92403713/21656
Group Owner:

[OE-core] [AUH] systemd: upgrading to 251.3 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe systemd failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
WARNING: Host distribution "almalinux-8.6" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1660 entries from dependency cache.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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: 1 seconds
INFO: Extracting current version source...
INFO: SRC_URI contains some conditional appends/prepends - will create branches
to represent these
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto 516108f273888df3dcfa4f42b140252a285a2288
WARNING: Command 'git rebase 516108f273888df3dcfa4f42b140252a285a2288' failed:
Auto-merging src/core/systemd.pc.in
CONFLICT (content): Merge conflict in src/core/systemd.pc.in

You will need to resolve conflicts in order to complete the upgrade.
INFO: Rebasing devtool-override-libc-musl onto
516108f273888df3dcfa4f42b140252a285a2288
WARNING: Command 'git rebase 516108f273888df3dcfa4f42b140252a285a2288' failed:
Auto-merging src/core/systemd.pc.in
CONFLICT (content): Merge conflict in src/core/systemd.pc.in

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/systemd
INFO: New recipe is
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/systemd/systemd_251.3.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 (#168065):
https://lists.openembedded.org/g/openembedded-core/message/168065
Mute This Topic: https://lists.openembedded.org/mt/92403711/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] u-boot: upgrading to 2022.07 FAILED

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-u-boot-upgrade-2022.04-2022.07.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/u-boot: PKGV changed from 2022.04 [default] to 
2022.07 [default]
packages/qemux86-poky-linux/u-boot: PV changed from "2022.04" to "2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-dbg: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-dbg: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-dev: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-dev: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-doc: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-doc: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-env: PKGSIZE changed from 4611 to 
4618 (+0%)
packages/qemux86-poky-linux/u-boot/u-boot-env: FILELIST: removed 
"/etc/u-boot-initial-env-qemux86-2022.04-r0", added 
"/etc/u-boot-initial-env-qemux86-2022.07-r0"
packages/qemux86-poky-linux/u-boot/u-boot-env: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-env: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-extlinux: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-extlinux: PV changed from "2022.04" 
to "2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-locale: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-locale: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-src: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-src: PV changed from "2022.04" to 
"2022.07"
packages/qemux86-poky-linux/u-boot/u-boot-staticdev: PKGV changed from 2022.04 
[default] to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot-staticdev: PV changed from "2022.04" 
to "2022.07"
packages/qemux86-poky-linux/u-boot/u-boot: PKGSIZE changed from 711059 to 
725071 (+2%)
packages/qemux86-poky-linux/u-boot/u-boot: FILELIST: removed 
"/boot/u-boot-qemux86-2022.04-r0.bin", added 
"/boot/u-boot-qemux86-2022.07-r0.bin"
packages/qemux86-poky-linux/u-boot/u-boot: PKGV changed from 2022.04 [default] 
to 2022.07 [default]
packages/qemux86-poky-linux/u-boot/u-boot: PV changed from "2022.04" to 
"2022.07"


0001-u-boot-upgrade-2022.04-2022.07.patch
Description: Binary data
packages/qemux86-poky-linux/u-boot/u-boot-env: FILELIST: removed 
"/etc/u-boot-initial-env-qemux86-2022.04-r0", added 
"/etc/u-boot-initial-env-qemux86-2022.07-r0"
packages/qemux86-poky-linux/u-boot/u-boot: FILELIST: removed 
"/boot/u-boot-qemux86-2022.04-r0.bin", added 
"/boot/u-boot-qemux86-2022.07-r0.bin"
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 889 .bb files complete (0 cached, 889 parsed). 1660 targets, 70 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
ERROR: Nothing PROVIDES 'u-boot'
u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the 
qemuppc machine configuration.

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

[OE-core] [AUH] efibootmgr: upgrading to 18 FAILED

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe efibootmgr failed.
NOTE: Starting bitbake server...
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 889 .bb files complete (0 cached, 889 parsed). 1660 targets, 35 
skipped, 0 masked, 0 errors.

Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.6" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
NOTE: Resolving any missing task queue dependencies

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

Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 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: 1 seconds
INFO: Creating workspace layer in 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Rebasing devtool onto c3f9f0534e32158f62c43564036878b93b9e0fd6
WARNING: Command 'git rebase c3f9f0534e32158f62c43564036878b93b9e0fd6' failed:
Auto-merging src/efibootmgr.c
CONFLICT (content): Merge conflict in src/efibootmgr.c
Auto-merging src/efibootdump.c
CONFLICT (content): Merge conflict in src/efibootdump.c

You will need to resolve conflicts in order to complete the upgrade.
INFO: Using source tree as build directory since that would be the default for 
this recipe
INFO: Upgraded source extracted to 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/efibootmgr
INFO: New recipe is 
/home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/efibootmgr/efibootmgr_18.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 (#168064): 
https://lists.openembedded.org/g/openembedded-core/message/168064
Mute This Topic: https://lists.openembedded.org/mt/92403709/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/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)

On Wed, 2022-07-06 at 20:23 +0200, Alexander Kanavin wrote:
> This allows:
> 
> 1. Showing users where and how to define these settings correctly when 
> setting up
> a build from templates in poky (meta-poky/conf/site.conf.sample has commented
> out examples and was previously unused).
> 
> 2. Distributing site-specific settings with template configurations in other 
> layers,
> so there's no need to set them up separately.
> 
> Signed-off-by: Alexander Kanavin 
> ---
>  scripts/oe-setup-builddir | 6 +-
>  1 file changed, 5 insertions(+), 1 deletion(-)

We'd always intended that site.conf was more something the user would
setup once for their environment and not need to change. It was
therefore deliberately left out of the auto-setup piece.

I hadn't remembered we have an sample version of it. I think a sample
is fine as an example of how a site might setup a shared downloads
directory or common proxy information but I don't think the layer
should be installing it, particularly if it can trample an existing
file which I think the patch could as it stands.

As such I don't think this patch is the right thing to do.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168063): 
https://lists.openembedded.org/g/openembedded-core/message/168063
Mute This Topic: https://lists.openembedded.org/mt/92212803/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 v2] sstatesig: Include all dependencies in SPDX task signatures

2022-07-15 Thread Joshua Watt

SDPX generation involves looking through BB_TASKDEPDATA for
dependencies, then linking to the generated documents for those
dependencies. These document links use a checksum to validate the
document, which means that if a upstream document changes, all
downstream documents must be regenerated to get the new checksum,
otherwise the compendium of documents produced by the build will have
broken links; therefore all dependent task should be included in the
signature (even from "ABI safe" recipes).

Signed-off-by: Joshua Watt 
---
 meta/lib/oe/sstatesig.py | 9 +
 1 file changed, 9 insertions(+)

diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 7150bd0929..de65244932 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -24,10 +24,19 @@ def sstate_rundepfilter(siggen, fn, recipename, task, dep, 
depname, dataCaches):
 return "/allarch.bbclass" in inherits
 def isImage(mc, fn):
 return "/image.bbclass" in " ".join(dataCaches[mc].inherits[fn])
+def isSPDXTask(task):
+return task in ("do_create_spdx", "do_create_runtime_spdx")
 
 depmc, _, deptaskname, depmcfn = bb.runqueue.split_tid_mcfn(dep)
 mc, _ = bb.runqueue.split_mc(fn)
 
+# Keep all dependencies between SPDX tasks in the signature. SPDX documents
+# are linked together by hashes, which means if a dependent document 
changes,
+# all downstream documents must be re-written (even if they are "safe"
+# dependencies).
+if isSPDXTask(task) and isSPDXTask(deptaskname):
+return True
+
 # (Almost) always include our own inter-task dependencies (unless it comes
 # from a mcdepends). The exception is the special
 # do_kernel_configme->do_unpack_and_patch dependency from archiver.bbclass.
-- 
2.33.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168062): 
https://lists.openembedded.org/g/openembedded-core/message/168062
Mute This Topic: https://lists.openembedded.org/mt/92400958/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] python3-picobuild: upgrade to 0.2

2022-07-15 Thread Ross Burton

Major features since 0.1:
- Implement support for legacy source trees
- Add option to loosen dependency checking

Signed-off-by: Ross Burton 
---
 .../{python3-picobuild_0.1.bb => python3-picobuild_0.2.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-picobuild_0.1.bb => 
python3-picobuild_0.2.bb} (95%)

diff --git a/meta/recipes-devtools/python/python3-picobuild_0.1.bb 
b/meta/recipes-devtools/python/python3-picobuild_0.2.bb
similarity index 95%
rename from meta/recipes-devtools/python/python3-picobuild_0.1.bb
rename to meta/recipes-devtools/python/python3-picobuild_0.2.bb
index 3c92b079f39..99e4cb87618 100644
--- a/meta/recipes-devtools/python/python3-picobuild_0.1.bb
+++ b/meta/recipes-devtools/python/python3-picobuild_0.2.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=6c811a9fbdf5641ff0b0d43fbbb440e5 \
 "
 
 SRC_URI = 
"git://gitlab.com/rossburton/picobuild.git;protocol=https;branch=main"
-SRCREV = "3441d5500a5ad23a44027576cf5261c3b7c1d6b0"
+SRCREV = "ed3b16ce48d91df181e5f5d77b9bbc2577b3fd9d"
 PV .= "+git${SRCPV}"
 
 S = "${WORKDIR}/git"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168061): 
https://lists.openembedded.org/g/openembedded-core/message/168061
Mute This Topic: https://lists.openembedded.org/mt/92399601/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 v2 2/2] zlib: minizip: add recipe

2022-07-15 Thread Sean Nyekjaer

Add the minizip library for use as a dependency.
zlib doesn't support vanilla autotools, but atleast this minizip does.
minizip does depend on zlib, so combining these recipes turns out to be
a quite hacky approach.

Signed-off-by: Sean Nyekjaer 
---
Should we keep Denys Dmytriyenko  as maintainer here?
It's after all the same artifact that is used for both recipes?

 meta/conf/distro/include/maintainers.inc |  1 +
 meta/recipes-core/zlib/minizip_1.2.12.bb | 15 +++
 2 files changed, 16 insertions(+)
 create mode 100644 meta/recipes-core/zlib/minizip_1.2.12.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index a69af3d780..1db5cadbcf 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -506,6 +506,7 @@ RECIPE_MAINTAINER:pn-meta-world-pkgdata = "Richard Purdie 
http://zlib.net/;
+SECTION = "libs"
+LICENSE = "Zlib"
+LIC_FILES_CHKSUM = 
"file://MiniZip64_info.txt;beginline=53;endline=73;md5=02090b3a3511ed8a910b77dae6906cea"
+
+include zlib.inc
+
+inherit autotools
+
+DEPENDS = "zlib"
+
+S = "${WORKDIR}/zlib-${PV}/contrib/minizip"
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.37.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168060): 
https://lists.openembedded.org/g/openembedded-core/message/168060
Mute This Topic: https://lists.openembedded.org/mt/92398813/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 v2 1/2] zlib: split SRC_URI into inc file

2022-07-15 Thread Sean Nyekjaer

This is done in preparation for adding packages from the zlib contrib
directory.
Unfortunatly it's not possible to add these via pkgconfig.

Signed-off-by: Sean Nyekjaer 
---
With this we are maintaining the same verison number for both zlib and
minizip in the recipe name. Would it be better to have it in the inc
file?

PV = "1.2.12" ?

 meta/recipes-core/zlib/zlib.inc   |  4 
 meta/recipes-core/zlib/zlib_1.2.12.bb | 18 +-
 2 files changed, 13 insertions(+), 9 deletions(-)
 create mode 100644 meta/recipes-core/zlib/zlib.inc

diff --git a/meta/recipes-core/zlib/zlib.inc b/meta/recipes-core/zlib/zlib.inc
new file mode 100644
index 00..b607a82312
--- /dev/null
+++ b/meta/recipes-core/zlib/zlib.inc
@@ -0,0 +1,4 @@
+SRC_URI = "https://zlib.net/zlib-${PV}.tar.xz;
+UPSTREAM_CHECK_URI = "http://zlib.net/;
+
+SRC_URI[sha256sum] = 
"7db46b8d7726232a621befaab4a1c870f00a90805511c0e0090441dac57def18"
diff --git a/meta/recipes-core/zlib/zlib_1.2.12.bb 
b/meta/recipes-core/zlib/zlib_1.2.12.bb
index e921703137..ba986d8cf2 100644
--- a/meta/recipes-core/zlib/zlib_1.2.12.bb
+++ b/meta/recipes-core/zlib/zlib_1.2.12.bb
@@ -6,16 +6,16 @@ SECTION = "libs"
 LICENSE = "Zlib"
 LIC_FILES_CHKSUM = 
"file://zlib.h;beginline=6;endline=23;md5=5377232268e952e9ef63bc555f7aa6c0"
 
-SRC_URI = "https://zlib.net/${BP}.tar.xz \
-   file://cc.patch \
-   file://ldflags-tests.patch \
-   file://0001-configure-Pass-LDFLAGS-to-link-tests.patch \
-   file://run-ptest \
-   
file://0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch \
-   "
-UPSTREAM_CHECK_URI = "http://zlib.net/;
+include zlib.inc
+
+SRC_URI += "file://cc.patch \
+file://ldflags-tests.patch \
+file://0001-configure-Pass-LDFLAGS-to-link-tests.patch \
+file://run-ptest \
+
file://0001-Correct-incorrect-inputs-provided-to-the-CRC-functio.patch \
+"
 
-SRC_URI[sha256sum] = 
"7db46b8d7726232a621befaab4a1c870f00a90805511c0e0090441dac57def18"
+UPSTREAM_CHECK_URI = "http://zlib.net/;
 
 CFLAGS += "-D_REENTRANT"
 
-- 
2.37.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168059): 
https://lists.openembedded.org/g/openembedded-core/message/168059
Mute This Topic: https://lists.openembedded.org/mt/92398812/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] rootfs-postcommands.bbclass: move host-user-contaminated.txt to ${S}

2022-07-15 Thread Ming Liu

From: Ming Liu 

This is to ensure host-user-contaminated.txt would be removed before
do_rootfs runs, since ${S} is in cleandirs of do_rootfs, otherwise, a
host-user-contaminated.txt file that generated from previous builds
could be used which is wrong.

Signed-off-by: Ming Liu 
---
 meta/classes/rootfs-postcommands.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/rootfs-postcommands.bbclass 
b/meta/classes/rootfs-postcommands.bbclass
index 452b87f9b3..a8a952f31d 100644
--- a/meta/classes/rootfs-postcommands.bbclass
+++ b/meta/classes/rootfs-postcommands.bbclass
@@ -305,7 +305,7 @@ rootfs_trim_schemas () {
 }
 
 rootfs_check_host_user_contaminated () {
-   contaminated="${WORKDIR}/host-user-contaminated.txt"
+   contaminated="${S}/host-user-contaminated.txt"
HOST_USER_UID="$(PSEUDO_UNLOAD=1 id -u)"
HOST_USER_GID="$(PSEUDO_UNLOAD=1 id -g)"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168058): 
https://lists.openembedded.org/g/openembedded-core/message/168058
Mute This Topic: https://lists.openembedded.org/mt/92398381/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] oeqa/selftest/sstatetests: Update test to work with bitbake changes

Bitbake is dropping the DL_DIR fallback for local file urls and ensuring
local urls are fetchable. This test fails as it copies the meta directory
of COREBASE but not scripts and nativesdk-qemu-helper references runqemu
from there which doesn't exist in the copied data.

Tweak to symlink scripts into position in the copied metadata which
avoids the now fatal parsing error.

Signed-off-by: Richard Purdie 
---
 meta/lib/oeqa/selftest/cases/sstatetests.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py 
b/meta/lib/oeqa/selftest/cases/sstatetests.py
index 4a32af902fb..4749f28ab8c 100644
--- a/meta/lib/oeqa/selftest/cases/sstatetests.py
+++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
@@ -594,6 +594,7 @@ BB_SIGNATURE_HANDLER = "OEBasicHash"
 copy_layer_2 = self.topdir + "/meta-copy2/meta"
 
 oe.path.copytree(core_layer, copy_layer_1)
+os.symlink(os.path.dirname(core_layer) + "/scripts", self.topdir + 
"/meta-copy1/scripts")
 self.write_config("""
 TMPDIR = "${TOPDIR}/tmp-sstatesamehash"
 """)
@@ -603,6 +604,7 @@ TMPDIR = "${TOPDIR}/tmp-sstatesamehash"
 bitbake("bash -S none")
 
 oe.path.copytree(core_layer, copy_layer_2)
+os.symlink(os.path.dirname(core_layer) + "/scripts", self.topdir + 
"/meta-copy2/scripts")
 self.write_config("""
 TMPDIR = "${TOPDIR}/tmp-sstatesamehash2"
 """)
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168057): 
https://lists.openembedded.org/g/openembedded-core/message/168057
Mute This Topic: https://lists.openembedded.org/mt/92398314/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] gcc-runtime: Fix missing MLPREFIX in debug mappings