On Sat, 2022-04-02 at 01:59 +0200, Peter Kjellerstedt wrote:
> Adding "patch-fuzz" to ERROR_QA should trigger the patch tasks to
> rerun to make sure any already existing fuzz is caught. This is
> achieved by using bb.utils.filter() to see if "patch-fuzz" is in
> ERROR_QA/WARN_QA as it adds whether
Fixed when opengl is not in DISTRO_FEATURES:
ERROR: Nothing PROVIDES 'virtual/libgbm' (but /path/to/waffle/waffle_1.7.0.bb
DEPENDS on or otherwise requires it)
Signed-off-by: Robert Yang
---
meta/recipes-graphics/waffle/waffle_1.7.0.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
di
The following changes since commit ff75909f2a9e970aaf389e0012888c29f02376e3:
meson: Robustify compiler detection logic (2022-04-01 23:11:32 +0100)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/pc
http://cgit.openembedded.org/openembedded-c
If "empty-dirs" is in ERROR_QA, then changes to QA_EMPTY_DIRS should
trigger the package_qa tasks to be rerun.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/insane.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 873
If a QA test is added to ERROR_QA, all package_qa tasks should rerun
to make sure any already existing errors are caught.
Signed-off-by: Peter Kjellerstedt
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.co
Adding "patch-fuzz" to ERROR_QA should trigger the patch tasks to
rerun to make sure any already existing fuzz is caught. This is
achieved by using bb.utils.filter() to see if "patch-fuzz" is in
ERROR_QA/WARN_QA as it adds whether the filtered strings are set or
not to the task hash.
Since the mec
Signed-off-by: Peter Kjellerstedt
---
meta/recipes-devtools/python/python3-jinja2_3.1.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-jinja2_3.1.1.bb
b/meta/recipes-devtools/python/python3-jinja2_3.1.1.bb
index 0a2bcd71f5..c38686a5c2
Not sure if this is working correctly, with opkg
and python3-cryptography-ptest included in the image I get:
* Solver encountered 1 problem(s):
* Problem 1/1:
* - conflicting requests
* - nothing provides python3-cryptography-vectors = 36.0.2 needed by
python3-cryptography-ptest-36.0.2-r0.
Signed-off-by: Martin Jansa
---
...e-warning-with-glibc-2.34-on-Linux-p.patch | 32 +++
...-elide-a-warning-that-caused-Solaris.patch | 24 ++
meta/recipes-support/boost/boost_1.72.0.bb| 2 ++
3 files changed, 58 insertions(+)
create mode 100644
meta/recipes-sup
On 4/1/22 04:11, Richard Purdie wrote:
On Thu, 2022-03-31 at 15:21 -0700, Saul Wold wrote:
This ensure that when depmod-native runs we can find the correct
exclude.conf information, in this case adding .debug to ignore
the .debug kernell modules. The kmod utilities like depmod can use
either /
Also David's email seems incorrect?
Fehler bei der Nachrichtenzustellung an folgende Empfänger oder Gruppen:
David Niederpruem (david.niederpr...@elektrobit.com)
Die eingegebene E-Mail-Adresse konnte nicht gefunden werden.
Überprüfen Sie die E-Mail-Adresse des Empfängers, und versuchen Sie,
die
Please submit the patch upstream first.
Alex
On Fri 1. Apr 2022 at 16.46, Simone Weiss
wrote:
> Add a ptest for popt to core-image-ptest-all. Provide a patch to popt to
> adopt the test format to "simple test" and a script for running the test.
> All tests passed on a trial run.
>
> Signed-off-
Add a ptest for popt to core-image-ptest-all. Provide a patch to popt to
adopt the test format to "simple test" and a script for running the test.
All tests passed on a trial run.
Signed-off-by: Simone Weiss
Signed-off-by: David Niederpruem
---
.../distro/include/ptest-packagelists.inc | 1
This fixes a regression when glib-2.0 was used with clang.
Signed-off-by: Khem Raj
---
...s-for-typechecking-with-atomic-compa.patch | 64 +
...variant-of-g_atomic_int_compare_and_.patch | 70 +++
meta/recipes-core/glib-2.0/glib-2.0_2.72.0.bb | 2 +
3 files chang
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
Recipe upgrade statistics:
* Succeeded: 27
expat, 2.4.8, Yi Zhao
createrepo-c, 0.20.0, Alexander Kanavin
dpkg, 1.21.7, Aníbal Limón
python3-dtschema, 2022.3.2, Bruce Ashfield
python3-hypothesis, 6.40.1, Tim Orling
python3-mako, 1.2.0, Oleksa
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*445711587d461539a4d8f9d35a7fe996a86d3c8d* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe piglit failed.
NOTE: Starting bit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*f37bb1ea48d2782e997085aedf440b4a159e8189* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86 bitbake vulkan-samples' failed
Loading cache...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *epiphany* to *42.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-epiphany-upgrade-41.3-42.0.patch
- c
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: R
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libx11* to *1.7.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libx11-upgrade-1.7.3.1-1.7.4.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-helloworld* to
*ad95e7f791d8e1e7e7ec7f7cedfc2f6b29f6c9e2* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade go-helloworld -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxvmc* to *1.0.13* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxvmc -V 1.0.13
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gdk-pixbuf* to *2.42.8* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-gdk-pixbuf-upgrade-2.42.6-2.42.8.pat
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsndfile1* to *1.1.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libsndfile1 -V 1.1.0
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *procps* to *4.0.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe procps failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acpica* to *20220331* has
Succeeded.
Next steps:
- apply the patch: git am 0001-acpica-upgrade-20211217-20220331.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *webkitgtk* to *2.36.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe webkitgtk failed.
NOTE: Starting bitbake server...
NOTE: Reconne
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libhandy* to *1.6.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libhandy-upgrade-1.5.0-1.6.1.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *librsvg* to *2.54.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-librsvg-upgrade-2.52.7-2.54.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-tools* to *2.13.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lttng-tools-upgrade-2.13.4-2.13.6.patch
- check the changes to upstream patches and summar
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tzdata* to *2022a* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2021e-2022a.patch
- ch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ghostscript* to *9.56.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ghostscript-upgrade-9.55.0-9.56.0.patch
- check the changes to upstream patches and summar
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-typing-extensions* to
*4.1.1* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-python3-typing-extens
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mc* to *4.8.28* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-mc-upgrade-4.8.27-4.8.28.patch
- check t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.40.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.39.5-6.40.1.patch
- check the changes to upstream pat
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pip* to *22.0.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pip-upgrade-22.0.3-22.0.4.patch
- check the changes to upstream patches and summar
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to
*2022.3.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-dtschema-upgrade-2022.1-2022.3.2.patch
- check the changes to upstream pat
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3* to *3.10.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-upgrade-3.10.3-3.10.4.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *0.62.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe meson failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*61.3.0* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3-setuptools failed.
NOTE: Starting bitbake serve
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-sphinx-rtd-theme* to
*1.0.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-sphinx-rtd-theme-upgrade-0.5.0-1.0.0.patch
- check the changes to ups
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-sphinx* to *4.5.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-sphinx-upgrade-4.4.0-4.5.0.patch
- check the changes to upstream patches and sum
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *squashfs-tools* to *4.5.1*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade squashfs-tools -V 4.5.1 -S
afdd63fc386919b4aa40d5
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-mako* to *1.2.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-mako-upgrade-1.1.6-1.2.0.patch
- check the changes to upstream patches and summari
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*c179db1b6f2ae484bfca1e9f8bae273e3319fa7d* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
c179
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.18* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *14.0.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade llvm -V 14.0.0 -S
329fda39c507e8740978d10458451dcdb21563be
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.23.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.22.3-3.23.0.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dpkg* to *1.21.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dpkg-upgrade-1.21.4-1.21.7.patch
- check the changes to upstream patches and summarize them in th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.18* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go-runtime failed.
NOTE: Starting bitbake server...
NOTE: Reconne
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux-libuuid* to *2.38*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-util-linux-libuuid-upgrade-2.3
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sysvinit* to *3.02* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-sysvinit-upgrade-3.01-3.02.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux* to *2.38* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-util-linux-upgrade-2.37.4-2.38.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *expat* to *2.4.8* has
Succeeded.
Next steps:
- apply the patch: git am 0001-expat-upgrade-2.4.7-2.4.8.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *zlib* to *1.2.12* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade zlib -V 1.2.12
NOTE: Starting bitbake server...
NOTE: Recon
The behaviour doesn't change because KERNEL_IMAGEDEST is defined as
'boot' in the same file (line 215).
Signed-off-by: Alessio Igor Bogani
---
meta/classes/kernel.bbclass | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classe
On Thu, 2022-03-31 at 15:21 -0700, Saul Wold wrote:
> This ensure that when depmod-native runs we can find the correct
> exclude.conf information, in this case adding .debug to ignore
> the .debug kernell modules. The kmod utilities like depmod can use
> either /etc/depmod.d or /lib/depmod.d. The k
On Fri, 2022-04-01 at 09:50 +0530, Sundeep KOKKONDA wrote:
> relocate_sdk.py was developed for little-endian architures and when tries
> to install SDK for big-endian machines errors like below will be shown.
>
> The changes made in the script to support big-endian architecture.
>
> Signed-off-by
Can you please explain why changing arm-eabi to arm fixes the issue
and provide the complete error?
We do build rust for arm machines on the autobuilder, and there is no
error like that occurring.
Alex
On Fri, 1 Apr 2022 at 08:02, Sundeep KOKKONDA
wrote:
>
> The build shows below error while bu
60 matches
Mail list logo
