Date   

Re: [PATCH v2] glibc: ptest: Fix glibc-tests package issue

Richard Purdie
 

On Sat, 2022-04-16 at 00:54 -0700, pgowda wrote:
The current default DISTRO_FEATURES does not support ptest.
Hence, the following error is generated during "bitbake glibc-tests".
ERROR: glibc-tests-2.35-r0 do_package: QA Issue: glibc-tests:
Files/directories were installed but not shipped in any package
The issue is not reproduced with "DISTRO = Yocto" as DISTRO_FEATURES
in Yocto supports ptest. However, when we run "glibc-tests" using
Open-embedded master sources; it generates the error as default
DISTRO is used.

Signed-off-by: pgowda <pgowda.cve@...>
---
meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/glibc/glibc-tests_2.35.bb b/meta/recipes-core/glibc/glibc-tests_2.35.bb
index 8c7ecf89ba..fc6eee91ec 100644
--- a/meta/recipes-core/glibc/glibc-tests_2.35.bb
+++ b/meta/recipes-core/glibc/glibc-tests_2.35.bb
@@ -29,6 +29,8 @@ RRECOMMENDS:${PN} = ""
RDEPENDS:${PN} = " glibc sed"
DEPENDS:append = " sed"

+DISTRO_FEATURES:append = " ptest"
+
# Just build tests for target - do not run them
do_check:append () {
oe_runmake -i check run-built-tests=no
This isn't what I meant. I meant something like:

REQUIRED_DISTRO_FEATURES = 'ptest'
inherit features_check

Cheers,

Richard


Re: [RFT][PATCH v3] gcc: upgrade 11.2 -> current gcc-12 snapshot

Richard Purdie
 

On Fri, 2022-04-15 at 10:38 -0700, Khem Raj wrote:
From: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@...>

- gcc 12 is in RC stages.
- Add patch to re-shuffle include of sched.h to fix build on musl

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@...>
Signed-off-by: Khem Raj <raj.khem@...>
---
v3
- Switch to own snapshot for quick turnarounds than waiting for a
weekly snapshot
- Add a fix for gcc target build on musl
- Fixed gcc for kernel build failures on arm/x86_64
- Fixed gcc for ccache build failure
I ran this through the autobuilder as requested as it means we have a chance to
get things fixed upstream before gcc 12 is released:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3535

We see failures in:

edgerouter/edgerouter-alt in linux-yocto 5.15/5.10:
https://autobuilder.yoctoproject.org/typhoon/#/builders/62/builds/5078
https://autobuilder.yoctoproject.org/typhoon/#/builders/111/builds/2965

meta-arm in linux-yocto 5.15:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2307

meta-intel in intel-media-driver:
https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/2770

qemuppc/qemuppc-alt in linux-yocto 5.15/5.10:
https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5033
https://autobuilder.yoctoproject.org/typhoon/#/builders/107/builds/2916

Four oe-selftest failures due to missing maintainer entries (easy fix)

A weird oe-selftest prservice.BitbakePrTests.test_import_export_override_db:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3409/steps/14/logs/stdio

The latter is one of our infamous intermittent issues and likely not gcc 12
"""
Parsing recipes...ERROR: ParseError in None: Not all recipes parsed, parser
thread killed/died? Exiting.
ERROR: Parsing halted due to errors, see error messages above
"""

So basically you have the intel-media-driver failure in meta-intel and a number
of kernel issues. I've cc'd a few of the maintainers just so they're aware of
the status, I appreciate we'd wait for the mainline kernel to resolve things.

Cheers,

Richard


Re: [PATCH] [PATCH] glibc: ptest: Fix glibc-tests package issue

Pgowda
 

Hi Richard,

Thanks very much for mentioning the correct way of fixing the issue.

The modified patch is posted as:-
https://lists.openembedded.org/g/openembedded-core/message/164524

Please let me know whether it's the way you mentioned it.
Or Can you please point me to other instances where it's been implemented.

Thanks & Regards
Pgowda

On Fri, Apr 15, 2022 at 6:32 PM Richard Purdie
<richard.purdie@...> wrote:

On Fri, 2022-04-15 at 04:11 -0700, pgowda wrote:
The current default DISTRO_FEATURES does not support ptest.
Hence, the following error is generated during "bitbake glibc-tests".
ERROR: glibc-tests-2.35-r0 do_package: QA Issue: glibc-tests:
Files/directories were installed but not shipped in any package
The issue is not reproduced with "DISTRO = Yocto" as DISTRO_FEATURES
in Yocto supports ptest. However, when we run "glibc-tests" using
Open-embedded master sources; it generates the error as default
DISTRO is used.

Signed-off-by: pgowda <pgowda.cve@...>
---
meta/conf/distro/include/default-distrovars.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This isn't quite the right approach, we should probably skip parsing of glibc-
tests if ptests aren't in DISTRO_FEATURES?

Cheers,

Richard


[PATCH v2] glibc: ptest: Fix glibc-tests package issue

Pgowda
 

The current default DISTRO_FEATURES does not support ptest.
Hence, the following error is generated during "bitbake glibc-tests".
ERROR: glibc-tests-2.35-r0 do_package: QA Issue: glibc-tests:
Files/directories were installed but not shipped in any package
The issue is not reproduced with "DISTRO = Yocto" as DISTRO_FEATURES
in Yocto supports ptest. However, when we run "glibc-tests" using
Open-embedded master sources; it generates the error as default
DISTRO is used.

Signed-off-by: pgowda <pgowda.cve@...>
---
meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/glibc/glibc-tests_2.35.bb b/meta/recipes-core/glibc/glibc-tests_2.35.bb
index 8c7ecf89ba..fc6eee91ec 100644
--- a/meta/recipes-core/glibc/glibc-tests_2.35.bb
+++ b/meta/recipes-core/glibc/glibc-tests_2.35.bb
@@ -29,6 +29,8 @@ RRECOMMENDS:${PN} = ""
RDEPENDS:${PN} = " glibc sed"
DEPENDS:append = " sed"

+DISTRO_FEATURES:append = " ptest"
+
# Just build tests for target - do not run them
do_check:append () {
oe_runmake -i check run-built-tests=no
--
2.35.1


[PATCH] ethtool: upgrade 5.16 -> 5.17

Changhyeok Bae
 

Signed-off-by: Changhyeok Bae <changhyeok.bae@...>
---
.../recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch | 2 +-
.../ethtool/{ethtool_5.16.bb => ethtool_5.17.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/ethtool/{ethtool_5.16.bb => ethtool_5.17.bb} (93%)

diff --git a/meta/recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch b/meta/recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch
index 034dc92444..7f859f40ed 100644
--- a/meta/recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch
+++ b/meta/recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch
@@ -19,7 +19,7 @@ index 8fc93c8..94ee28d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,7 +2,7 @@ dnl Process this file with autoconf to produce a configure script.
- AC_INIT(ethtool, 5.16, netdev@...)
+ AC_INIT(ethtool, 5.17, netdev@...)
AC_PREREQ(2.52)
AC_CONFIG_SRCDIR([ethtool.c])
-AM_INIT_AUTOMAKE([gnu subdir-objects])
diff --git a/meta/recipes-extended/ethtool/ethtool_5.16.bb b/meta/recipes-extended/ethtool/ethtool_5.17.bb
similarity index 93%
rename from meta/recipes-extended/ethtool/ethtool_5.16.bb
rename to meta/recipes-extended/ethtool/ethtool_5.17.bb
index 5dca03d082..61032d4836 100644
--- a/meta/recipes-extended/ethtool/ethtool_5.16.bb
+++ b/meta/recipes-extended/ethtool/ethtool_5.17.bb
@@ -11,7 +11,7 @@ SRC_URI = "${KERNELORG_MIRROR}/software/network/ethtool/ethtool-${PV}.tar.gz \
file://avoid_parallel_tests.patch \
"

-SRC_URI[sha256sum] = "4160fa127d75d5a6ebd5e871118486ac730dea2f28b2f1ad40fd1ed3d0d369e0"
+SRC_URI[sha256sum] = "3e32735d13aa19e2be32d3528ef8a135fc99782950ab3fa602198e72992e9450"

UPSTREAM_CHECK_URI = "https://www.kernel.org/pub/software/network/ethtool/"

--
2.17.1


[AUH] vte: upgrading to 0.68.0 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-vte-upgrade-0.66.2-0.68.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


[AUH] Upgrade status: 2022-04-15

Auto Upgrade Helper
 

Recipe upgrade statistics:

* Failed(do_compile): 12
u-boot-tools, 2022.04, Marek Vasut <marek.vasut@...>
u-boot, 2022.04, Marek Vasut <marek.vasut@...>
util-linux-libuuid, 2.38, Chen Qi <Qi.Chen@...>
util-linux, 2.38, Chen Qi <Qi.Chen@...>
cmake, 3.23.1, Pascal Bach <pascal.bach@...>
python3-pyparsing, 3.0.8, Oleksandr Kravchuk <open.source@...>
python3-typing-extensions, 4.1.1, Tim Orling <tim.orling@...>
mc, 4.8.28, Ross Burton <ross.burton@...>
stress-ng, 0.14.00, Anuj Mittal <anuj.mittal@...>
gdk-pixbuf, 2.42.8, Ross Burton <ross.burton@...>
librsvg, 2.54.0, Anuj Mittal <anuj.mittal@...>
libgcrypt, 1.10.1, Hongxu Jia <hongxu.jia@...>
* Succeeded: 50
openssh, 9.0p1, Unassigned <unassigned@...>
expat, 2.4.8, Yi Zhao <yi.zhao@...>
sysvinit, 3.03, Ross Burton <ross.burton@...>
apt, 2.4.5, Aníbal Limón <limon.anibal@...>
createrepo-c, 0.20.0, Alexander Kanavin <alex.kanavin@...>
dpkg, 1.21.7, Aníbal Limón <limon.anibal@...>
git, 2.35.3, Robert Yang <liezhi.yang@...>
help2man, 1.49.2, Hongxu Jia <hongxu.jia@...>
json-c, 0.16, Yi Zhao <yi.zhao@...>
mtools, 4.0.39, Anuj Mittal <anuj.mittal@...>
python3-dbusmock, 0.27.5, Oleksandr Kravchuk <open.source@...>
python3-dtschema, 2022.3.2, Bruce Ashfield <bruce.ashfield@...>
python3-hypothesis, 6.43.1, Tim Orling <tim.orling@...>
python3-jsonpointer, 2.3, Bruce Ashfield <bruce.ashfield@...>
python3-mako, 1.2.0, Oleksandr Kravchuk <open.source@...>
python3-pip, 22.0.4, Zang Ruochen <zangrc.fnst@...>
python3-sphinx-rtd-theme, 1.0.0, Tim Orling <tim.orling@...>
python3-sphinx, 4.5.0, Tim Orling <tim.orling@...>
python3-zipp, 3.8.0, Tim Orling <tim.orling@...>
repo, 2.23, Jasper Orschulko <Jasper.Orschulko@...>
ruby, 3.1.2, Ross Burton <ross.burton@...>
strace, 5.17, Robert Yang <liezhi.yang@...>
acpica, 20220331, Ross Burton <ross.burton@...>
ethtool, 5.17, Changhyeok Bae <changhyeok.bae@...>
ghostscript, 9.56.1, Hongxu Jia <hongxu.jia@...>
libaio, 0.3.113, Alexander Kanavin <alex.kanavin@...>
libmnl, 1.0.5, Khem Raj <raj.khem@...>
epiphany, 42.1, Alexander Kanavin <alex.kanavin@...>
adwaita-icon-theme, 42.0, Ross Burton <ross.burton@...>
libhandy, 1.6.1, Alexander Kanavin <alex.kanavin@...>
fontconfig, 2.14.0, Ross Burton <ross.burton@...>
freetype, 2.12.0, Ross Burton <ross.burton@...>
harfbuzz, 4.2.0, Anuj Mittal <anuj.mittal@...>
mesa, 22.0.1, Otavio Salvador <otavio.salvador@...>
pango, 1.50.7, Ross Burton <ross.burton@...>
libx11, 1.7.5, Unassigned <unassigned@...>
xwayland, 22.1.1, Unassigned <unassigned@...>
linux-firmware, 20220411, Otavio Salvador <otavio.salvador@...>
lttng-tools, 2.13.7, Richard Purdie <richard.purdie@...>
wireless-regdb, 2022.04.08, Adrian Bunk <bunk@...>
ffmpeg, 5.0.1, Alexander Kanavin <alex.kanavin@...>
boost, 1.79.0, Alexander Kanavin <alex.kanavin@...>
diffoscope, 209, Joshua Watt <JPEWhacker@...>
libbsd, 0.11.6, Yi Zhao <yi.zhao@...>
libcap, 2.64, Yi Zhao <yi.zhao@...>
libgit2, 1.4.3, Unassigned <unassigned@...>
libsoup, 3.0.6, Anuj Mittal <anuj.mittal@...>
libusb1, 1.0.26, Anuj Mittal <anuj.mittal@...>
shared-mime-info, 2.2, Anuj Mittal <anuj.mittal@...>
vte, 0.68.0, Anuj Mittal <anuj.mittal@...>
* Failed (devtool error): 29
dropbear, 2022.82, Yi Zhao <yi.zhao@...>
glib-2.0, 2.72.1, Anuj Mittal <anuj.mittal@...>
zlib, 1.2.12, Denys Dmytriyenko <denis@...>
gptfdisk, 1.0.9, Alexander Kanavin <alex.kanavin@...>
gnu-config, 20211108-new-commits-available, Robert Yang <liezhi.yang@...>
go-runtime, 1.18.1, Khem Raj <raj.khem@...>
go, 1.18.1, Khem Raj <raj.khem@...>
llvm, 14.0.1, Khem Raj <raj.khem@...>
meson, 0.62.0, Alexander Kanavin <alex.kanavin@...>
python3-setuptools, 62.1.0, Oleksandr Kravchuk <open.source@...>
libstd-rs, 1.60.0, Randy MacLeod <Randy.MacLeod@...>
rust-llvm, 1.60.0, Randy MacLeod <Randy.MacLeod@...>
squashfs-tools, 4.5.1, Robert Yang <liezhi.yang@...>
subversion, 1.14.2, Richard Purdie <richard.purdie@...>
valgrind, 3.19.0, Alexander Kanavin <alex.kanavin@...>
go-helloworld, 0.1-new-commits-available, Khem Raj <raj.khem@...>
procps, 4.0.0, Alexander Kanavin <alex.kanavin@...>
piglit, 1.0-new-commits-available, Ross Burton <ross.burton@...>
mkfontscale, 1.2.2, Unassigned <unassigned@...>
xdpyinfo, 1.3.3, Unassigned <unassigned@...>
libxcursor, 1.2.1, Unassigned <unassigned@...>
libxvmc, 1.0.13, Unassigned <unassigned@...>
kexec-tools, 2.0.24, Unassigned <unassigned@...>
libsndfile1, 1.1.0, Unassigned <unassigned@...>
at-spi2-core, 2.44.0, Tim Orling <tim.orling@...>
icu, 71.1, Alexander Kanavin <alex.kanavin@...>
libcap-ng-python, 0.8.3, Yi Zhao <yi.zhao@...>
libcap-ng, 0.8.3, Yi Zhao <yi.zhao@...>
libgpg-error, 1.45, Hongxu Jia <hongxu.jia@...>
* Failed(other errors): 2
cargo, 1.60.0, Randy MacLeod <Randy.MacLeod@...>
vulkan-samples, git-new-commits-available, Ross Burton <ross.burton@...>

TOTAL: attempted=93 succeeded=50(53.76%) failed=43(46.24%)

Recipe upgrade statistics per Maintainer:

Changhyeok Bae <changhyeok.bae: attempted=1 succeeded=1(100.00%) failed=0(0.00%)
Zang Ruochen <zangrc.fnst: attempted=1 succeeded=1(100.00%) failed=0(0.00%)
Ross Burton <ross.burton: attempted=11 succeeded=7(63.64%) failed=4(36.36%)
Aníbal Limón <limon.anibal: attempted=2 succeeded=2(100.00%) failed=0(0.00%)
Richard Purdie <richard.purdie: attempted=2 succeeded=1(50.00%) failed=1(50.00%)
Pascal Bach <pascal.bach: attempted=1 succeeded=0(0.00%) failed=1(100.00%)
Alexander Kanavin <alex.kanavin: attempted=11 succeeded=6(54.55%) failed=5(45.45%)
Jasper Orschulko <Jasper.Orschulko: attempted=1 succeeded=1(100.00%) failed=0(0.00%)
Adrian Bunk <bunk: attempted=1 succeeded=1(100.00%) failed=0(0.00%)
Hongxu Jia <hongxu.jia: attempted=4 succeeded=2(50.00%) failed=2(50.00%)
Oleksandr Kravchuk <open.source: attempted=4 succeeded=2(50.00%) failed=2(50.00%)
Marek Vasut <marek.vasut: attempted=2 succeeded=0(0.00%) failed=2(100.00%)
Joshua Watt <JPEWhacker: attempted=1 succeeded=1(100.00%) failed=0(0.00%)
Anuj Mittal <anuj.mittal: attempted=9 succeeded=6(66.67%) failed=3(33.33%)
Yi Zhao <yi.zhao: attempted=7 succeeded=4(57.14%) failed=3(42.86%)
Bruce Ashfield <bruce.ashfield: attempted=2 succeeded=2(100.00%) failed=0(0.00%)
Robert Yang <liezhi.yang: attempted=4 succeeded=2(50.00%) failed=2(50.00%)
Otavio Salvador <otavio.salvador: attempted=2 succeeded=2(100.00%) failed=0(0.00%)
Unassigned <unassigned: attempted=10 succeeded=4(40.00%) failed=6(60.00%)
Denys Dmytriyenko <denis: attempted=1 succeeded=0(0.00%) failed=1(100.00%)
Randy MacLeod <Randy.MacLeod: attempted=3 succeeded=0(0.00%) failed=3(100.00%)
Chen Qi <Qi.Chen: attempted=2 succeeded=0(0.00%) failed=2(100.00%)
Tim Orling <tim.orling: attempted=6 succeeded=4(66.67%) failed=2(33.33%)
Khem Raj <raj.khem: attempted=5 succeeded=1(20.00%) failed=4(80.00%)


[AUH] libusb1: upgrading to 1.0.26 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-libusb1-upgrade-1.0.25-1.0.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


[AUH] lttng-tools: upgrading to 2.13.7 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-lttng-tools-upgrade-2.13.4-2.13.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


[AUH] libgcrypt: upgrading to 1.10.1 FAILED

Auto Upgrade Helper
 

Hello,

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

Detailed error information:

do_compile failed



Next steps:
- apply the patch: git am 0001-libgcrypt-upgrade-1.9.4-1.10.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


[AUH] shared-mime-info: upgrading to 2.2 SUCCEEDED

Auto Upgrade Helper
 

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *shared-mime-info* to *2.2* has Succeeded.

Next steps:
- apply the patch: git am 0001-shared-mime-info-upgrade-2.1-2.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


[AUH] libsoup: upgrading to 3.0.6 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-libsoup-upgrade-3.0.5-3.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


[AUH] libgpg-error: upgrading to 1.45 FAILED

Auto Upgrade Helper
 

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe libgpg-error failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1640 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:945d3905ead0bce43330f7adbbc2a01ddf1bff58"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% 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
Loading cache...done.
Loaded 1640 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1641 targets, 34 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:945d3905ead0bce43330f7adbbc2a01ddf1bff58"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

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
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 100% |####################################| Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching https://www.gnupg.org/ftp/gcrypt/libgpg-error/libgpg-error-1.45.tar.bz2...
INFO: Rebasing devtool onto 124be0f88822cbb87d086de5ba8c562a3faaefbc
WARNING: Command 'git rebase 124be0f88822cbb87d086de5ba8c562a3faaefbc' failed:
Auto-merging src/gpg-error.m4
CONFLICT (content): Merge conflict in src/gpg-error.m4

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/libgpg-error
INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libgpg-error/libgpg-error_1.45.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


[AUH] libgit2: upgrading to 1.4.3 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-libgit2-upgrade-1.4.2-1.4.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


[AUH] at-spi2-core: upgrading to 2.44.0 FAILED

Auto Upgrade Helper
 

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *at-spi2-core* to *2.44.0* has Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe at-spi2-core failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1640 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:47da4a658ac7ba3bd231d2ba6af5638b2c1eed64"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% 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: 1 seconds
Loading cache...done.
Loaded 1640 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1641 targets, 34 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:47da4a658ac7ba3bd231d2ba6af5638b2c1eed64"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% 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: 1 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 100% |####################################| Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching https://download.gnome.org/sources//at-spi2-core/2.44/at-spi2-core-2.44.0.tar.xz...
INFO: Rebasing devtool onto 5e0bc55ad9cc6e3979568c44ef8a9400555f34e8
WARNING: Command 'git rebase 5e0bc55ad9cc6e3979568c44ef8a9400555f34e8' failed:
Auto-merging meson.build
CONFLICT (content): Merge conflict in 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/at-spi2-core
INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/at-spi2-core/at-spi2-core_2.44.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


[AUH] boost: upgrading to 1.79.0 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-boost-upgrade-1.78.0-1.79.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


[AUH] libcap-ng-python: upgrading to 0.8.3 FAILED

Auto Upgrade Helper
 

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libcap-ng-python* to *0.8.3* has Failed (devtool error).

Detailed error information:

Running 'devtool upgrade' for recipe libcap-ng-python failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1640 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:ef5b10a6ccf2abbdc56902cce442d8c4eacabf37"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% 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
Loading cache...done.
Loaded 1640 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1641 targets, 34 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:ef5b10a6ccf2abbdc56902cce442d8c4eacabf37"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

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
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 100% |####################################| Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching https://people.redhat.com/sgrubb/libcap-ng/libcap-ng-0.8.3.tar.gz...
INFO: Rebasing devtool onto 8be2c7f3d0a67465388304e5f57972ccc1f533e1
WARNING: Command 'git rebase 8be2c7f3d0a67465388304e5f57972ccc1f533e1' failed:
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/libcap-ng-python
INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libcap-ng-python/libcap-ng-python_0.8.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


[AUH] diffoscope: upgrading to 209 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-208-209.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


[AUH] libcap: upgrading to 2.64 SUCCEEDED

Auto Upgrade Helper
 

Hello,

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

Next steps:
- apply the patch: git am 0001-libcap-upgrade-2.63-2.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


[AUH] libcap-ng: upgrading to 0.8.3 FAILED

Auto Upgrade Helper
 

Hello,

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

Detailed error information:

Running 'devtool upgrade' for recipe libcap-ng failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1640 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:ef5b10a6ccf2abbdc56902cce442d8c4eacabf37"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

Initialising tasks...done.
Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% 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
Loading cache...done.
Loaded 1640 entries from dependency cache.
Parsing recipes...done.
Parsing of 883 .bb files complete (881 cached, 2 parsed). 1641 targets, 34 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.0"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "tmp-auh-upgrades:ef5b10a6ccf2abbdc56902cce442d8c4eacabf37"
workspace = "master:81b4d8bc6bdc47a731a1f7ed741d7336559a1348"

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
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
DEBUG 5 [Errno 25] Inappropriate ioctl for device
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 0% | | ETA: --:--:--
Adding changed files: 100% |####################################| Time: 0:00:00
INFO: Extracting current version source...
INFO: Extracting upgraded version source...
INFO: Fetching https://people.redhat.com/sgrubb/libcap-ng/libcap-ng-0.8.3.tar.gz...
INFO: Rebasing devtool onto ae585a68905ebea178ceea50f90a1708d317dbc2
WARNING: Command 'git rebase ae585a68905ebea178ceea50f90a1708d317dbc2' failed:
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/libcap-ng
INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/libcap-ng/libcap-ng_0.8.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

9461 - 9480 of 173978