Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.05* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.17.04-0.17.05.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 *python3-hypothesis* to
*6.98.5* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.97.3-6.98.5.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-urllib3* to *2.2.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-urllib3-upgrade-2.1.0-2.2.0.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 *gstreamer1.0-libav* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-libav-upgrade-1.22.9-1.22.10.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lsof* to *4.99.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-lsof-upgrade-4.98.0-4.99.3.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust-llvm* to *1.76.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust-llvm failed.
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cargo* to *1.76.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe cargo failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ruby* to *3.3.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe ruby failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xz* to *5.4.6* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade xz -V 5.4.6
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-yamllint* to *1.34.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-yamllint-upgrade-1.33.0-1.34.0.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 *man-pages* to *6.06* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-man-pages-upgrade-6.05.01-6.06.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-trove-classifiers* to
*2024.1.31* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-trove-classifiers-upgrade-2024.1.8-2024.1.31.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-beartype* to *0.17.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-beartype-upgrade-0.17.0-0.17.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 *rust* to *1.76.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pip* to *24.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pip-upgrade-23.3.2-24.0.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography* to
*42.0.2* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3-cryptography failed.
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-lxml* to *5.1.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-lxml -V 5.1.0
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *liburi-perl* to *5.27* has
Succeeded.
Next steps:
- apply the patch: git am 0001-liburi-perl-upgrade-5.25-5.27.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-poetry-core* to
*1.9.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-poetry-core-upgrade-1.8.1-1.9.0.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdnf* to *0.73.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libdnf-upgrade-0.72.0-0.73.0.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 *pkgconf* to *2.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pkgconf-upgrade-2.1.0-2.1.1.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 *python3-certifi* to
*2024.2.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-certifi-upgrade-2023.11.17-2024.2.2.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to
*2023.11* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *librepo* to *1.17.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe librepo failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.22.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *1.3.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-1.3.1-1.3.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 *git* to *2.43.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-git-upgrade-2.43.0-2.43.2.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.22.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go-runtime failed.
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.9.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.9-4.9.1.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 *dpkg* to *1.22.4* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe dpkg failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *elfutils* to *0.190* has
Succeeded.
Next steps:
- apply the patch: git am 0001-elfutils-upgrade-0.189-0.190.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 *dnf* to *4.19.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dnf-upgrade-4.18.2-4.19.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 *ovmf* to *edk2-stable202311*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *zlib* to *1.3.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe zlib failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.7.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.5.3-6.7.1.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 *update-rc.d* to
*b8f950105010270a768aa12245d6abf166346015* has Succeeded.
Next steps:
- apply the patch: git am 0001-update-rc.d-upgrade-to-latest-revision.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *createrepo-c* to *1.0.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-createrepo-c-upgrade-1.0.3-1.0.4.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 *glib-2.0* to *2.78.4* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-glib-2.0-upgrade-2.78.3-2.78.4.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *255.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-systemd-boot-upgrade-255.1-255.3.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 *ofono* to *2.4* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-ofono-upgrade-2.3-2.4.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxml2* to *2.12.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxml2-upgrade-2.11.5-2.12.5.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ttyrun* to *2.31.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ttyrun-upgrade-2.30.0-2.31.0.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 *ell* to *0.62* has Succeeded.
Next steps:
- apply the patch: git am 0001-ell-upgrade-0.61-0.62.patch
- check the changes to upstream patches and summarize them in the commit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssh* to *9.6p1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-openssh-upgrade-9.5p1-9.6p1.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *efivar* to *39* has Succeeded.
Next steps:
- apply the patch: git am 0001-efivar-upgrade-38-39.patch
- check the changes to upstream patches and summarize them in the commit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.18.24* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bind-upgrade-9.18.21-9.18.24.patch
- check the changes to upstream patches and summarize them
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> These patches improve the VSCode support in devtool ide-sdk from
> Adrian Freihofer.
>
> I added a generic C++ configuration for the VScode
> extension while awaiting for autotools support.
>
> A refactoring is proposed for the
By default, the cpptools VSCode extension will use the host's headers
and flags for linting. This results in a lot of include errors and
misleading definitions. Even though this generic configuration doesn't
include all the depenendencies, it is a proper fallback for recipe
classes we do not
Among the files generated by meson is compile_commands.json. It is not
used by bitbake during the build. However, if the devtool workspace is
opened inside an IDE, that IDE can use compile_commands.json to
configure linting and code completion. This is notably relied on by the
new devtool ide-sdk
When debugging or browsing files, the user may fall into external
sources from other packages in the sysroot or dbg-rootfs. Modifying them
will only lead to confusion since they will be overwritten by Yocto. The
user should open them in a separate devtool modify session if they want
to make
The generated scripts use the sys.path configuration found inside
bitbake. It can be a different python version than the one used on the
host through the IDE.
For instance, when running the generated script
deploy_target_cmake-example-core2-64 from an eSDK generated on another
machine, I got the
These patches improve the VSCode support in devtool ide-sdk from
Adrian Freihofer.
I added a generic C++ configuration for the VScode
extension while awaiting for autotools support.
A refactoring is proposed for the meson class. Without absolute compiler
paths, the linter inside VSCode will not
An exception was raised because we did not have the topdir attribute
which was used in fallback mode (non cmake/meson recipes).
Already in the merge queue in Adrian's latest patches.
---
scripts/lib/devtool/ide_sdk.py | 1 +
1 file changed, 1 insertion(+)
diff --git
When launching the debug configuration, the source files from the debug
rootfs were openened in the editor instead of the local workspace files.
We add an exception to properly map them to the file being developed and
compiled by the IDE integration. This also more closely matches what the
user
Apply a patch proposed by Rich to fix the init crashes
Signed-off-by: Khem Raj
---
...akage-in-last-commit-uninitialized-p.patch | 41 +++
meta/recipes-core/musl/musl_git.bb| 1 +
2 files changed, 42 insertions(+)
create mode 100644
Do not use https protocol for fetching
Musl author confirms that https protocol is not well supported yet on
musl git host, currently we experience this problem intermittently on
some build hosts where the fetching fails.
fatal: protocol error: bad line length character: erro
WARNING: Failed to
On Thu, Feb 15 2024 at 11:25:24 AM +00:00:00, Ross Burton
wrote:
Mesa 24.0.0 is - as clearly indicated on the web site - a development
snapshot. 24.0.1 is now out, can you upgrade to that?
Thank you. I didn't see that mentioned in the gitlab tag. I sent the
mesa-24.0.1 update as a follow up
Signed-off-by: Markus Volk
---
.../mesa/{mesa-gl_24.0.0.bb => mesa-gl_24.0.1.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 2 +-
meta/recipes-graphics/mesa/{mesa_24.0.0.bb => mesa_24.0.1.bb} | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename
On 6 Dec 2023, at 16:06, Jonathan GUILLOT via lists.openembedded.org
wrote:
> +LOCALE_PATHS += "${datadir}/cups/templates”
This doesn’t quite do what you expect. Listing the packages generated by cups I
see:
cups-locale-da:
/usr/share/cups/templates/da/add-class.tmpl
From: Randy MacLeod
With the 3.22 upgrade 21 additional tests fail on qemuarm64.
Skip them until the problems are resolved. Tracked by:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15399
Signed-off-by: Randy MacLeod
---
.../valgrind/valgrind/remove-for-aarch64 | 27
From: "bar...@tkos.co.il"
Cc: Vyacheslav Yurkov
Signed-off-by: Baruch Siach
Signed-off-by: Richard Purdie
(cherry picked from commit aebd526cdfea738745e57183b1015fd327bd94df)
Signed-off-by: Steve Sakoman
---
meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb | 2 +-
1 file changed,
From: Chen Qi
The problem could be reproduced with the following settings:
MACHINE = "qemux86-64"
KERNEL_SPLIT_MODULES = "0"
require conf/multilib.conf
MULTILIBS ?= "multilib:lib32"
DEFAULTTUNE:virtclass-multilib-lib32 ?= "core2-32"
The error message is as below:
bb.data_smart.ExpansionError:
From: Jonathan GUILLOT
USB devices are auto-mounted in a directory named like theirs labels.
Special characters like whitespace are octal-escaped in /proc/mounts
output. Using directly this output file as an argument for umount failed
and the mount directory can't be removed as still busy.
Using
From: Richard Purdie
rpm 4.19 now builds with LFS64 support enabled by default,
so it calls statvfs64() to get the space available on the
filesystem it is installing packages into. This is not
getting caught by pseudo, so rpm is checking the host's
root filesystem, rather than the filesystem
From: Julien Stephan
do_populate_lic dependencies are defined inside license.bbclass such as:
addtask populate_lic after do_patch before do_build
but externalsrc deletes the do_patch task, so the only dependency left for
do_populate_lic is "before do_build"
On a devtool context, when doing
From: Richard Purdie
We occasionally see races over the lockfile used by externalsrc/devtool
when walking files for the source_date_epock calculation. Skip this file
if present to avoid the issues and fix a real issue where SDE could be
contaminated too.
[YOCTO #14921]
Signed-off-by: Richard
From: Richard Purdie
Most of the allarch code is conditional and only set if the recipe remains
marked
as allarch. The qemu wrapper handling is not handled in the same way however and
is unconditional.
Move the code to some slightly uglier inline python to allow it to be
conditional
and match
From: Wang Mingyu
Changelog:
https://gstreamer.freedesktop.org/releases/1.22
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 30b3835c367ff1de00d24cddf3bd920ea29f15c5)
Signed-off-by: Steve Sakoman
---
From: Wang Mingyu
Changelog:
==
* Fix operation of --no-absolute-filenames --make-directories
* Restore access and modification times of symlinks in copy-in
and copy-pass modes.
0001-configure-Include-needed-header-for-major-minor-macr.patch
revmoed since it's included in 2.15
From: Wang Mingyu
Changelog:
atk-adaptor: Fix critical when no table cell array is returned.
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 9bed9f07aea6c425748c8908641ce8a99fd5162f)
Signed-off-by: Steve Sakoman
---
From: Kai Kang
Update xserver-xorg from 21.1.9 to 21.1.11.
Release Notes of 21.1.11 [1]:
This release contains fixes for the issues reported in today's security
advisory: https://lists.x.org/archives/xorg/2024-January/061525.html
* CVE-2023-6816
* CVE-2024-0229
* CVE-2024-21885
*
From: Alexander Sverdlin
Signed-off-by: Alexander Sverdlin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 0caafdbbf4e7dc84b919afe14f7cb8c46a9e4ac2)
Signed-off-by: Steve Sakoman
---
...nux-firmware_20231030.bb => linux-firmware_20231211.bb} | 7
From: Ross Burton
Primarily list the number of patches found, useful when debugging.
Also clean up some bad escaping that caused warnings and use
re.IGNORECASE instead of manually doing case-insenstive rang matches.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from
From: Benjamin Bara
Pull in fixes for CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780.
Signed-off-by: Benjamin Bara
Signed-off-by: Steve Sakoman
---
meta/recipes-core/glibc/glibc-version.inc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Robert Joslyn
The CPE vendor is "gnome" and the CPE product is "gtk" for both gtk+3
and gtk4 recipes. Set CVE_PRODUCT so we properly match the NVD database.
Signed-off-by: Robert Joslyn
Signed-off-by: Richard Purdie
(cherry picked from commit 253f5f745d66acefcc739f1c9ad2dd46be630e47)
From: Simone Weiß
This is fixed via a patch added in gcc-13.2.inc already, but still
reported e.g. for libgcc as it is not defining an own source but use the
shared gcc-source.
Signed-off-by: Simone Weiß
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from
From: Ross Burton
Handle CVE_STATUS[...] being set to an empty string just as if it was
not set at all.
This is needed for evaluated CVE_STATUS values to work, i.e. when
setting not-applicable-config if a PACKAGECONFIG is disabled.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
From: Ross Burton
Backport the upstream fix for CVE-2023-48795.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from commit 314fa19c5e07fa632ff0434a6adbb97de1319a02)
Signed-off-by: Steve Sakoman
---
.../libssh2/libssh2/CVE-2023-48795.patch | 466
From: Yogita Urade
CVE-2023-52355:
An out-of-memory flaw was found in libtiff that could be
triggered by passing a crafted tiff file to the
TIFFRasterScanlineSize64() API. This flaw allows a remote
attacker to cause a denial of service via a crafted input
with a size smaller than 379 KB.
Issue
From: Peter Marko
This CVE is for iCPE cloudflare:zlib.
Alternative to ignoring would be to limit CVE_PRODUCT, but
historic CVEs already have two - gnu:zlib and zlib:zlib.
So limiting it could miss future CVEs.
Signed-off-by: Peter Marko
Signed-off-by: Richard Purdie
(cherry picked from
Please review this set of changes for nanbield and have comments back by
end of day Monday, February 19
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6568
The following changes since commit 0584d01f623e1f9b0fef4dfa95dd66de6cbfb7b3:
From: Yogita Urade
CVE-2023-6228:
An issue was found in the tiffcp utility distributed by the
libtiff package where a crafted TIFF file on processing may
cause a heap-based buffer overflow leads to an application
crash.
References:
https://nvd.nist.gov/vuln/detail/CVE-2023-6228
On Tue, Feb 13, 2024 at 6:33 PM wrote:
>
> From: BELOUARGA Mohamed
>
> This patch corrects the default value of SPDX_NAMESPACE_PREFIX as the previous
> value is not expected to exist.
> It adds also the documentation of the variable SPDX_NAMESPACE_PREFIX.
> This patch can also be linked to the
On Thu, 2024-02-15 at 16:06 +0100, Jan-Simon Möller wrote:
> Am Freitag, 9. Februar 2024, 15:17:13 CET schrieb Richard Purdie via
> lists.openembedded.org:
> > On Wed, 2024-02-07 at 13:21 +0530, akash hadke wrote:
> >
> > I think a few of us are torn on this. If it were accepted upstream, I'd
>
On Wed, 2024-01-31 at 13:39 +0100, Alexander Kanavin wrote:
> Existing conf-notes.txt is not adequate in situations where the user
> needs to select a config template from several, or get an overview of them and
> is interested only in a brief explanation of what the template is for,
> but not
On Thu, 2024-02-15 at 10:29 +, Sadineni, Harish via
lists.openembedded.org wrote:
>
> Hi all,
>
> We are analysing the test failures reported by the autobilder
> athttps://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/qemux86-64-tc/testresults.json
> The autobuilder result
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
On 15 Feb 2024, at 06:40, Mikko Rapeli wrote:
> optee xtests are triggering a reproducible RCU stall in our testing with
> --cpu max,pauth-impdef=on and qemu-system 8.2.1 from Debian unstable.
> This does not happen with --cpu cortex-a57 on this qemu-machine version.
>
[sigh]
Can you file a
Hi,
Any idea furhter, what could be the issue?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195513):
https://lists.openembedded.org/g/openembedded-core/message/195513
Mute This Topic: https://lists.openembedded.org/mt/98361235/21656
Group
On Thu, 15 Feb 2024 at 12:44, Richard Purdie
wrote:
> > Mesa 24.0.0 is - as clearly indicated on the web site - a development
> > snapshot. 24.0.1 is now out, can you upgrade to that?
>
> FWIW I did take this knowing that it was a development snapshot and
> they we'd be very likely to be able to
On Thu, 2024-02-15 at 11:25 +, Ross Burton wrote:
> Mesa 24.0.0 is - as clearly indicated on the web site - a development
> snapshot. 24.0.1 is now out, can you upgrade to that?
FWIW I did take this knowing that it was a development snapshot and
they we'd be very likely to be able to update
Mesa 24.0.0 is - as clearly indicated on the web site - a development snapshot.
24.0.1 is now out, can you upgrade to that?
Ross
> On 14 Feb 2024, at 18:14, Markus Volk via lists.openembedded.org
> wrote:
>
> - refresh 0001-meson.build-check-for-all-linux-host_os-combinations.patch
> -
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexandre Belloni via
> lists.openembedded.org
> Sent: den 15 februari 2024 10:26
> To: belouargamoha...@gmail.com
> Cc: openembedded-core@lists.openembedded.org;
>
On Tue, 6 Feb 2024 at 19:49, Khem Raj wrote:
> diff --git a/meta/recipes-devtools/rust/files/rv32-rustix-libc-backend.patch
> b/meta/recipes-devtools/rust/files/rv32-rustix-libc-backend.patch
> new file mode 100644
> index 000..462a651428f
> --- /dev/null
> +++
101 - 194 of 194 matches
Mail list logo
