[Edited Message Follows]
When i apply and check my patch in my git bash console i have no any error
about "malformed diff lines".
Livius@DESKTOP-LIVIUS MINGW64 /d/Yocto/openembedded-core (master)
$ git apply --check
0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.pat
[Edited Message Follows]
When i apply and check my patch in my git bash console i have no any error
about "malformed diff lines".
Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$ git apply --check
0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.pat
When i apply my patch in my git bash console i have no any error about
"malformed diff lines".
Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$ git am 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch
Applying: archiver.bbclass: Fix work-share
From: Benjamin Szőke
Restore to use checking inherited kernel class, because it possible
that some BSP's linux kernel recipe (like linux-fslc in meta-freescale)
change source dir to S = "${WORKDIR}/git" symbolic link and in this
case work-shared checking is failed for kernel recipe.
It seems to me i found, when it can not work well.
I use linux-fslc recipe from meta-freescale which redefining somewhy source
directory in linux-imx.inc file.
https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/linux/linux-imx.inc#L22
S = "${WORKDIR}/git"
In kernel.bbclass
[Edited Message Follows]
Hi,
https://github.com/openembedded/openembedded-core/commit/5fbb4ca8da4f4f1ea426275c45634802dcb5a575
This patch caused something terrible wrong behavior, because
".../work-shared//kernel-source/" directory is totally empty and the
complete Linux kernel source is
Hi,
https://github.com/openembedded/openembedded-core/commit/5fbb4ca8da4f4f1ea426275c45634802dcb5a575
This patch caused something terrible wrong behavior, because
".../work-shared//kernel-source/" directory is totally empty and the
complete Linux kernel source is missing if INHERIT +=
[Edited Message Follows]
Thanks the suggestion, it seems it can solve this issue.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200315):
https://lists.openembedded.org/g/openembedded-core/message/200315
Mute This Topic:
Thanks the suggestion, it seems can solve this issue.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200315):
https://lists.openembedded.org/g/openembedded-core/message/200315
Mute This Topic: https://lists.openembedded.org/mt/105616493/21656
As i see it is merged only for master branch of poky repo. Will it be merged to
scarthgap branch also?
It seems to me i have an issue which can be solved in scarthgap via this patch:
https://github.com/DynamicDevices/meta-mono/pull/224#issuecomment-2144017190
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
It is reported:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14979
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174213):
https://lists.openembedded.org/g/openembedded-core/message/174213
Mute This Topic:
As i see in OpenEmbedded Layer Index website (
https://layers.openembedded.org/layerindex/branch/master/layers/ ) automatic
layer updates stoped to works for all layers. Please fix it.
https://layers.openembedded.org/layerindex/layerupdate/9393191/
It is done: https://lists.openembedded.org/g/openembedded-core/message/172841
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172933):
https://lists.openembedded.org/g/openembedded-core/message/172933
Mute This Topic:
From: Benjamin Szőke
Add 7-Zip support in conversion types and commands. Default arguments of 7-Zip
are compression level: 9, method: BZip2, extension: 7z. All these are
overridable from local.con for any other use case in user side. First goal was
to make an alternative zip conversion which
From: Benjamin Szőke
Signed-off-by: Benjamin Szőke
---
meta/classes-recipe/image_types.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes-recipe/image_types.bbclass
b/meta/classes-recipe/image_types.bbclass
index f70c71b9d4..ae00728a74 100644
---
From: Benjamin Szőke
Add 7-Zip support in conversion types and commands. Default arguments of 7-Zip
are compression level: 9, method: BZip2, extension: zip. All these are
overridable from local.con for any other use case in user side. First goal was
to make an alternative zip conversion which
Good point for this zip extension conflict, you are right. If somebody is a
overzealous developer can use IMAGE_TYPES = "wic.zip wic.7zip" then sure there
will be an extension conflict after the compression in deploy time. This
escaped my notice this because this use case is not so realistic
I resend this patch via " git send-email".
https://lists.openembedded.org/g/openembedded-core/message/172765
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172767):
https://lists.openembedded.org/g/openembedded-core/message/172767
Mute This Topic:
From: Benjamin Szőke
Add 7-Zip support in conversion types and commands. Default arguments of 7-Zip
are compression level: 9, method: BZip2, extension: zip. All these are
overridable from local.con for any other use case in user side. First goal was
to make an alternative zip conversion which
I week ago Python 3 was succesfully updated to Python 3.11 in Poky master (
https://git.yoctoproject.org/poky/commit/?id=b06633b6ae91132f444a15a7f11dd778f01d5b6f
). Can we request to get it in kirkstone branch too? There are many new useful
feature in new Python 3.11, it is faster and better in
What should i check in buildhistory? In my buildhistory folder linux-firmware
folder contains all packages as a subfolders, like was in my
tmp/deploy/rpm/noarch. Following content is in my
linux-firmware/linux-firmware-imx-sdma-imx7d/latest text file.
PE = 1
PV = 20220913
PR = r0
RPROVIDES =
I have a linux-firmware_%.bbappend (
https://github.com/Freescale/meta-freescale-3rdparty/blob/kirkstone/recipes-kernel/linux-firmware/linux-firmware_%25.bbappend
) from meta-freescale-3rdparty layer. I think, it is too simple, it can not
cause the problem. In my local.conf I set up to generate
In my tmp/deploy/rpm/noarch folder i can see many-many other firmware .rpm
files like linux-firmware-bcm43xx, linux-firmware-nvidia-tegra and so on, these
were not planed to be installed. It seems to me, the full linux-firmware
package was deployed somehow. I think i am using poky now, this is
Hi,
I would like to install linux-firmware-ath10k and linux-firmware-imx-sdma-imx7d
firmware package to my image recipe in kirkstone release but when i append them
to IMAGE_INSTALL somewhy each pack from linux-firmware recipe installs itself.
It is extramly large in size about 500 MB, it is
I can not use 'git send-email' because my workstation is not configured to be
able to send any mail. You can use my patch, the content is available under
'--' what is need to for it, or I can copy and paste it and re-send to this
thread. But in 2022, I really recommend to you to improve your
I added to support 7-Zip in conversion types/commands. It is fully configurable
in compression level, method and file extension.
From: "Benjamin Szőke"
Date: Thu, 25 Aug 2022 21:45:55 +0200
Subject: [PATCH] image_types: add 7-Zip support in conversion types and commands
---
I got this "feature" on Yocto project of Xilinx (
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto )
rel-v2022.1 (honister). It seems to me my Linux kernel uses SHA-512 in default
because after my first password change i could se the ident number of this
encryption in
In Yocto Honister if i use sha256crypt for my password hash my finished Linux
image can not like it, and at first boot it forces to me to change it. If i use
sha512crypt for my hash everything is ok at Linux first boot.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Finaly, i found the problem and i could solve it. SHA-256 is too weak to make a
password hash, this is why on first login we need to change password always.
Please fix it in Yocto manual (
https://docs.yoctoproject.org/singleindex.html#term-EXTRA_USERS_PARAMS ). When
i set it to generate
Finaly, i found the problem and i could solve it. SHA-256 is too weak to make a
password hash, this is why on first login we need to change password always.
Please fix it in Yocto manual (
https://docs.yoctoproject.org/singleindex.html#term-EXTRA_USERS_PARAMS ). When
i set it to generate
Hi!
I am using honister release in Xilinx Yocto (meta-petalinux), my experience is
that my root user's password is expired in default and i need to change it in
first login. My final root password is pre-configured by usermod -p
and i am not using the new passwd-expire command.
Can i disable
Hi!
In extrausers.bbclass (
https://github.com/openembedded/openembedded-core/blob/honister/meta/classes/extrausers.bbclass
) there is a quite new passwd-expire (
https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg05373.html ) to
force password change on first login. I am using
In OpenEmbedded Kickstart Reference manual (
https://docs.yoctoproject.org/ref-manual/kickstart.html ) there are no any
support for F2FS filesystem ( https://en.wikipedia.org/wiki/F2FS ) in --fstype
options. Could you support it and plan to implement? It seems to me this file
system type can
33 matches
Mail list logo
