This fixes build issues seen on mips, but problem is generic
Signed-off-by: Khem Raj
---
.../webkitgtk/add_missing_include.patch | 19 +++
meta/recipes-sato/webkit/webkitgtk_2.36.0.bb | 1 +
2 files changed, 20 insertions(+)
create mode 100644 meta/recipes-sato/webkit/we
The BB variable can't be referenced directly in a python function,
this misusage of the variable reference causes strip function to be
always skipped.
Fixed: b9c3db4953e4 ("kernel.bbclass: Use KERNEL_IMAGEDEST instead of hardcoded
boot path")
Signed-off-by: Kevin Hao
---
meta/classes/kernel.bbc
it fails to build on mips
https://errors.yoctoproject.org/Errors/Details/654398/
On Thu, Apr 7, 2022 at 10:00 AM Alexander Kanavin
wrote:
>
> Drop patches:
> 0001-Fix-racy-parallel-build-of-WebKit2-4.0.gir.patch
> 0001-When-building-introspection-files-add-CMAKE_C_FLAGS-.patch
> (both merged ups
zgrep applied to a crafted file name with two or more newlines
can no longer overwrite an arbitrary, attacker-selected file.
Upstream-Status: Backport
[https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=dc9740df61e575e8c3148b7bd3c147a81ea00c7c]
CVE: CVE-2022-1271
Signed-off-by: Ralph Siemsen
Malicious filenames can make xzgrep to write to arbitrary files
or (with a GNU sed extension) lead to arbitrary code execution.
Upstream-Status: Backport [https://tukaani.org/xz/xzgrep-ZDI-CAN-16587.patch]
CVE: CVE-2022-1271
Signed-off-by: Ralph Siemsen
---
.../xz/xz/CVE-2022-1271.patch
This includes a fix for CVE-2022-1271.
The existing "wrong path" patch needed to be refreshed, because the
context changed due to the following upstream change:
https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=31193bbd13cd2807d8ccaa2ba5b072303d5425e7
Signed-off-by: Ralph Siemsen
---
.../{g
Malicious filenames can make xzgrep to write to arbitrary files
or (with a GNU sed extension) lead to arbitrary code execution.
Upstream-Status: Backport [https://tukaani.org/xz/xzgrep-ZDI-CAN-16587.patch]
CVE: CVE-2022-1271
Signed-off-by: Ralph Siemsen
---
.../xz/xz/CVE-2022-1271.patch
Signed-off-by: Jon Mason
---
meta-poky/conf/distro/poky-tiny.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-poky/conf/distro/poky-tiny.conf
b/meta-poky/conf/distro/poky-tiny.conf
index 499af906a898..9a3106879021 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/con
also had this issue and found out, that the bluetooth service did come
up, once bluetooth was enabled
My fix was to edit like this
ReadWritePaths=:/var/lib/bluetooth
The colon ensures that the service won't fail if the directory doesn't exist
Am 08.04.22 um 13:01 schrieb Yi Zhao:
On 4/8/22
Hello,
On 06/04/2022 15:53:24+0200, Simone Weiss wrote:
> Add a ptest for libgpg-error to core-image-ptest-all. All tests passed on a
> trial run.
>
It seems the tests are failing on the autobuilders:
{'libgpg-error': '2022-04-08T16:22\n'
'2022-04-08T16:22\n'
'
On 4/8/22 12:55 PM, Jon Mason wrote:
On Fri, Apr 8, 2022 at 3:40 PM Khem Raj wrote:
On 4/8/22 12:25 PM, Jon Mason wrote:
Signed-off-by: Jon Mason
---
meta-poky/conf/distro/poky-tiny.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-poky/conf/distro/poky-tiny.conf
b/meta
Hello Brenda,
It seems this fails in some builds:
ERROR: lib32-qemu-6.2.0-r0 do_package: Didn't find service unit
'lib32-qemu-guest-agent.service', specified in
SYSTEMD_SERVICE:lib32-qemu-guest-agent.
Full log here:
https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/2850/steps
On Fri, Apr 8, 2022 at 3:40 PM Khem Raj wrote:
>
>
>
> On 4/8/22 12:25 PM, Jon Mason wrote:
> > Signed-off-by: Jon Mason
> > ---
> > meta-poky/conf/distro/poky-tiny.conf | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/meta-poky/conf/distro/poky-tiny.conf
> > b/meta-poky/conf/di
On 4/8/22 12:53 PM, Jon Mason wrote:
On Fri, Apr 8, 2022 at 3:38 PM Khem Raj wrote:
On 4/8/22 12:25 PM, Jon Mason wrote:
Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
entries, as it should be generic now.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/l
On Fri, Apr 8, 2022 at 3:38 PM Khem Raj wrote:
>
>
>
> On 4/8/22 12:25 PM, Jon Mason wrote:
> > Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
> > entries, as it should be generic now.
> >
> > Signed-off-by: Jon Mason
> > ---
> > meta/recipes-kernel/linux/linux-yocto-tiny_
On 4/8/22 12:25 PM, Jon Mason wrote:
Signed-off-by: Jon Mason
---
meta-poky/conf/distro/poky-tiny.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-poky/conf/distro/poky-tiny.conf
b/meta-poky/conf/distro/poky-tiny.conf
index 499af906a898..91c596faf182 100644
--- a/meta-poky/con
On 4/8/22 12:25 PM, Jon Mason wrote:
Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
entries, as it should be generic now.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --g
Use the Arm Versatile 926 kernel configs and round out all of the virtio
interfaces to match other QEMU machines.
Signed-off-by: Jon Mason
---
meta/conf/machine/qemuarmv5.conf | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/meta/conf/machine/qemuarmv5.conf b/met
Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
entries, as it should be generic now.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-
Signed-off-by: Jon Mason
---
meta-poky/conf/distro/poky-tiny.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-poky/conf/distro/poky-tiny.conf
b/meta-poky/conf/distro/poky-tiny.conf
index 499af906a898..91c596faf182 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/con
The virtio PCI devices seemed to be required for this machine for some
versions of qemu (based on errors from running qemu saying that the
devices don't exist). Changes to the entries here is all that is needed
to get it working.
Signed-off-by: Jon Mason
---
meta/conf/machine/qemuarm64.conf | 8
Changes in v2:
* Addressed Khem's comments
* Rebased to the latest version
* Added distro description for poky-tiny, as this makes it more obvious
which distro is being booted when there are multiple
The yocto-kernel-cache changes were sent, accepted, and should be
uploaded shortly.
Thanks,
Jon
For uniformity, use the virtio device interface, as all the other virtio
devices for this machine are the non-PCI ones.
Signed-off-by: Jon Mason
---
meta/conf/machine/qemuarm.conf | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/mac
The line in question is already in place in qemuarm.conf. Remove it
from here, as it is not necessary and references an older kernel.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 3 ---
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 3 ---
2 files changed, 6 del
The leaking test case has been fixed upstream, so backport the patch.
Signed-off-by: Ross Burton
---
.../fix-leak-metric.patch | 36 +++
.../skip-leaky-test.patch | 19 --
.../python/python3-cryptography_36.0.2.bb | 2 +-
3 fil
On 4/8/22 18:51, Stefan Herbrechtsmeier wrote:
Am 08.04.2022 um 11:23 schrieb Yi Zhao:
On 4/8/22 16:34, Stefan Herbrechtsmeier wrote:
Am 08.04.2022 um 10:15 schrieb Yi Zhao via lists.openembedded.org:
There is a bluetooth service startup failure:
bluetooth.service: Failed at step NAMESPACE s
Am 08.04.2022 um 11:23 schrieb Yi Zhao:
On 4/8/22 16:34, Stefan Herbrechtsmeier wrote:
Am 08.04.2022 um 10:15 schrieb Yi Zhao via lists.openembedded.org:
There is a bluetooth service startup failure:
bluetooth.service: Failed at step NAMESPACE spawning
/usr/libexec/bluetooth/bluetoothd: No su
On 4/8/22 16:34, Stefan Herbrechtsmeier wrote:
Am 08.04.2022 um 10:15 schrieb Yi Zhao via lists.openembedded.org:
There is a bluetooth service startup failure:
bluetooth.service: Failed at step NAMESPACE spawning
/usr/libexec/bluetooth/bluetoothd: No such file or directory
bluetooth.service: F
Am 08.04.2022 um 10:15 schrieb Yi Zhao via lists.openembedded.org:
There is a bluetooth service startup failure:
bluetooth.service: Failed at step NAMESPACE spawning
/usr/libexec/bluetooth/bluetoothd: No such file or directory
bluetooth.service: Failed to set up mount namespacing:
/run/systemd/
There is a bluetooth service startup failure:
bluetooth.service: Failed at step NAMESPACE spawning
/usr/libexec/bluetooth/bluetoothd: No such file or directory
bluetooth.service: Failed to set up mount namespacing:
/run/systemd/unit-root/var/lib/bluetooth: No such file or directory
This is becau
On Fri, 8 Apr 2022 at 09:03, Richard Purdie
wrote:
> There is something not quite right with one of the llvm changes:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5022
> https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/5043/steps/32/logs/stdio
This bit:
+
On Thu, 2022-04-07 at 19:00 +0200, Alexander Kanavin wrote:
> llvm-config no longer links with libLLVM, so there is no need
> to install it in -native (and it isn't built in the first place).
> This also significantly speeds up llvm-native build.
>
> Signed-off-by: Alexander Kanavin
> ---
> meta
32 matches
Mail list logo
