Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gawk* to *5.3.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gawk-upgrade-5.2.2-5.3.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 *vala* to *0.56.14* has
Succeeded.
Next steps:
- apply the patch: git am 0001-vala-upgrade-0.56.13-0.56.14.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 *vulkan-samples* to
*2be6f826269be1731cf9f8631b4f4d97364164f8* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe vulkan-samples failed.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lsof* to *4.99.0* 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.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsecret* to *0.21.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsecret-upgrade-0.21.1-0.21.2.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 *kmscube* to
*96d63eb59e34c647cda1cbb489265f8c536ae055* has Succeeded.
Next steps:
- apply the patch: git am 0001-kmscube-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cairo* to *1.18.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe cairo 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 *libva-utils* to *2.20.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libva-utils-upgrade-2.20.0-2.20.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 *weston* to *13.0.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-weston-upgrade-12.0.2-13.0.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.03* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.17.01-0.17.03.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 *texinfo* to *7.1* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade texinfo -V 7.1
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *appstream* to *1.0.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe appstream 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 *libxrandr* to *1.5.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxrandr-upgrade-1.5.3-1.5.4.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 *piglit* to
*8c88708145af4f75a3a2eaf8fd08d649acc02fcc* has Succeeded.
Next steps:
- apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *waffle* to *1.8.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe waffle 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 *enchant2* to *2.6.4* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-enchant2-upgrade-2.6.2-2.6.4.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20231211*
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 *puzzles* to
*08365fb260ae6e32442dd9f196e65d13facb4b33* has Succeeded.
Next steps:
- apply the patch: git am 0001-puzzles-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bmap-tools* to *3.7* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade bmap-tools -V 3.7 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *icu* to *74-2* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade icu -V 74-2
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 *libusb1* to *1.0.27* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libusb1 -V 1.0.27
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *repo* to *2.40* has Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.39-2.40.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 *rpm* to *4.19.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rpm 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 *cargo* to *1.74.1* 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 *go-helloworld* to
*1d6d2400d4027025cb8edc86a139c9c581d672f7* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade go-helloworld
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust* to *1.74.1* 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 *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 *shadow* to *4.14.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe shadow 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 *systemd-bootchart* to *235*
has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd-bootchart failed.
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *valgrind* to *3.22.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-valgrind-upgrade-3.21.0-3.22.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xserver-xorg* to *21.1.10*
has Succeeded.
Next steps:
- apply the patch: git am 0001-xserver-xorg-upgrade-21.1.9-21.1.10.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 *diffoscope* to *253* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-252-253.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 *gpgme* to *1.23.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gpgme-upgrade-1.23.1-1.23.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 *python3* to *3.12.1* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3 -V 3.12.1
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libstd-rs* to *1.74.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libstd-rs 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 *qemu* to *8.1.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-qemu-upgrade-8.1.2-8.1.3.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust-llvm* to *1.74.1* 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 *gdb* to *14.1* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: finish -f gdb
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 *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 *python3-hatchling* to
*1.20.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.18.0-1.20.0.patch
- check the changes to upstream
On Fri, 15 Dec 2023 at 17:04, Richard Purdie
wrote:
> > Meanwhile I'd like to implement what I mentioned in note (1) in patch
> > 4/9, as it's a real regression that I realized only today as I was
> > preparing the patchset for submission and now it's bothering me :)
>
> Yes, it is and I do
LGTM, Thanks
Reviewed-By: Joshua Watt
On Fri, Dec 15, 2023 at 10:11 AM Jeremy Puhlman via
lists.openembedded.org
wrote:
>
> From: "Jeremy A. Puhlman"
>
> On occasion a file is attmpeded to be opened prior to the
> creation of the spdx_workdir. Create the directory before
> the open, just in
On Fri, Dec 15, 2023 at 4:37 AM Johannes Pointner wrote:
>
> On Wed, Dec 13, 2023 at 12:01 PM Ross Burton wrote:
> >
> > On 6 Dec 2023, at 07:40, Johannes Pointner via lists.openembedded.org
> > wrote:
> > >
> > > From: Johannes Pointner
> > >
> > > If DISTRO_FEATURE usrmerge is enabled,
From: Ross Burton
The event test suite is full of timing-sensitive test cases, so skip
them too.
[ YOCTO #15321 ]
Signed-off-by: Ross Burton
---
meta/recipes-devtools/tcltk/tcl/run-ptest | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Dec 15, 2023 at 4:41 AM Alex Kiernan wrote:
>
> On Thu, Dec 14, 2023 at 10:28 AM Ross Burton wrote:
> >
> > On 13 Dec 2023, at 14:06, Richard Purdie via lists.openembedded.org
> > wrote:
> > > I've run this with this patch included:
> > >
> > >
This update requires libadwaita 1.4.2 and also some backports for
gnome-software
On Fri, Dec 15 2023 at 06:30:56 PM +01:00:00, Markus Volk
wrote:
- remove backport patch
- update 0001-remove-hardcoded-path.patch
- fix api-documentation
Version 1.0.0
~~
Released: 2023-11-11
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 *systemd-boot* to *255* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd-boot 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 *btrfs-tools* to *6.6.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.5.3-6.6.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 *cmake* to *3.28.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.27.7-3.28.1.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux-libuuid* to
*2.39.3* 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 *dpkg* to *1.22.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dpkg-upgrade-1.22.0-1.22.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 *go* to *1.21.5* 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 *pkgconf* to *2.1.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pkgconf-upgrade-2.0.3-2.1.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 *ttyrun* to *2.30.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ttyrun-upgrade-2.29.0-2.30.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 *go-runtime* to *1.21.5* 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 *usbutils* to *017* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-usbutils-upgrade-015-017.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kbd* to *2.6.4* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade kbd -V 2.6.4
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 *dbus-wait* to
*64bc7c8fae61ded0c4e555aa775911f84c56e438* has Succeeded.
Next steps:
- apply the patch: git am 0001-dbus-wait-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bluez5* to *5.71* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bluez5-upgrade-5.70-5.71.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 *systemd* to *255* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd failed.
NOTE: Reconnecting to bitbake server...
Loading
=
Version 1.4.2
=
- Really fix build with libappstream 1.0
=
Version 1.4.1
=
- Fix build with MSVC
- Fix build with libappstream 1.0
- AdwCarousel
- Fix carousel scroll behavior with page reordering
- AdwComboRow
- Fix focus when opening the
- remove backport patch
- update 0001-remove-hardcoded-path.patch
- fix api-documentation
Version 1.0.0
~~
Released: 2023-11-11
Notes:
* This version breaks API and bumps the SONAME of libappstream!
Applications using AppStream will have to be ported to the new API.
The 1.0
From: Robert Yang
The following changes since commit ae642a4b038c6946e6c8aa9778bf09099d938a31:
sstate: Fix dir ownership issues in SSTATE_DIR (2023-12-15 11:14:29 +)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/nfs-utils
From: Robert Yang
Update Upstream-Status for
0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch.
Signed-off-by: Robert Yang
---
.../0001-reexport.h-Include-unistd.h-to-compile-with-musl.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, 2023-12-14 at 18:28 +0100, Alexander Kanavin wrote:
> On Thu, 14 Dec 2023 at 15:39, Richard Purdie
> wrote:
>
> > I not entirely happy about this since start_worker() executes processes
> > and isn't trivial. The code is careful enough to tear them down too at
> > exit but it is all a
On Fri, 2023-12-15 at 17:49 +0100, Alexander Kanavin wrote:
> On Fri, 15 Dec 2023 at 17:04, Richard Purdie
> wrote:
>
> > > Meanwhile I'd like to implement what I mentioned in note (1) in patch
> > > 4/9, as it's a real regression that I realized only today as I was
> > > preparing the patchset
From: "Jeremy A. Puhlman"
On occasion a file is attmpeded to be opened prior to the
creation of the spdx_workdir. Create the directory before
the open, just in case.
File: '/build/layers/poky/meta/classes/create-spdx-2.2.bbclass', lineno: 1081,
function: combine_spdx
1077:)
On Thu, 14 Dec 2023 at 22:31, Bruce Ashfield wrote:
>
> To avoid burning everyone out even more (plus Scarthgap m1 is going to
> build shortly), I'm not sending the new reference kernel updates until
> January.
>
> Even just the send of them and any AB runs will steal time and be a
> distraction
On Fri, 2023-12-15 at 16:47 -0700, Joshua Watt wrote:
> On Fri, Dec 15, 2023 at 3:47 PM Richard Purdie
> wrote:
> >
> > On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> > > Adds the path to the runtime state directory (/run). In particular,
> > > systemd units need to have the correct
On Fri, Dec 15, 2023 at 3:47 PM Richard Purdie
wrote:
>
> On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> > Adds the path to the runtime state directory (/run). In particular,
> > systemd units need to have the correct path to the runtime directory
> > because RequiresMountsFor doesn't
When SRCREV is used, call bb.fetch.get_srcrev() before accessing
SRC_URI. Without this new bb.fetch.get_srcrev() call, SRC_URI might be
accessed before SRCREV had a chance to be processed.
In master, this is fixed by
Le 14/12/2023 à 22:50, Yoann Congal a écrit :
> Le 14/12/2023 à 17:24, Steve Sakoman a écrit :
>> This patch resulted in oe-seftest failures on the autobuilder:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6322
>>
>> A representative log:
>>
>>
systemd-boot native recipe provides ukify tool to build
UKI images for systemd-boot
Signed-off-by: Viswanath Kraleti
---
.../systemd/systemd-boot-native_254.4.bb | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
Converts IPK package generation to use zstd instead of xz. zstd has a
much larger compression/speed tradeoff range allowing users to choose
what suits them best. In addition, it support parallel compression for
additional compression speed up.
A new variable called ZSTD_DEFAULTS is provided to
On Fri, 2023-12-15 at 13:51 -0700, Joshua Watt wrote:
>
> @@ -337,7 +335,7 @@ CONVERSION_CMD:lz4 = "lz4 -9 -z -l ${IMAGE_NAME}.${type}
> ${IMAGE_NAME}.${type}.l
> CONVERSION_CMD:lzo = "lzop -9 ${IMAGE_NAME}.${type}"
> CONVERSION_CMD:zip = "zip ${ZIP_COMPRESSION_LEVEL} ${IMAGE_NAME}.${type}.zip
Adds the path to the runtime state directory (/run). In particular,
systemd units need to have the correct path to the runtime directory
because RequiresMountsFor doesn't follow symbolic links. This means that
if a unit calls out a directory in /var/run (a symbolic link to /run),
it may actually
The state directory must be correctly specified as under /run because
RequiresMountsFor doesn't follow symbolic links which means the unit may
run before /run is mounted if the default of /var/run/rpcbind is kept
Signed-off-by: Joshua Watt
---
meta/recipes-extended/rpcbind/rpcbind_1.2.6.bb | 2
On Fri, 2023-12-15 at 13:34 -0700, Joshua Watt wrote:
> Adds the path to the runtime state directory (/run). In particular,
> systemd units need to have the correct path to the runtime directory
> because RequiresMountsFor doesn't follow symbolic links. This means that
> if a unit calls out a
I think a space is needed at the end of the string. We get into string
concatenation forning different element
| ERROR: _exec_cmd: export
On 15 Dec 2023, at 10:49, Yoann Congal wrote:
> FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-raid tests)
> also prevent bluez to be built in a default core-image-minimal build, we can
> skip this one (strace: Disable bluetooth support by default) and still fix
> [YOCTO
This avoids the following error when running `devtool modify` on a
recipe that has a menuconfig task, but does not have
KCONFIG_CONFIG_ENABLE_MENUCONFIG set.
.../temp/run.do_configure.4163366: line 152:
${@ oe.types.boolean('${KCONFIG_CONFIG_ENABLE_MENUCONFIG}') }: bad
substitution
On Fri, 2023-12-15 at 11:59 +, Ross Burton wrote:
> On 15 Dec 2023, at 10:49, Yoann Congal wrote:
> > FYI, since Khem's patch ([OE-core] [PATCH] util-linux: Delete md-
> > raid tests) also prevent bluez to be built in a default core-image-
> > minimal build, we can skip this one (strace:
On Wed, Dec 13, 2023 at 12:01 PM Ross Burton wrote:
>
> On 6 Dec 2023, at 07:40, Johannes Pointner via lists.openembedded.org
> wrote:
> >
> > From: Johannes Pointner
> >
> > If DISTRO_FEATURE usrmerge is enabled, SLIBDIR is just a symlink to LIBDIR.
> > ldconfig-native uses hardcoded paths
From: Lee Chee Yang
update include fix for CVE-2023-46218.
skip test 1477 which check that libcurl-errors.3 and the public
header files have the same set of error codes.
Notes: This test is not included in the source tarball.
https://github.com/curl/curl/issues/12462
Release Notes:
curl and
Hi,
Le 14/12/2023 à 20:34, Khem Raj a écrit :
> These tests are marked as known failures upstream as well [1]
> if we delete them then we can drop dependency on mdadm for ptests which
> can further reduce the dependency chain for ptest enabled minimal images
>
> [1]
>
Le 14/12/2023 à 20:36, Khem Raj a écrit :
> On Thu, Dec 14, 2023 at 11:33 AM Alexandre Belloni
> wrote:
>>
>> On 14/12/2023 10:53:05-0800, Khem Raj wrote:
>>> On Thu, Dec 14, 2023 at 1:10 AM Alexander Kanavin
>>> wrote:
On Wed, 13 Dec 2023 at 09:57, Yoann Congal wrote:
>
>
On Thu, Dec 14, 2023 at 10:28 AM Ross Burton wrote:
>
> On 13 Dec 2023, at 14:06, Richard Purdie via lists.openembedded.org
> wrote:
> > I've run this with this patch included:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4082
>
> Same failure:
>
>
- build amd vulkan driver for x86 platforms
- drop included patch
[https://gitlab.freedesktop.org/mesa/mesa/-/blob/1fbdd37d4c1133ced5eb9812daa1fff04cbf5daa/meson.build#L1711]
Signed-off-by: Lucas Stach
---
Based on the 23.3.0 update patch [1] from Markus Volk, but bumped to 23.3.1
and fixed
90 matches
Mail list logo
