This includes multiple CVE fixes.
The license change is due to changes in maintainership, the license
itself is unchanged.
Signed-off-by: Richard Purdie
---
meta/recipes-support/vim/vim.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Needed for additional tests e.g. autopoint-1 which are otherwise skipped
Make locale-base-de-de and locale-base-fr-fw rdep unconditional as
musl-locales do provide these locales
Signed-off-by: Khem Raj
---
meta/recipes-core/gettext/gettext_0.22.bb | 4 +---
1 file changed, 1 insertion(+), 3
When SPDX manifests are enabled for OE-Core, it hightlights that the SDK_NAME
default isn't working well. Add IMAGE_BASENAME to it to help avoid conflicts
between outut files.
I suspect the defaults aren't working well and most distros are already
overriding this.
Signed-off-by: Richard Purdie
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/rust/cargo-c-native_0.9.18.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/rust/cargo-c-native_0.9.18.bb
b/meta/recipes-devtools/rust/cargo-c-native_0.9.18.bb
index 4f34f50ca90..44423b7aa87 100644
---
We can probably output the logs from run-ptest as upstream suggested?
That'd avoid having to carry a rejected patch, even if it can be
removed (maybe) after the issue is fixed.
Alex
On Mon, 11 Sept 2023 at 15:40, Mikko Rapeli wrote:
>
> Log the input and output banner files. Output seems to
>
On Thu, 7 Sept 2023 at 14:04, Richard Purdie
wrote:
> See meta/conf/distro/include/no-static-libs.inc which does things like:
>
> meta/conf/distro/include/no-static-libs.inc:DISABLE_STATIC:pn-openssl-native
> = ""
> meta/conf/distro/include/no-static-libs.inc:DISABLE_STATIC:pn-nativesdk-openssl
Log the input and output banner files. Output seems to
contain more lines than input which fails the test but
it's not clear what is in there from the ssh command
stderr. So print them out to dig deeper into the root
cause.
Upstream rejected previous logging patch so they will likely
do the same
Upstream rejected the change:
https://github.com/openssh/openssh-portable/pull/437
Signed-off-by: Mikko Rapeli
---
...0001-openssh-regress-Makefile-print-logs-if-test-fails.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Andrian
Many thanks for the documentation patch!
Copying the docs@ mailing list...
On 10.09.23 at 17:52, Adrian Freihofer wrote:
Signed-off-by: Adrian Freihofer
---
documentation/sdk-manual/extensible.rst | 97 -
1 file changed, 96 insertions(+), 1 deletion(-)
From: Ross Burton
The modesetting driver works well in qemu, so install it by default. The
plain framebuffer has been buggy in recent 6.4 kernels, a sign that it's
not getting much testing. The Xorg modesetting driver that can use more
powerful virtualised hardware is much better.
We override
From: Ross Burton
On modern systems, both real and virtual hardware, the modesetting
driver is preferred over the dumb framebuffer driver as it is more
functional and is essentially the default Xorg video driver.
Signed-off-by: Ross Burton
---
From: Ross Burton
The default XSERVER value is good enough for this BSP, so we don't need
to set it explicitly.
Signed-off-by: Ross Burton
---
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 3 ---
1 file changed, 3 deletions(-)
diff --git
The following changes since commit 03d37854b1dacbecd2c522821c59ef01d9bd305c:
build-appliance-image: Update to master head revision (2023-09-10 09:03:42
+0100)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib rbt/crypt
Fixed:
IMAGE_INSTALL:append = " libxcrypt-compat"
$ bitbake -cpopulate_sdk
file /usr/lib/libcrypt.so from install of
libxcrypt-compat-dev-4.4.33-r0.0.aarch64 conflicts with file from package
libcrypt-dev-4.4.33-r0.2.aarch64
Remove libcrypt.so like other files to fix the error.
Signed-off-by:
On 10 Sep 2023, at 16:54, Marta Rybczynska via lists.yoctoproject.org
wrote:
> On Sun, 10 Sept 2023, 17:14 Khem Raj, wrote:
> On Sun, Sep 10, 2023 at 4:18 AM Steve Sakoman wrote:
> >
> > Branch: master
> >
> > New this week: 10 CVEs
> > CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5
> >
From: Siddharth Doshi
Note: The Fix needs to be pushed in gdb rather than bintuils-gdb as we are
disabling gdb in binutils configure.
Upstream-Status: Backport from
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=033bc52bb6190393c8eed80925fa78cc35b40c6d]
CVE: CVE-2023-39128
opps. Please ignore this.
Sent by mistake. Apologies for the error.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187481):
https://lists.openembedded.org/g/openembedded-core/message/187481
Mute This Topic:
From: Changqing Li
Fix an issue with early log messages being lost when running in systemd.
Signed-off-by: Changqing Li
Signed-off-by: Steve Sakoman
---
...KillMode-process-is-not-recommended-.patch | 33
...-messages-lost-when-running-in-syste.patch | 75 +++
From: Siddharth Doshi
Note: The Fix needs to be pushed in gdb rather than bintuils-gdb as we are
disabling gdb in binutils configure.
Upstream-Status: Backport from
[https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=033bc52bb6190393c8eed80925fa78cc35b40c6d]
CVE: CVE-2023-39128
Hi Sanjana,
Thank-you for this patch.
But, i feel this is not the right way to patch this vulnerability. No doubts
the patch is released for binutils-gdb, but that is because the sources are
merged.
However, in our systems, the command gdb comes from gdb package and not from
bintuils-gdb.
I guess i missed the patch status. Apologies for that.
Thank-you for updating me on the status.
Regards,
Siddharth
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187477):
https://lists.openembedded.org/g/openembedded-core/message/187477
Mute
From: Vijay Anusuri
A DMA-MMIO reentrancy problem may lead to memory corruption bugs
like stack overflow or use-after-free.
Summary of the problem from Peter Maydell:
https://lore.kernel.org/qemu-devel/cafeaca_23vc7he3iam-jva6w38lk4hjowae5kcknhprd5fp...@mail.gmail.com
Reference:
22 matches
Mail list logo
