Hi All,
QA for yocto- 3.1.20.rc2 is completed. This is the full report for this
release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jing Hui
>
On Thu, Oct 13, 2022 at 2:21 PM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Khem Raj
> > Sent: den 13 oktober 2022 17:41
> > To: Peter Kjellerstedt
> > Cc: Ross Burton ; Patches and discussions about the
> > oe-core layer
> > Subject: Re: [OE-core] [PATCH] gcc: Allow
> -Original Message-
> From: Khem Raj
> Sent: den 13 oktober 2022 17:41
> To: Peter Kjellerstedt
> Cc: Ross Burton ; Patches and discussions about the
> oe-core layer
> Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-
> directories to take effect
>
> On Thu, Oct 13,
Test that the shared recipes in original mode with diff enabled works in
multiconfig,
otherwise it will not build when using the same TMP dir.
The test can be run with:
oe-selftest -r
archiver.Archiver.test_archiver_multiconfig_shared_unpack_and_patch
| oe-selftest - INFO -
STAGING_KERNEL_DIR uses the MACHINE name so it breaks the multiconfig
and in this cases it will run the shared recipes twice, one for each
machine.
STAGING_KERNEL_DIR it's been introduced in commit 5487dee2e1
Signed-off-by: Jose Quaresma
---
meta/classes/archiver.bbclass | 2 +-
1 file
From: Sergei Zhmylev
In case user requested to build a binary repeatable package,
it's required to honor the SOURCE_DATE_EPOCH environment
variable. So forcefully set mtime inside all the routines
which modify fstab in case it is updated.
Signed-off-by: Sergei Zhmylev
---
From: Richard Purdie
Avoid accidentally linking to the rdma library from the host by
adding a PACKAGECONFIG for the option. This was found on new
Fedora 36 autobuilder workers.
Signed-off-by: Richard Purdie
(cherry picked from commit 2a0f3cb225e4d5471155abbcd05d09bd6bf1620f)
Signed-off-by:
Avoid accidentally linking to the rbd library from the host by
adding a PACKAGECONFIG for the option.
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
Avoid accidentally linking to the vde library from the host by
adding a PACKAGECONFIG for the option.
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
(cherry picked from commit 8839e9540528b0b46c4fb4f95e508f038bcef8b9)
Signed-off-by: Steve Sakoman
---
From: John Edward Broadbent
Git has removed support for "git submodule--helper list".
https://github.com/git/git/commit/31955475d1c283120d5d84247eb3fd55d9f5fdd9
This change provides an alternate method for gathering the submodules
information.
Tested:
Build recipes with and without submodules
From: Michael Halstead
Update uninative to work with the new glibc 2.36 version
Signed-off-by: Michael Halstead
Signed-off-by: Richard Purdie
(cherry picked from commit 410226b053e14e32add1f9b4b811f84a1c445a7c)
Signed-off-by: Steve Sakoman
---
meta/conf/distro/include/yocto-uninative.inc |
This test will fail any time the host has libdrm > 2.4.107
Signed-off-by: Steve Sakoman
---
meta/lib/oeqa/selftest/cases/runtime_test.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index
From: Tim Orling
Security and bug fixes.
* Drop CVE-2021-28861.patch as it was merged in 3.8.14 release.
Fixes:
* CVE-2020-10735
https://nvd.nist.gov/vuln/detail/CVE-2020-10735
* CVE-2021-28861
https://nvd.nist.gov/vuln/detail/CVE-2021-28861
* CVE-2018-25032
From: Hitendra Prajapati
Source: https://downloads.isc.org/isc/dhcp
MR: 122797, 122812
Type: Security Fix
Disposition: Backport from https://downloads.isc.org/isc/dhcp/4.4.3-P1/patches/
ChangeID: 31490133cae8fc9c77073f9023955d3ff39c0b6e
Description:
Fixed CVEs:
1. CVE-2022-2928
From: Hitendra Prajapati
Source: https://git.qemu.org/?p=qemu.git
MR: 117886
Type: Security Fix
Disposition: Backport from
https://git.qemu.org/?p=qemu.git;a=commit;h=b9d383ab797f54ae5fa8746117770709921dc529
&&
Please review this set of patches for dunfell and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4330
The following changes since commit dbad46a0079843b380cf3dda6008b12ab9526688:
build-appliance-image:
On Thu, Oct 13, 2022 at 7:38 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Ross Burton
> > Sent: den 13 oktober 2022 16:05
> > To: Peter Kjellerstedt
> > Cc: Patches and discussions about the oe-core layer > c...@lists.openembedded.org>
> > Subject: Re: [OE-core]
> -Original Message-
> From: Ross Burton
> Sent: den 13 oktober 2022 16:05
> To: Peter Kjellerstedt
> Cc: Patches and discussions about the oe-core layer c...@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH] gcc: Allow -Wno-error=poison-system-
> directories to take effect
>
>
Whilst this is a good fix, I’m horrified to ask why you need it…
Ross
> On 13 Oct 2022, at 14:29, Peter Kjellerstedt via lists.openembedded.org
> wrote:
>
> The change in commit e903b29f (gcc-cross: pass
> -Werror=poison-system-directories to compiler stages) made it impossible
> to disable
On Thu, Oct 13, 2022 at 2:59 AM Marta Rybczynska
wrote:
> $ bitbake weston
> Loading cache: 100%
>
> |###|
> Time: 0:00:00
> Loaded 1640 entries from dependency cache.
The change in commit e903b29f (gcc-cross: pass
-Werror=poison-system-directories to compiler stages) made it impossible
to disable the error using -Wno-error=poison-system-directories.
Signed-off-by: Peter Kjellerstedt
---
.../0002-gcc-poison-system-directories.patch | 36 +--
On Thu, Oct 13, 2022 at 9:13 AM Alexandre Belloni
wrote:
>
> Hello,
>
> On 12/10/2022 08:17:14+0100, Alex Kiernan wrote:
> > Release notes:
> > https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html
> >
>
> This causes the following failure:
>
Hi Ross,
I did that.
current behavior:
$ devtool modify busybox
Initialising tasks: 100% |###|
Time: 0:00:00
Sstate summary: Wanted 14 Local 0 Mirrors 0 Missed 14 Current 6 (0%
match, 30% complete)
NOTE: Executing Tasks
...
your new behavior:
@@ -52,7 +52,7
From: Sergei Zhmylev
When SOURCE_DATE_EPOCH variable is set, binary repeatable build
is expected. This commit implements reproducable disk identifiers
in such a case using its value as a Random seed.
Signed-off-by: Sergei Zhmylev
---
scripts/lib/wic/plugins/imager/direct.py | 5 -
1 file
On 12 Oct 2022, at 21:51, Khem Raj via lists.openembedded.org
wrote:
> As per https://wiki.yoctoproject.org/wiki/Weekly_Status, master is frozen for
> release and RP is on vacation, so patches are being review/accumulated but
> are not merging just yet.
>
> Can we publish the staging branch
> On 13 Oct 2022, at 09:23, Andrej Valek via lists.openembedded.org
> wrote:
> I had some time and made some more testing.
>
> Looks like, that the problematic commits are here:
> https://github.com/openembedded/openembedded-core/commit/41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1
>
I guess it’s not. I’ve been pushing to enable these in oe-core but we’re
not there yet. You get them enabled by default in poky.
Alex
On Thu 13. Oct 2022 at 11.59, Marta Rybczynska wrote:
> $ bitbake weston
> Loading cache: 100%
>
>
$ bitbake weston
Loading cache: 100%
|###|
Time: 0:00:00
Loaded 1640 entries from dependency cache.
ERROR: Nothing PROVIDES 'weston'
weston was skipped: missing required
Hello,
This seems to have caused the following failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/6301/steps/13/logs/stdio
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
Hi Pgowda,
Many thanks for your patches!
On 10/13/22 09:47, Pgowda wrote:
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
Cheers - try the new layer setup and config management tools too :-)
Alex
On Thu, 13 Oct 2022 at 10:44, Leon Woestenberg wrote:
>
> Hello Alexander,
>
> On Wed, Jun 22, 2022 at 12:33 PM Alexander Kanavin
> wrote:
> >
> > There's been a recent discussion about how we can make the Yocto SDK
> >
Hello Alexander,
On Wed, Jun 22, 2022 at 12:33 PM Alexander Kanavin
wrote:
>
> There's been a recent discussion about how we can make the Yocto SDK
> experience better [1]. One of the ideas was to eliminate the SDK
> as a separate artefact altogether and simply provide everything
> that the SDK
Signed-off-by: He Zhe
---
.../lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.8.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.13.4.bb =>
lttng-tools_2.13.8.bb} (98%)
diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.13.4.bb
Hello again,
I had some time and made some more testing.
Looks like, that the problematic commits are here:
https://github.com/openembedded/openembedded-core/commit/41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1
What happens when you run 'bitbake weston'?
Alex
On Thu, 13 Oct 2022 at 10:10, Marta Rybczynska wrote:
>
>
>
> On Thu, 13 Oct 2022, 17:00 Alexandre Belloni,
> wrote:
>>
>> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote:
>> > Hello all,
>> > I'm trying to build the core-image-weston in
Hello,
On 12/10/2022 08:17:14+0100, Alex Kiernan wrote:
> Release notes:
> https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html
>
This causes the following failure:
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/5901/steps/12/logs/stdio
ERROR: rust-1.64.0-r0 do_patch:
On Thu, 13 Oct 2022, 17:00 Alexandre Belloni,
wrote:
> On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote:
> > Hello all,
> > I'm trying to build the core-image-weston in kirkstone to look into
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926
> >
> > It turns out that the image does
On 13/10/2022 09:52:44+0200, Marta Rybczynska wrote:
> Hello all,
> I'm trying to build the core-image-weston in kirkstone to look into
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926
>
> It turns out that the image does not build (oe-core
> e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with
Hello all,
I'm trying to build the core-image-weston in kirkstone to look into
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14926
It turns out that the image does not build (oe-core
e728d0965d6fda8ac54e065ca7bf7eb9da9a8170 with bitbake
6603c3e39f1cf746669ec6c9f0be8c6e6ece426e). I'm getting:
From: pgowda
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport
[https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status:
This causes ptest failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/4115/steps/12/logs/stdio
'pango': ['pango/test-no-fonts.test']}
On 11/10/2022 16:05:57+0800, wangmy wrote:
> Signed-off-by: Wang Mingyu
> ---
> .../pango/{pango_1.50.10.bb => pango_1.50.11.bb}
On 12/10/2022 16:46:44+, Ross Burton wrote:
> We only have 1.50.9 in oe-core master, please ensure that you sent patches
> based on master, or if they’re based on another staging branch please make
> that clear.
>
this applied fine on master-next because we carry your 1.50.10 upgrade
>
42 matches
Mail list logo
