Signed-off-by: Khem Raj
---
.../files/0001-dram-Fix-build-with-gcc-11.patch | 1 +
1 file changed, 1 insertion(+)
diff --git
a/recipes-bsp/trusted-firmware-a/files/0001-dram-Fix-build-with-gcc-11.patch
b/recipes-bsp/trusted-firmware-a/files/0001-dram-Fix-build-with-gcc-11.patc
this fails to build:
The stack trace of python calls that resulted in this exception/failure was:
File: '', lineno: 24, function:
0020:__anon_70__home_akuster_oss_clean_poky_meta_classes_recipe_rootfs_postcommands_bbclass(d)
0021:__anon_125__home_akuster_oss_clean_poky_meta_classes_recipe_image_
Signed-off-by: Armin Kuster
---
recipes-scanners/clamav/files/test.patch | 26
1 file changed, 26 deletions(-)
delete mode 100644 recipes-scanners/clamav/files/test.patch
diff --git a/recipes-scanners/clamav/files/test.patch
b/recipes-scanners/clamav/files/test.patch
d
These are changes I did so apply the appropriate label.
Signed-off-by: Armin Kuster
---
recipes-security/isic/files/configure_fix.patch | 5 ++---
recipes-security/isic/files/isic-0.07-make.patch| 4 +---
recipes-security/isic/files/isic-0.07-netinet.patch | 4 +---
3 files changed, 4 in
Hello Kai,
Can you rebase this to the latest master. There was a layer reorg
landed during the posting of this patch.
BR,
Armin
On 6/20/23 11:55 PM, Kai Kang wrote:
From: Kai Kang
Variables PREFERRED_PYTHON_PATH and PYTHON3_PATH are set with
${PYTHON_EXECUTABLE}. For cross compile, ${PYTH
Add a eval script.
Lets see how many checks pass out of the box
Signed-off-by: Armin Kuster
---
.../0001-standard.profile-expand-checks.patch | 228 ++
.../scap-security-guide/files/run_eval.sh | 3 +
.../scap-security-guide_0.1.67.bb | 12 +-
3 files changed,
We already have this directory to save the environment variable settings
so they can be copied into the initramfs for runtime setup.
There are quite a few veritysetup args, and the nature of storing the
hash data after the filesystem data in an "oversized" partition can be
error prone due to round
In making changes to the existing veritysetup arg list, it is harder to
see what the proposed change is since they are are glued together on one
long line. Break them up so reviewing future unified diffs will be more
easy to visually parse.
This also makes it easier to temp. dump the args to a fi
Create a wks.in that allows an out-of-the-box build of a bootable
USB image using systemd and the hash data as a separate device or
partition.
A focus here was to ensure we used proper GPT names and GPT types,
and the GPT UUIDs that are based on splitting the root hash.
Signed-off-by: Paul Gortma
There are essentially two ways for dealing with where to put the hash
data for dm-verity block integrity checks.
You can store both in a single partition, by using ~95% of the storage
space for the filesystem and the remaining 5% tail for the hash, or you
can use a completely separate partition (o
The prior commits create the separate hash so now it is time to update
the initramfs framework so that veritysetup, which is responsible for
binding the data and hash, is aware of when separate hash is in use,
and can react accordingly.
The added code follows the existing appended hash code style,
The primary goal here is to enable storage of dm-verity hash on a separate
device/partition.
There are essentially two ways for dealing with where to put the hash data
for dm-verity block integrity checks.
You can store both in a single partition, by using ~95% of the storage space
for the filesy
Export the dynamic build data for consumption in wic image generation.
It can either be included directly or manually parsed for useful chunks
in custom configurations people end up making.
For convenience, it is placed alongside the work-shared/dm-verity dir
where we already store the plain envi
Without these one line descriptors and their associated marker prefix,
the output from "wic list images" only shows they are available as a
choice but w/o any description
Signed-off-by: Paul Gortmaker
---
wic/beaglebone-yocto-verity.wks.in | 1 +
wic/systemd-bootdisk-dmverity.wks.in | 1 +
2 f
Hi,
After a few problems that took me a while to fix, I've now used a default poky
with default configuration, and it builds just fine.
There must be something in one of my configuration files that appends that
"image/local" at the end of WORKDIR, but I've search in entire folder and there
are
On Wed, Jun 21, 2023 at 3:42 PM akuster808 wrote:
> Hello Martin,
>
Hello Armin,
On 6/21/23 6:42 AM, Martin Jansa wrote:
> > There is new patch-status QA check in oe-core:
> >
> https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
> >
> > This is te
Hello Martin,
On 6/21/23 6:42 AM, Martin Jansa wrote:
There is new patch-status QA check in oe-core:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
This is temporary work around just to hide _many_ warnings from
optional patch-status (if you a
On Wed, 2023-06-21 at 04:10 -0700, lavkhush2...@gmail.com wrote:
> Hi all,
>
> I want to create .deb file of package python3-speechrecognition , I
> successfully builded natively on target board riscv platform and i
> copied binary from target board and with using recipe i am copying
> binary
That's not how it works. You need to write a recipe that cross-builds
the needed package from source. Taking prebuilt binaries from
elsewhere is asking for trouble, and not recommended even for
experienced developers.
Alex
On Wed, 21 Jun 2023 at 13:10, wrote:
>
> Hi all,
>
> I want to create .de
Hi all,
I want to create .deb file of package python3-speechrecognition , I
successfully builded natively on target board riscv platform and i copied
binary from target board and with using recipe i am copying binary in path:
/usr/lib/python3.8/site-packages and trying to create .deb file f
Hi,
I have problem with reproducibility of this issue.
What I did: build buildtools tarball and install it
Than build sdk with this buildtools tarball.
1. No changes. Buildtools tarball installed and relocated into.
/nobackup/oobitots/btt-master/sysroots/x86_64-xesdk-linux/usr/bin/file point
There is new patch-status QA check in oe-core:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
This is temporary work around just to hide _many_ warnings from
optional patch-status (if you add it to WARN_QA).
This just added
Upstream-Status: Pend
Hi Team,
Is there any update for this patch? Can you pIs let me know, if there's any
issue with the patch.
Thanks,
Shubham
On Wed, Jun 7, 2023 at 12:57 PM Shubham Kulkarni via lists.yoctoproject.org
wrote:
> From: Shubham Kulkarni
>
> audit repository clone failing with git protocol as
> gi
23 matches
Mail list logo
