On Sat, 22 Oct 2022 at 05:07, Khem Raj wrote:
>>> we should apply the v1 of patch and move on.
>>
>>
>> No again. Riscv32 is already listed so it’s on you to use existing mapping
>> to use those entries, and not add new ones.
>
>
> ?
> v1 is passing the needed options via cflags. No patching nee
On Fri, Oct 21, 2022 at 7:58 PM Alexander Kanavin
wrote:
>
>
> On Fri 21. Oct 2022 at 23.49, Khem Raj wrote:
>
>> On Fri, Oct 21, 2022 at 2:01 PM Alexander Kanavin
>> wrote:
>> >
>> > On Fri, 21 Oct 2022 at 22:05, Khem Raj wrote:
>> > > Update the arch part of tuple to consider OE's names
>> >
On Fri 21. Oct 2022 at 23.49, Khem Raj wrote:
> On Fri, Oct 21, 2022 at 2:01 PM Alexander Kanavin
> wrote:
> >
> > On Fri, 21 Oct 2022 at 22:05, Khem Raj wrote:
> > > Update the arch part of tuple to consider OE's names
> > > for riscv32
> >
> > > +--- a/vendor/crossbeam-utils-0.8.8/no_atomic.r
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Randy MacLeod
> Sent: den 18 oktober 2022 02:14
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] kbd: package some fonts as restricted
>
> The distribution terms of the Agafari
The U-Boot signing code is a bit of a mess. The problem is that mkimage
determines the public keys to embed into a device tree based on an image
that it is signing. This results in all sorts of contortions: U-Boot has to
be available to the kernel recipe so that it can have the correct public
keys
In preparation for the next commit, split off several
Signed-off-by: Sean Anderson
---
meta/classes-recipe/kernel-fitimage.bbclass | 25 +
meta/classes-recipe/uboot-config.bbclass| 3 +++
meta/classes-recipe/uboot-sign.bbclass | 19
3 files changed
uboot_fitimage_assemble is called from one place with the same
arguments. Instead of using shell variables as intermediaries, simplify
the function by using the bitbake variables directly. Removing a layer
of indirection makes it easier to determine what values are being
substituted in. Some variab
We have a specific variable for the path to the boot directory. Use it
instead of open-coding this path.
Signed-off-by: Sean Anderson
---
meta/classes-recipe/kernel-fitimage.bbclass | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta/classes-recipe/kernel-f
This series reworks the uboot-sign and kernel-fitimage classes to cut their
intertwining web of dependencies. We do this by signing the kernel image
twice: once for real, and once to embed the keys into U-Boot's dtb. This
cuts two of the dependencies between U-Boot and Linux's recipes, and
moves th
When generating our SPL-verifying certificate, we use FIT_KEY_REQ_ARGS,
which is intended for the U-Boot-verifying certificate. Instead, use
UBOOT_FIT_KEY_REQ_ARGS.
Fixes: 0e6b0fefa0 ("u-boot: Use a different Key for SPL signing")
Signed-off-by: Sean Anderson
---
meta/classes-recipe/uboot-sign.
Replacing sysroot_stage_all by a no-op recipe makes it difficult for
bbappends to stage files intentionally. Instead, just clear
SYSROOT_DIRS, allowing other bbappends to easily add new directories.
Signed-off-by: Sean Anderson
---
meta/classes-recipe/kernel.bbclass | 4 +---
1 file changed, 1
The trailing slash in ${B} caused -fdebug-prefix-map=${B}=... to not
match as intended, resulting in ${TMPDIR} ending up in files in
${PN}-dbg when externalsrc was in use, which in turn triggered buildpath
QA warnings.
Signed-off-by: Peter Kjellerstedt
---
meta/classes-recipe/externalsrc.bbclass
On Wed, Oct 19, 2022 at 8:29 AM Ross Burton wrote:
>
> On 19 Oct 2022, at 07:34, Khem Raj via lists.openembedded.org
> wrote:
> >
> > On Tue, Oct 18, 2022 at 10:42 PM Alexander Kanavin
> > wrote:
> >>
> >> Can you show examples where this is needed? Custom variable does not seem
> >> a good id
On Fri, Oct 21, 2022 at 2:01 PM Alexander Kanavin
wrote:
>
> On Fri, 21 Oct 2022 at 22:05, Khem Raj wrote:
> > Update the arch part of tuple to consider OE's names
> > for riscv32
>
> > +--- a/vendor/crossbeam-utils-0.8.8/no_atomic.rs
> > b/vendor/crossbeam-utils-0.8.8/no_atomic.rs
> > +@@ -
On Fri, 21 Oct 2022 at 22:05, Khem Raj wrote:
> Update the arch part of tuple to consider OE's names
> for riscv32
> +--- a/vendor/crossbeam-utils-0.8.8/no_atomic.rs
> b/vendor/crossbeam-utils-0.8.8/no_atomic.rs
> +@@ -49,6 +49,8 @@ const NO_ATOMIC_64: &[&str] = &[
> + "powerpc-wrs-vxwor
Update the arch part of tuple to consider OE's names
for riscv32
Signed-off-by: Khem Raj
---
- Add riscv32-* to known arches for crossbeam-utils
- Keep the patch for both crossbeam versions
.../rust/rust/crossbeam_atomic.patch | 26 ---
1 file changed, 16 insertions(+),
On Fri, Oct 21, 2022 at 10:28 AM Alexander Kanavin
wrote:
>
> On Fri, 21 Oct 2022 at 19:16, Khem Raj wrote:
>
> > anyway, the builds failed at exactly the same point so as I sensed it
> > does not work.
>
> You need to find out why though. Upstream maintains a list, and we
> need to use it, and n
Update the patch to apply to only 0.8.8 version
Update the arch part of tuple to consider OE's names
for riscv32
Signed-off-by: Khem Raj
---
- Add riscv32-* to known arches for crossbeam-utils
.../rust/rust/crossbeam_atomic.patch | 57 ++-
1 file changed, 16 insertions(
Instead of changing the script environment to affect the child
processes, make a copy of the environment with modifications and pass
that to subprocess.
Specifically, when dri rendering is enabled, LD_PRELOAD was being passed
to all processes created by the script which resulted in other commands
The bridge helper program is invoked directly from QEMU when it needs to
attach to a network bridge. As such, it is subject to the environment of
QEMU itself. Specifically, if bridging is enabled with direct rendering
acceleration, QEMU is run with an LD_PRELOAD that attempts to preload
several uni
On Fri, 21 Oct 2022 at 19:16, Khem Raj wrote:
> anyway, the builds failed at exactly the same point so as I sensed it
> does not work.
You need to find out why though. Upstream maintains a list, and we
need to use it, and not duplicate it piecemeal.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You rece
On Fri, Oct 21, 2022 at 10:12 AM Alexander Kanavin
wrote:
>
> On Fri, 21 Oct 2022 at 19:00, Khem Raj wrote:
> > > On Fri, 21 Oct 2022 at 18:07, Khem Raj wrote:
> > > > Looking briefly over the code, my educated guess is that target names
> > > > are still not matching
> > > > rusts tuple uses ri
On Fri, 21 Oct 2022 at 19:00, Khem Raj wrote:
> > On Fri, 21 Oct 2022 at 18:07, Khem Raj wrote:
> > > Looking briefly over the code, my educated guess is that target names
> > > are still not matching
> > > rusts tuple uses riscv32gc but we use riscv32
> >
> > I believe we have a remapping in met
On Fri, Oct 21, 2022 at 9:19 AM Alexander Kanavin
wrote:
>
> On Fri, 21 Oct 2022 at 18:07, Khem Raj wrote:
> > Looking briefly over the code, my educated guess is that target names
> > are still not matching
> > rusts tuple uses riscv32gc but we use riscv32
>
> I believe we have a remapping in me
Hi Willy
Thanks for the patch!
On 10/21/22 15:17, Willy Tu via lists.openembedded.org wrote:
Install API only if opensshinternals is in DISTRO_FEATURES.
Install the OpenSSH header + lib files for other repo to build using it.
For example, https://github.com/google/hiba is dependent on those fil
Hi Ross,
Thanks for the feedback.
Can you point to the right repo to update? Just to make sure that I
understand the concern, you are not referring to
https://github.com/openembedded/meta-openembedded/pull/597, right? I am
making changes to
http://cgit.openembedded.org/openembedded-core/tree/meta
On Fri, Oct 21, 2022 at 10:54 AM Alexander Kanavin
wrote:
>
> I think we had a similar problem in rust, and I ended up rewriting the
> shell script in python and running it with nativepython3 :-)
I had to re-write the script to be a C program because there wasn't
any way to make qemu find and inv
On Fri, 21 Oct 2022 at 18:07, Khem Raj wrote:
> Looking briefly over the code, my educated guess is that target names
> are still not matching
> rusts tuple uses riscv32gc but we use riscv32
I believe we have a remapping in meta/lib/oe/rust.py, can you check if
that works?
Alex
-=-=-=-=-=-=-=-=
Backport the fix from upstream to fix this CVE.
Signed-off-by: Ross Burton
---
.../lighttpd/lighttpd/CVE-2022-41556.patch| 31 +++
.../lighttpd/lighttpd_1.4.66.bb | 1 +
2 files changed, 32 insertions(+)
create mode 100644 meta/recipes-extended/lighttpd/lightt
On Fri, Oct 21, 2022 at 8:41 AM Alexander Kanavin
wrote:
>
> On Fri, 21 Oct 2022 at 16:05, Khem Raj wrote:
> > This patch is doing something else where its mapping and broadening
> > the architecture to match crossbeam's understanding of it.
> > Here issue is new where it does not yet realize tha
I think we had a similar problem in rust, and I ended up rewriting the
shell script in python and running it with nativepython3 :-)
Alex
On Fri, 21 Oct 2022 at 17:48, Joshua Watt wrote:
>
> Ya I've tracked it down to when qemu invokes the qemu-oe-bridge-helper
> to setup network bridging. This i
Ya I've tracked it down to when qemu invokes the qemu-oe-bridge-helper
to setup network bridging. This is a shell script that uses /bin/sh, and
as the log indicates, /bin/sh can't find the required symbols to start
up (and qemu fails).
I also see it when runqemu attempt so to invoke the stty p
This is the first time I hear about this - can you find out what is
expecting the symbol, and where it's supposed to come from?
Alex
On Fri, 21 Oct 2022 at 17:27, Joshua Watt wrote:
>
> This patch broke runqemu for me when I moved to kirkstone. I get this error:
>
> /bin/sh: symbol lookup error
On Fri, 21 Oct 2022 at 16:05, Khem Raj wrote:
> This patch is doing something else where its mapping and broadening
> the architecture to match crossbeam's understanding of it.
> Here issue is new where it does not yet realize that some
> architectures do not have 64bit atomics implemented.
Here'
The patches need your Signed-off-by: alongside the Upstream-Status.
Thanks,
Ross
> On 21 Oct 2022, at 14:16, Claus Stovgaard via lists.openembedded.org
> wrote:
>
> Backport of patch already present upstream to fix issues with invalid
> characters for GLIB when combining gstreamer1.0-libav wit
This patch broke runqemu for me when I moved to kirkstone. I get this error:
/bin/sh: symbol lookup error:
/grmn/prj/mrn/alchemy/build/tmp/eng/kirkstone/tetra/sysroots-uninative/x86_64-linux/lib/librt.so.1:
undefined symbol: __libc_unwind_link_get, version GLIBC_PRIVATE
And I'm not sure how to f
Hi,
oe-core doesn’t accept merge requests on the github mirrors, and you pushed to
meta-oe, which is a different repository.
>> + if ${@bb.utils.contains('DISTRO_FEATURES', 'opensshinternals', 'true',
>> 'false', d)}; then
This should be a PACKAGECONFIG, as it’s not a distro-wide setting.
>>
From: Sergei Zhmylev
In case user requested to build a binary repeatable package,
it's required to honor the SOURCE_DATE_EPOCH environment
variable. So forcefully set mtime inside all the routines
which modify fstab in case it is updated.
Signed-off-by: Sergei Zhmylev
---
scripts/lib/wic/parti
The code to parse arguments was inadvertently skipping all arguments in
the elif block after gl-es if it was specified on the command line.
Signed-off-by: Joshua Watt
---
scripts/runqemu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index 9
On Thu, Oct 20, 2022 at 11:04 PM Alexander Kanavin
wrote:
>
> We carry this patch, so that manual per-target fixups like this are
> not needed, and crossbeam's internal lists are used properly:
>
> https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/rust/rust/crossbeam_atomic.patch?h=mast
From: Omkar
Upgrade dbus from 1.12.22 to 1.12.24
Fix Below CVE's:
2022-42010
2022-42011
2022-42012
Signed-off-by: Omkar Patil
---
.../dbus/{dbus-test_1.12.22.bb => dbus-test_1.12.24.bb} | 0
meta/recipes-core/dbus/dbus.inc | 2 +-
meta/recipes-core/dbus
From: wangmy
(From OE-Core rev: 1fb8ea03cf6c4df4d8c2cc9329dfe80c83a37e2d)
Signed-off-by: Wang Mingyu
Signed-off-by: Richard Purdie
(cherry picked from commit dc98fba73aeac4d1e661475dfb4acfca94d6c8f8)
Signed-off-by: Omkar Patil
---
.../dbus/{dbus-test_1.12.20.bb => dbus-test_1.12.22.bb}
just for visibility.
On Fri, Oct 21, 2022 at 6:17 AM Willy Tu via lists.openembedded.org
wrote:
>
> Install API only if opensshinternals is in DISTRO_FEATURES.
>
> Install the OpenSSH header + lib files for other repo to build using it.
> For example, https://github.com/google/hiba is dependent
Install API only if opensshinternals is in DISTRO_FEATURES.
Install the OpenSSH header + lib files for other repo to build using it.
For example, https://github.com/google/hiba is dependent on those files
to build and this change is needed to meet that requirement.
https://github.com/openembedded
Backport of patch already present upstream to fix issues with invalid
characters for GLIB when combining gstreamer1.0-libav with ffmpeg 5.x.
Remove when gstreamer1.0-libav is upgraded to 1.21.1 or above
Signed-off-by: Claus Stovgaard
---
...r-APNG-encoder-property-registration.patch | 82 ++
Hi Adrian,
On 10/21/22 14:01, Adrian Freihofer wrote:
Signed-off-by: Adrian Freihofer
---
documentation/ref-manual/kickstart.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/documentation/ref-manual/kickstart.rst
b/documentation/ref-manual/kickstart.rst
index d82da0ee75..306295
Signed-off-by: Adrian Freihofer
---
documentation/ref-manual/kickstart.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/documentation/ref-manual/kickstart.rst
b/documentation/ref-manual/kickstart.rst
index d82da0ee75..30629563f2 100644
--- a/documentation/ref-manual/kickstart.rst
++
So if you would like this patch to be merged you need to do two things:
- enable ptest and add the component to ptest images
- take the patches that were submitted upstream and add them with
'Submitted' status, instead of this mono-patch
Alex
On Fri, 21 Oct 2022 at 11:12, Alexander Kanavin via
li
Please explain why oe-core should carry this (with all the maintenance
and rebase burden that brings) if the component is not ptest-enabled
and is not otherwise using those tests.
Besides, these fixes should go upstream first, which I already did for you:
https://github.com/giampaolo/psutil/pull/2
From: Changqing Li
* Add RDEPENDS for package python3-psutil-tests to fix following error:
$ python3 -m psutil.tests
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 187, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
Fi
50 matches
Mail list logo
