On Tue, Nov 7, 2023 at 10:09 PM Hemraj, Deepthi via
lists.openembedded.org
wrote:
>
> From: Deepthi Hemraj
>
> [YOCTO #15061]
> Rust multilib sdks broken because of the conflicts between attempted installs
> of rust-cross-canadian for arm and aarch64.
>
> Arm and aarch64 target architectures
From: Deepthi Hemraj
[YOCTO #15061]
Rust multilib sdks broken because of the conflicts between attempted installs
of rust-cross-canadian for arm and aarch64.
Arm and aarch64 target architectures are trying to install cargo.sh and rust.sh
in the same path which resulted in the issue.
The
From: Vijay Anusuri
Upstream-Status: Backport
[https://gitlab.freedesktop.org/xorg/xserver/-/commit/541ab2ecd41d4d8689e71855d93e492bc554719a
&
https://gitlab.freedesktop.org/xorg/xserver/-/commit/564ccf2ce9616620456102727acb8b0256b7bbd7]
Signed-off-by: Vijay Anusuri
---
From: Vijay Anusuri
Upstream-Status: Backport
[https://gitlab.freedesktop.org/xorg/xserver/-/commit/541ab2ecd41d4d8689e71855d93e492bc554719a
&
https://gitlab.freedesktop.org/xorg/xserver/-/commit/564ccf2ce9616620456102727acb8b0256b7bbd7]
Signed-off-by: Vijay Anusuri
---
On 11/6/23 23:50, Steve Sakoman wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Fri, Oct 20, 2023 at 12:47 PM Alexandre Belloni via
lists.openembedded.org
wrote:
The new website looks nice, just https://yoctoproject.org/development/releases/
is populated by:
Plugin JSON Content Importer Pro not running: Check Licence! Check that a
Licence is active for https://yoctoproject.org
Instead of actual release data.
Peter
From: yo...@lists.yoctoproject.org On
From: Ross Burton
e4487cae1 Bump version to 23.2.2
1e8478455 Xi/randr: fix handling of PropModeAppend/Prepend (CVE-2023-5367)
829a99117 Switch to libbsd-overlay
4f8a851b6 xwayland: Cancel the EI disconnect timer when freed
cc79b2a83 glamor: xv: Fix invalid accessing of plane attributes for NV12
Current Dev Position: YP 4.3 (Final Release)
Next Deadline: 27th October 2023 YP 4.3 Final Release
Next Team Meetings:
-
Bug Triage meeting Thursday November 9, 7:30 am PDT (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync
From: Jermain Horsman
The test creates a layer setup, modifies it to use a branch,
attempts a checkout using the modified file, it modifies the
layers setup again to use a revision restoring it to the
original state.
A final checkout is skipped as the revision might not be
present, additionally
From: Jermain Horsman
This allows for modifications of an existing configuration file
using current revisions.
Signed-off-by: Jermain Horsman
---
meta/lib/bblayers/updatesetup.py | 78
1 file changed, 78 insertions(+)
create mode 100644
From: Jermain Horsman
Having a default remote present allows for the checkout of a
branch in the case multiple remotes are available.
This requires an update to the json-schema and associated checks.
Signed-off-by: Jermain Horsman
---
meta/files/layers.example.json| 5
From: Jermain Horsman
Includes a function to determine the default remote.
Signed-off-by: Jermain Horsman
---
meta/lib/oe/buildcfg.py | 16
1 file changed, 16 insertions(+)
diff --git a/meta/lib/oe/buildcfg.py b/meta/lib/oe/buildcfg.py
index f9cb0cc74c..2ca654e56e 100644
---
From: Jermain Horsman
Refactor to use git functions from library.
Signed-off-by: Jermain Horsman
---
meta/lib/bblayers/makesetup.py | 32 ++--
1 file changed, 10 insertions(+), 22 deletions(-)
diff --git a/meta/lib/bblayers/makesetup.py
From: Jermain Horsman
Includes a git describe and git toplevel function and functions
to get info for git remotes.
Signed-off-by: Jermain Horsman
---
meta/lib/oe/buildcfg.py | 29 +
1 file changed, 29 insertions(+)
diff --git a/meta/lib/oe/buildcfg.py
From: Jermain Horsman
These changes allow for situations where one or more layers are checked out
using a branch instead of a revision, care is taken to make sure this works
when using multiple remotes.
All changes made are backwards compatible with older setup-layer json files.
Signed-off-by:
From: Jermain Horsman
During development it can be useful to use a branch instead of a
revision, e.g. when rebasing often or just for easy upgrading of
the setup.
This is a first iteration, it updates the generation of the
setup-layers.json file as well as the json schema for it.
This allows
Since syslinux is only compatible with platforms that use x86-based
CPUs, this change allows creation of bootable ISO images for other
EFI-compatible platforms by replacing invocation of the isohybrid
tool for those platforms with a python script that creates MBR
partition table with a single
Hello, Alex!
I created this patch in hope that I could ensure compatibility with legacy
platforms that use BIOS, that is why I kept the syslinux part.
I don't think it is a good idea to drop syslinux usage entirely, IMHO.
Best regards, Andrey.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
This begs the question. Should we drop syslinux usage altogether? It
hasn't been maintained for several years, and is unlikely to become
maintained again.
Alex
On Tue, 7 Nov 2023 at 15:51, Andrey Popov wrote:
>
> Since syslinux is only compatible with platforms that use x86-based
> CPUs, this
Since syslinux is only compatible with platforms that use x86-based
CPUs, this change allows creation of bootable ISO images for other
EFI-compatible platforms by replacing invocation of the isohybrid
tool for those platforms with a python script that creates MBR
partition table with a single
From: Massimiliano Minella
As stated in the LICENSES/README.md "Unless otherwise noted, the systemd
project sources are licensed under the terms and conditions of the GNU
Lesser General Public License v2.1 or later", so replace LGPL-2.1-only
with LGPL-2.1-or-later.
With the exception of some
On Tue, Nov 7, 2023 at 4:09 AM Max Krummenacher wrote:
>
> From: Max Krummenacher
>
> Kernel 6.7-rc1 commit 02e85f74668e ("tools: arm64: Add a Makefile for
> generating sysreg-defs.h") uses files from arch/arm64/tools/,
> gen-sysreg.awk and sysreg.
> Without the files the build of perf fails
On Tue, Nov 7, 2023 at 4:26 AM Rasmus Villemoes
wrote:
>
> From: Rasmus Villemoes
>
> Building for an arm64 target, e.g. qemuarm64 or a raspberrypi3,
> without "python" in PACKAGECONFIG, results in
>
> | Makefile.config:892: *** ERROR: No python interpreter needed for jevents
> generation.
On Tue, Nov 7 2023 at 11:18:15 AM +01:00:00, Markus Volk
wrote:
Shouldn't
they be as well tweaked to rely on the class doing the right thing?
functionwise its been ok but I've found some additional things to
cleanup, so I'll send a v2.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
Hi Richard,
On 07.11.2023 13:15, Richard Purdie wrote:
On Tue, 2023-11-07 at 13:00 +0100, Lukas Funke wrote:
From: Lukas Funke
Check if the filesystem is supported by the kernel before trying to
mount it. Systemd-mount will mount the directories asynchronously
resulting in stale directories
Lukas Funke escreveu no dia terça,
7/11/2023 à(s) 12:00:
> From: Lukas Funke
>
> Check if the filesystem is supported by the kernel before trying to
> mount it. Systemd-mount will mount the directories asynchronously
> resulting in stale directories if the devices filesystem is not
> supported.
Thanks a lot!
—runall didn’t occur to me at all.
Alex
On Tue 7. Nov 2023 at 13.01, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> You could reproduce an error in this test with:
>
> bitbake core-image-minimal
> bitbake tzcode-native -c cleansstate
> oe-selftest -r
>
Try to enable vapi build automatically if GI_DATA_ENABLED = True.
Do it basically the same way it is done for gi
Signed-off-by: Markus Volk
---
meta/classes-recipe/vala.bbclass | 23 +++
meta/recipes-gnome/gcr/gcr_4.1.0.bb | 2 --
On 7 Nov 2023, at 12:17, Ross Burton via lists.openembedded.org
wrote:
>
> On 6 Nov 2023, at 15:34, Vijay Anusuri via lists.openembedded.org
> wrote:
>>
>> From: Vijay Anusuri
>>
>> Upstream-Status: Backport
>
> This is not a backport as the MR is still open:
>
>
On 6 Nov 2023, at 15:34, Vijay Anusuri via lists.openembedded.org
wrote:
>
> From: Vijay Anusuri
>
> Upstream-Status: Backport
This is not a backport as the MR is still open:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1189
These are Submitted.
Ross
On Tue, 2023-11-07 at 13:00 +0100, Lukas Funke wrote:
> From: Lukas Funke
>
> Check if the filesystem is supported by the kernel before trying to
> mount it. Systemd-mount will mount the directories asynchronously
> resulting in stale directories if the devices filesystem is not
> supported.
>
You could reproduce an error in this test with:
bitbake core-image-minimal
bitbake tzcode-native -c cleansstate
oe-selftest -r
sstatetests.SStatePrintdiff.test_image_minimal_vs_base_do_configure
since tzcode-native isn't needed once tzdata is available and isn't rebuilt
by "bitbake
From: Lukas Funke
Check if the filesystem is supported by the kernel before trying to
mount it. Systemd-mount will mount the directories asynchronously
resulting in stale directories if the devices filesystem is not
supported.
Signed-off-by: Lukas Funke
---
From: Narpat Mali
There was an extra space between the result and ':'.
After removing extra space, the ptest result will be:
result : testname -> result: testname
Signed-off-by: Narpat Mali
---
meta/recipes-devtools/python/python3-jinja2/run-ptest | 2 +-
1 file changed, 1 insertion(+), 1
The Baekmuk font uses this license.
The license file was extracted from
http://kldp.net/baekmuk/release/865-baekmuk-ttf-2.2.tar.gz
The SPDX link for this license:
https://spdx.org/licenses/Baekmuk.html
Signed-off-by: Zoltán Böszörményi
---
meta/files/common-licenses/Baekmuk | 11 +++
You can add the license to the layer where the recipe is, see LICENSE_PATH
variable used in meta-oe for example.
On Tue, Nov 7, 2023 at 12:30 PM Zoltan Boszormenyi
wrote:
> Hi,
>
> I have a font package recipe for baekmuk-ttf-fonts
> which can't be built under Yocto 4.3 do to these:
>
>
I guess you can send a patch?
Alex
On Tue, 7 Nov 2023 at 12:30, Zoltan Boszormenyi wrote:
>
> Hi,
>
> I have a font package recipe for baekmuk-ttf-fonts
> which can't be built under Yocto 4.3 do to these:
>
> WARNING: baekmuk-ttf-fonts-2.2-r0 do_populate_lic: QA Issue:
> baekmuk-ttf-fonts: No
Hi,
I have a font package recipe for baekmuk-ttf-fonts
which can't be built under Yocto 4.3 do to these:
WARNING: baekmuk-ttf-fonts-2.2-r0 do_populate_lic: QA Issue: baekmuk-ttf-fonts: No generic
license file exists for: Baekmuk in any provider [license-exists]
ERROR: baekmuk-ttf-fonts-2.2-r0
From: Thomas Perrot
Here is list of changes in this major release
https://github.com/riscv-software-src/opensbi/compare/v1.2...v1.3.1
Signed-off-by: Thomas Perrot
---
meta/recipes-bsp/opensbi/{opensbi_1.2.bb => opensbi_1.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/RFC-scripts-oe-replicate-build-add-a-script-that-packages-and-replicates-a-yocto-build-elsewhere.patch
FAIL: test
This scripts takes an existing, active yocto build, and puts pieces of it
into a bundle directory, which is then placed in a tarball, and a
self-extracting shell archive. This allows moving the bundle to another
machine, or placing it on a network server for downloads.
The bundle includes:
- a
On Tue, Nov 7 2023 at 11:06:26 AM +01:00:00, Alexander Kanavin
wrote:
There is quite a bit more recipes in core that inherit vala. Shouldn't
they be as well tweaked to rely on the class doing the right thing?
yes, and I build almost all of them regulary. On a first look it seems
like they
There is quite a bit more recipes in core that inherit vala. Shouldn't
they be as well tweaked to rely on the class doing the right thing?
[ak@fedora poky]$ grep -ir vala meta*|grep inher
meta/recipes-support/libical/libical_3.0.16.bb:inherit cmake pkgconfig
gobject-introspection vala
Try to enable vapi build automatically if GI_DATA_ENABLED = True.
Do it basically the same way it is done for gi
Signed-off-by: Markus Volk
---
meta/classes-recipe/vala.bbclass | 23 +++
.../libdazzle/libdazzle_3.44.0.bb | 1 +
From: Rasmus Villemoes
Building for an arm64 target, e.g. qemuarm64 or a raspberrypi3,
without "python" in PACKAGECONFIG, results in
| Makefile.config:892: *** ERROR: No python interpreter needed for jevents
generation. Install python or build with NO_JEVENTS=1.. Stop.
Signed-off-by: Rasmus
In the recent upgrade, which started to be installed as which.debianutils and
the man
page was also renamed. Update the recipe to remove the now unneeded man page
alternatives
and rename the binary to match what the code expects. This avoids warnings like:
WARNING: debianutils-5.14-r0
On 06/11/2023 16.07, Richard Purdie wrote:
> On Mon, 2023-11-06 at 16:00 +0100, Rasmus Villemoes wrote:
>>
>> When I set PACKAGECONFIG for perf in a perf.bbappend file, without
>> python being in there, the build breaks:
>>
[...]
>> This difference is, to put it mildly, quite confusing and
On Wed, Aug 9, 2023 at 10:19 AM Max Krummenacher via
lists.openembedded.org
wrote:
>
> From: Max Krummenacher
>
> The current implementation expects the license file in NO_GENERIC_LICENSE
> specified as being relative to ${S}.
> Assuming that there are two source locations this gets confusing to
From: Max Krummenacher
Kernel 6.7-rc1 commit 02e85f74668e ("tools: arm64: Add a Makefile for
generating sysreg-defs.h") uses files from arch/arm64/tools/,
gen-sysreg.awk and sysreg.
Without the files the build of perf fails independent of the used
architecture (confirmed with armv7 and
The backported patch fixes the following warning:
systemd-vconsole-setup[221]: Failed to import credentials, ignoring: No such
file or directory
Signed-off-by: Chen Qi
---
...l-return-0-for-missing-creds-in-read.patch | 139 ++
meta/recipes-core/systemd/systemd_253.1.bb|
51 matches
Mail list logo
