Hi all,
This is the full report for yocto-3.1.13.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
new issue found
Bug 14669 - [QA 3.1.13 RC1] failure in ptest
:gstreamer1.0.gstreame
This patch backports the AArch32 support for Arm's Neoverse N2 CPU.
Upstream-Status: Backport
[https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d7e8411f6a333d4054894ad3b23f23415a525230]
Signed-off-by: pgowda
---
meta/recipes-devtools/gcc/gcc-10.2.inc| 1 +
.../0038-aarch64-neoverse-n2
On Mon, Dec 20, 2021 at 5:08 AM Martin Jansa wrote:
>
> Hi,
>
> I don't remember the details, but looks like not intended. I guess I was
> running with default SRC_URI which contains syslog.cfg and other optional
> fragments, can you please refresh it again with all .cfg files removed from
> SR
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc
On Mon, 2021-12-20 at 17:01 +, Paul Barker wrote:
> On 17/12/2021 15:36, Matt Madison wrote:
> > This patch series switches to using the OE_IMPORTS mechanism
> > for installing the crate fetcher. This simplifies the addition
> > and clears up issues with interactions between SRCPV and
> > the s
From: Paul Eggleton
If IMAGE_LINK_NAME is empty (supported everywhere else) then do not
create the symlink for the .qemuboot file.
Signed-off-by: Paul Eggleton
---
meta/classes/qemuboot.bbclass | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/classes/qemuboot.bbc
This patchset puts in the remaining pieces to allow disabling symlinks
and then renaming the real files to avoid having the version in their
names, for example:
IMAGE_LINK_NAME = ""
IMAGE_VERSION_SUFFIX = ""
IMAGE_NAME_SUFFIX = ""
INITRAMFS_LINK_NAME = ""
KERNEL_ARTIFACT_NAME = "${MACHINE}"
KERN
From: Paul Eggleton
Allow setting any of the *_LINK_NAME variables to empty string in order
to disable creating symlinks for kernel artifacts, as you can already
for filesystem images with IMAGE_LINK_NAME. Additionally, for the image
type named symlinks, add a KERNEL_IMAGETYPE_SYMLINK boolean var
From: Paul Eggleton
Allow .bin suffix to be removed (or changed) in the various artifact
filenames. Removing this extension is useful when trying to remove
symlinks and present only unversioned image files (especially for the
FIT image).
Signed-off-by: Paul Eggleton
---
meta/classes/kernel-art
Turn the explicitly enabled zlib support into an enabled by default
PACKAGECONFIG, and add Zstd support (disabled by default).
Signed-off-by: Ross Burton
---
meta/recipes-kernel/kmod/kmod_29.bb | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/kmod/k
There's no good reason to keep separate target and native recipes for
kmod, so merge them into a single kmod_29.bb which uses class extension.
The symlinks are not created differently for target vs native builds, as
the native sbindir is in PATH.
Signed-off-by: Ross Burton
---
meta/recipes-kern
Remove the change of ac_pwd from config.status as the build is
successful without it (it was added with no explanation in 152c973 when
ptest was enabled).
Signed-off-by: Ross Burton
---
meta/recipes-kernel/kmod/kmod_git.bb | 4
1 file changed, 4 deletions(-)
diff --git a/meta/recipes-kerne
The time and timeout tests are sensitive to system load, and as we run
these on build machines they fail randomly.
[ YOCTO #14371 ]
Signed-off-by: Ross Burton
---
.../gawk/gawk/test-time.patch | 22 ---
meta/recipes-extended/gawk/gawk_5.1.1.bb | 6 -
2
Major changes in 3.0.1:
* Fixed invalid handling of X509_verify_cert() internal errors in libssl
([CVE-2021-4044])
* Allow fetching an operation from the provider that owns an unexportable key
as a fallback if that is still allowed by the property query.
Drop patches which were backpo
The test suite makes incorrect assumptions about OpenSSL versions post-
3.0, so backport the fix for the test suite.
Signed-off-by: Ross Burton
---
...enSSL-version-check-for-3.0.1-GH-301.patch | 60 +++
.../recipes-devtools/python/python3_3.10.1.bb | 1 +
2 files changed, 61 in
On 17/12/2021 15:36, Matt Madison wrote:
This patch series switches to using the OE_IMPORTS mechanism
for installing the crate fetcher. This simplifies the addition
and clears up issues with interactions between SRCPV and
the shared-state fetching logic.
Matt Madison (4):
lib/crate.py: instal
On Fri, Dec 17, 2021 at 8:37 AM Alexander Kanavin
wrote:
>
> Should this be named oe.crate for consistency and avoiding potential clashes?
I retained the existing name for this change set. The same thought
had occurred to me, though.
-Matt
>
> Alex
>
> On Fri, 17 Dec 2021 at 18:37, Matt Madiso
The test suite makes incorrect assumptions about OpenSSL versions post-
3.0, so backport the fix for the test suite.
Signed-off-by: Ross Burton
---
...enSSL-version-check-for-3.0.1-GH-301.patch | 60 +++
.../recipes-devtools/python/python3_3.10.1.bb | 1 +
2 files changed, 61 in
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
272aedd4a305 Linux 5.10.87
8dd559d53b3b arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
65c578935bcc arm: extend pfn_valid to take into account freed memory map
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
57dcae4a8b93 Linux 5.15.10
dbcda209899a perf inject: Fix itrace space allowed for new attributes
5b4a8fbe4b0b fuse: make sure reclaim doesn't write the inode
18fc0ba9b10e stagi
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
e4f2aee6612e Linux 5.10.85
47301c06f602 Documentation/Kbuild: Remove references to gcc-plugin.sh
af5ba49cf705 MAINTAINERS: adjust GCC PLUGINS after gcc-plugin.sh removal
ad1342
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
43e577d7a2cb Linux 5.15.8
c2bd1add2c3e bpf: Add selftests to cover packet access corner cases
5475fcf0a1c4 clocksource/drivers/dw_apb_timer_of: Fix probe failure
ee6104661b46 m
From: Bruce Ashfield
Updating linux-yocto/5.15 to the latest korg -stable release that comprises
the following commits:
4e8c680af6d5 Linux 5.15.7
3ded93ae46ce ipmi: msghandler: Make symbol 'remove_work_wq' static
888fc81107ca serial: liteuart: fix minor-number leak on probe errors
602824cf9aa9 s
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
a0582e24d371 Linux 5.10.84
e6edaf267793 ipmi: msghandler: Make symbol 'remove_work_wq' static
a8d18fb4d11b net/tls: Fix authentication failure in CCM mode
dbe73dace94c parisc:
From: Bruce Ashfield
Richard,
Here's the latest set of -stable updates that I've been testing
over the past couple of weeks. I avoided sending these due to the
project milestone .. but don't want to hold onto them until
January.
Speaking of January, you'll notice that there are no 5.14 updates.
On Mon, Dec 20, 2021 at 5:12 AM wrote:
>
> From: Bruce Ashfield
>
> Steve,
>
> I thought I had sent some of these before, but I didn't notice them
> in any of the recent dunfell updates.
>
> Here are the tested -stable updates that I've done (hence they aren't
> squashed, since each set of SRCREV
On Mon, 2021-12-20 at 23:03 +0800, wangmy wrote:
> License-Update: directory of copyright file changed.
> refresh fix_cflags_handling.patch
>
> Changelog:
> ===
> Limit the maximum amount of rbytes to 64 bytes (512 bits) for
> yescrypt,
> gost-yescrypt, and scrypt. Also reflect this limit
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
e8ef940326ef Linux 5.4.167
c97579584fa8 arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
6026d4032dbb arm: extend pfn_valid to take into account freed memory map
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
7f70428f0109 Linux 5.4.165
3a99b4baff3c bpf: Add selftests to cover packet access corner cases
b8a2c49aa956 misc: fastrpc: fix improper packet size calculation
8f9a25e452f8 irqc
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
57899c4e26bf Linux 5.4.163
6c728efe164f tty: hvc: replace BUG_ON() with negative return value
c3024e1945fe xen/netfront: don't trust the backend response data blindly
828b1d3861
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
9334f48f5673 Linux 5.4.162
46a8e16fcf2c ALSA: hda: hdac_stream: fix potential locking issue in
snd_hdac_stream_assign()
293385739d68 ALSA: hda: hdac_ext_stream: fix potential l
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
5915b0ea6746 Linux 5.4.159
abc49cc45d0a rsi: fix control-message timeout
64e6632ab4c1 media: staging/intel-ipu3: css: Fix wrong size comparison
imgu_css_fw_init
From: Bruce Ashfield
Steve,
I thought I had sent some of these before, but I didn't notice them
in any of the recent dunfell updates.
Here are the tested -stable updates that I've done (hence they aren't
squashed, since each set of SRCREVs are a useful test/debug point).
Cheers,
Bruce
The f
refresh pidof-add-m-option.patch
Changelog:
==
* Default to showing processes in the uninterruptable state (D).
The -z flag no longer affects whether processes in D state are shown.
The -z flag does still toggle whether zombie (Z) processes are shown.
* Removed unnecessary check w
Signed-off-by: Wang Mingyu
---
...ib-metadata_4.8.2.bb => python3-importlib-metadata_4.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-importlib-metadata_4.8.2.bb =>
python3-importlib-metadata_4.9.0.bb} (88%)
diff --git a/meta/recipes-
Until now the CVE checker was giving information about CVEs found for
a product (or more products) contained in a recipe. However, there was
no easy way to find out which products or recipes have no CVEs. Having
no reported CVEs might mean there are simply none, but can also mean
a product name (CP
License-Update: directory of copyright file changed.
refresh fix_cflags_handling.patch
Changelog:
===
Limit the maximum amount of rbytes to 64 bytes (512 bits) for yescrypt,
gost-yescrypt, and scrypt. Also reflect this limit in the documentation
(issue #145).
Signed-off-by: Wang Mingyu
-
License-Update: version of license file updated.
Signed-off-by: Wang Mingyu
---
...{linux-firmware_20211027.bb => linux-firmware_20211216.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20211027.bb =>
linux-firmware_202112
The append/override ordering was meaning that whilst the data was being picked
up later in the package processing, it wasn't being picked up by do_package.
This means changes to qemu options were not causing task signatures to change.
Fix the variable ordering with the append to correct this.
The
The gnu sources server has been known to disappear. Use the YP sources
mirror instead. If that breaks, the autobuilder is broken anyway. This
should reduce test failures from upstream network issues.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/bbtests.py | 2 +-
1 file changed
On Mon, 2021-12-20 at 05:40 -0800, Matt Madison wrote:
> On Sun, Dec 19, 2021 at 3:36 PM Richard Purdie
> wrote:
> >
> > On Wed, 2021-12-15 at 12:16 -0800, Matt Madison wrote:
> > > which is introducing task hash changes for some
> > > allarch package builds, and should no longer
> > > be needed
On Sun, Dec 19, 2021 at 3:36 PM Richard Purdie
wrote:
>
> On Wed, 2021-12-15 at 12:16 -0800, Matt Madison wrote:
> > which is introducing task hash changes for some
> > allarch package builds, and should no longer
> > be needed with recent versions of qemu.
> >
> > Signed-off-by: Matt Madison
> >
Hi,
I don't remember the details, but looks like not intended. I guess I was
running with default SRC_URI which contains syslog.cfg and other optional
fragments, can you please refresh it again with all .cfg files removed from
SRC_URI?
Regards,
On Thu, Dec 16, 2021 at 6:26 PM Jan Lübbe wrote:
On Sun, 2021-12-19 at 12:16 +, Oleksiy Obitotskyy via lists.openembedded.org
wrote:
> Hi All,
>
> I'm working with gatesgarth and after 'bitbake core-image-minimal -c
> populate_sdk' into .../deploy/sdk
> contains image installer .sh and manifests *.{host/target}.manifest. Host one
> contain
On Wed, 2021-12-15 at 11:11 +, Ross Burton wrote:
> Major changes in 3.0.1:
>
> * Fixed invalid handling of X509_verify_cert() internal errors in libssl
> ([CVE-2021-4044])
> * Allow fetching an operation from the provider that owns an unexportable
> key
> as a fallback if that is
I still want to question the need for this. I’d rather allow only an
explicit list giving an explicit order in the recipe.
Alex
On Mon 20. Dec 2021 at 13.15, Max Krummenacher wrote:
> The current developer manual [1] specifies that patches that are
> part of a directory which is given in SRC_UR
This adds a test which tests the do_patch task.
Execute it with:
oe-selftest -r bbtests.BitbakeTests.test_patching
Signed-off-by: Max Krummenacher
---
.../patchtest/patchtest/0001-10.patch | 25 +
.../patchtest/patchtest/0001-111.patch| 25 +
.../patchtes
The current developer manual specifies that patches that are
part of a directory which is given in SRC_URI are applied by
the do_patch task. However that is not implemented in the
current code.
Implement part of it with two differences:
- The implementation requires the parameter "apply=yes" and
The current developer manual [1] specifies that patches that are
part of a directory which is given in SRC_URI are applied by
the do_patch task. However that is not implemented in the
current code.
This patchset implements that, but deviates from what is
documented. If the patches are applied I wi
This includes just a busybox upgrade to address some security issues.
Tested on autobuilder and no issues found.
Thanks,
Anuj
The following changes since commit f6791df317e66b2d3fa88d3a038d888d4512305a:
libpcre/libpcre2: correct SRC_URI (2021-12-10 12:45:13 +0800)
are available in the Git r
Bug fix release. 1.33.2 has fixes for hush and ash (parsing fixes) and
unlzma (fix a case where we could read before beginning of buffer).
Signed-off-by: Anuj Mittal
---
.../{busybox-inittab_1.33.0.bb => busybox-inittab_1.33.2.bb}| 0
.../busybox/{busybox_1.33.1.bb => busybox_1.33.2.bb}
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b3aa80b45c4f46029efeb204bb9f2d2c4278a0e5]
Signed-off-by: pgowda
---
.../binutils/binutils-2.37.inc|1 +
.../binutils/0001-CVE-2021-42574.patch| 1998 +
2 files change
No, as upstream explained, in this case the null indicates invalid internal
state, so the correct behavior for the program is indeed to halt the
program execution and for you it is to find out how the invalid internal
state occurs in the first place through debugging or similar.
Alex
Alex
On Mon
Steve,
Earlier we have also thought the same things from the upstream issue comment
and we have tried another workaround mentioned on the ticket which is disabled
epoll.
We have tried it and it didn't work for the project. we still facing the issue.
Then we tried the NULL check for the variable
54 matches
Mail list logo
