Hi Richard,
> On Mon, 2024-09-16 at 19:38 +, Jonas Mark (BT-FS/ENG1-Mue) wrote:
> > I am wondering whether it would be reasonable to ask for backporting
> > of the fix for inter-recipe useradd dependencies to Kirkstone?
> >
> > I am referring to the fix for bug #13419 which was fixed on
> Scar
Hi Alexander,
yes, we'll try to chat with you when we see you.
I am convinced your workaround would work. According to the adduserbase.bbclass
it should just give a notice (no error, no warning) in case the group already
exists.
We started by trying to backport the fix from Scarthgap. More in
Hello Steve and Richard,
I am wondering whether it would be reasonable to ask for backporting of the fix
for inter-recipe useradd dependencies to Kirkstone?
I am referring to the fix for bug #13419 which was fixed on Scarthgap.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13419
I understa
From: Ricardo Simoes
To fulfill OverlayFS workdir requirements, the mount-copybind script
creates a workdir. But if the mount operation fails for any reason,
the workdir is left there.
Then, subsequent runs of mount-copybind will again try to
create the directory and pollute system logs with fai
From: Ricardo Simoes
When the mountpoint parameter is a directory, the mount-copybind will
first try to use OverlayFS. Because of that, it needs to create the
OverlayFS workdir (determined by the overlay_workdir).
But if the environment variable MOUNT_COPYBIND_AVOID_OVERLAYFS is set
to "1", the
From: Ricardo Simoes
The recipe `volatile-binds` relies on the `mount-copybind` script
to create volatile mount points. In commit [1], the script was modified
to use OverlayFS as the primary mount strategy. If OverlayFS fails, it
falls back to an old-school bind mount.
To meet the requirements o
From: Ricardo Simoes
This commit sets the CVE_PRODUCT variable to "libusb" to match the
product name used in the NIST CPE database [1].
[1]: https://nvd.nist.gov/products/cpe/search
Signed-off-by: Ricardo Simoes
Signed-off-by: Mark Jonas
---
meta/recipes-support/libusb/libusb1_1.0.27.bb | 2
From: Jonas Höppner
The commit d7341f1f22c32ff6cc95d7127f26f87d7fc9c6bd has introduced a
variable to disable the symlink creation for kernel images.
kernel.bbclass contains code to generate a pkg_posinst step for the
kernel-image package which will generate a symlink after installation
on target/
The commit d7341f1f22c32ff6cc95d7127f26f87d7fc9c6bd has introduced a
variable to disable the symlink creation for kernel images.
kernel.bbclass contains code to generate a pkg_posinst step for the
kernel-image package which will generate a symlink after installation
on target/during rootfs creation
Hi Bruce and Steve,
> Von: Bruce Ashfield
> On Fri, Jun 4, 2021 at 11:09 AM Steve Sakoman wrote:
> >
> > On Fri, Jun 4, 2021 at 2:45 AM Jonas Mark (BT-FIR/ENG1-Grb)
> > wrote:
> > >
> > > Hi,
> > >
> > > We are using DT overlays and have the need to pass the -@ parameter
> > > in DTC_FLAGS to
Hi,
We are using DT overlays and have the need to pass the -@ parameter in
DTC_FLAGS to Linux' make. The patch
"kernel-devicetree: Introduce KERNEL_DTC_FLAGS to pass dtc flags"
https://git.openembedded.org/openembedded-core/commit/?h=hardknott&id=063b5de86624a42b0aa784db6dddc7552a6dee7f
makes t
From: Jonas Höppner
Currently the headers are not installed and the ltp-dev package is
empty.
This patch adds an include-install make target in the do_install step to
install them in sysroot which ends up as a working ltp-dev package.
Signed-off-by: Jonas Höppner
---
meta/recipes-extended/ltp
12 matches
Mail list logo
