On 15/07/2022 18:00:57+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 aut
The following changes since commit 4667abcc925ae0c430cccb480ec530506f6201ae:
dropbear: break dependency on base package for -dev package (2022-07-01
08:35:07 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://c
The following changes since commit af25fff399fa623b4fd6efbca21e01ea6b4d1fd7:
qemu: add PACKAGECONFIG for capstone (2022-07-12 04:08:20 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/opene
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
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 di
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
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
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 ex
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 th
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 dep
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
Sig
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.
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 exception
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 ne
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/
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
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 t
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 particu
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', 'u
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/c
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 o
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/case
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
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 bitba
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
x
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
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
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 b
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 th
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 di
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
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 bitba
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
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 t
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/
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
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...
NOT
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
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:
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...
NOT
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
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
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 bit
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: Reconnect
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 summari
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
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 distributio
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 upstr
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 upstrea
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: Rec
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 th
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 pat
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
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 pat
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 t
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
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
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
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.pat
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 cha
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 the
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
- che
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
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
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
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
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 d
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. Dis
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 ge
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/pyth
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
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 hav
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/r
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 in
This fixes reproducibility issues with multilibs were a different recipe
specific sysroot is used which was leaking into debug symbols in libraries.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/met
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.
Signed-off-by: Ross Burton
---
meta/recipes-multimedia/pulseaudio/pulse
Hello,
On 13/07/2022 10:28:03+0200, Luis Enriquez wrote:
> This allows choosing padding algorithm when building fitImage. It may be
> pkcs-1.5 or pss.
>
> Signed-off-by: LUIS ENRIQUEZ
> From: LUIS ENRIQUEZ
> ---
> meta/classes/kernel-fitimage.bbclass | 5 +
> 1 file changed, 5 insertions(
77 matches
Mail list logo
